Set Decision Class Remit
Put a decision class in the board's remit, or take it out.
⛔THIS IS WHERE FREDERICK'S ANSWER LANDS, AND IT EXISTS SO THAT AN AGENT IS NEVER THE ONE WHO WRITES IT. The §6 question is "which decisions do you want the board to decide?" -- and without a place for the answer, the day he answers it somebody writes a migration in his name.
⛔IT IS A REMIT, NOT A THRESHOLD. Nothing in this schema orders decisions by size: magnitude_band is free text and decisions.stake is text. So the board's scope is a list, class by class.
⛔CORRECTED 2026-10-04 (#3592; the text this replaces said decision_classes.board_reviews "defaults FALSE -- nothing reaches the board until he says so here", which was the 2026-09-20 rule, migration 0511). RA-24 (2026-09-25, Frederick: "Everything important") superseded it: decisions.service.register_class stamps board_reviews = true on every NON-ROUTINE class at birth, attributed to the chairman, and migration 0655 backfilled the existing ones. Only a routine, reversible in-house class starts outside the remit. So this route is how a class goes OUT of the remit (or a routine one goes in), and a later registration never overrides the choice.
The class records who said it (board_reviews_set_by/_at, 0512), and a CHECK refuses a remit with nobody attributed -- the same discipline 0376 applied to the promotion threshold.
Request
- Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
- URL: https://api.pigeonly.com/api/chairman/decision-classes/{class_key}/remit
- Auth: none declared
Path parameters
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.