rooster-instructions

Create Instruction

Files a directive from Damien, carrying the chairman's own authority (migration 0572's own header). Refused for anything other than an api key holding the instruct scope -- an ordinary human session reaches current_principal fine (it is not a read-only key, so the central method wall never engages) but has no api_key_scopes at all, so the explicit check below still refuses it. This is Damien's channel, not a second way for a human to do the same thing a human's own tools already do.

⛔ENQUEUES ITS OWN PLANNING WORK, IF SOMEBODY IS CONFIGURED TO RUN IT. Unset EXECUTIVE_MANAGER_PRINCIPAL_ID never blocks filing the directive -- Damien's instruction is real and recorded either way -- it just has nothing planning it yet, and the response says so plainly rather than silently dropping the obligation.

post/api/rooster/instructions

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/rooster/instructions
  • Auth: none declared

Request body

textstring required

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.