Blocker, authorization, failure and framework-issue routes
Every route on this page needs the standard Authorization: Bearer <token> header. While a
feature is off or not running, its routes answer 503 with a short error saying so (after
authentication, so an unauthenticated caller only ever sees 401).
Blocker Ledger
Section titled “Blocker Ledger”The Blocker Ledger records “I am blocked” claims and walks each one through a fixed pipeline
(candidate → authority-checked → access-requested → dry-run → live-run) until it is
settled as resolved or as a true-blocker. It is signal-only: it records and structures the
work, and never holds an outbound message. Switch: monitoring.blockerLedger.enabled. Every
write route requires the X-Instar-Request: 1 header (403 without it) and is rate-limited to
30 calls a minute.
GET /blockerslists entries. Query:limit,offset, andincludeArchived=1to include archived entries.GET /blockers/:idreturns one entry: its state, the full transition history, any recorded evidence, and its terminal record once settled.404for an unknown id.POST /blockersopens an entry. Body:detectedText(the blocker wording) andorigin(who opened it), both required (400without them). Answers201with the new entry in statecandidate.POST /blockers/:id/advancemoves an entry one step along the pipeline. Body:origin, plus the evidence the next step needs (authorityCheck,accessRequest,dryRunorliveRun) and an optionalnote. A settled entry cannot advance.POST /blockers/:id/settlesettles an entry. Bodykind: "resolved"takes aplaybookPath; it is refused unless the entry has a successful live run, and the playbook exists on disk inside the allowed skill and playbook folders and mentions the blocker id. Bodykind: "true-blocker"takes areasonKindfrom the closed list (operator-only-secret,operator-only-account,legal-billing-authorization,operator-judgment), arebuttal, theaccessRequestmade to the user, and the failed attempt that came first. When the Self-Unblock checklist is on, that attempt must be a stored checklist run named byselfUnblockRunId(a caller-writtenfailedAttemptis then ignored). The settle is judged by the outbound gate’s authority before it is written. A settled true-blocker carries arecheckAfterdate, when it is reopened and tested again.
Errors: 400 missing detectedText or origin, 403 missing intent header, 404 unknown entry, 409 settling an entry that is already settled, 422 for any other evidence or validation refusal (advancing a settled entry included).
Self-Unblock checklist runs
Section titled “Self-Unblock checklist runs”While this checklist is on, no blocker can be settled as a true blocker without a stored run:
the agent runs the Self-Unblock checklist, which probes every credential source it can reach for
the target. The secret and account kinds need a self-fetch run; the other kinds a dry-run run. Switch:
monitoring.blockerLedger.selfUnblockChecklist.enabled. Both routes send
Cache-Control: no-store, and each probe’s free-text detail is wrapped as data, not
instructions.
POST /blockers/self-unblock-runruns the checklist now and stores the run, so a later settle can cite itsrunIdasselfUnblockRunId. Body:target(aservice:scopestring, required) and optionalrequiredAttemptType(self-fetch, the default, ordry-run). NeedsX-Instar-Request: 1. Returns the run:runId,target,completedAt,exhausted, the resultingrung, and one row per probe (source,reachable,holdsRelevantCred,probedAt,matchedScopeTags).GET /blockers/self-unblock-runslists recent runs in the same shape, newest last;limitcaps it (1 to 200, default 200).
Authorization requests
Section titled “Authorization requests”An agent can propose that the operator grant a named Slack user one floor action for a set
time. The proposal confers nothing until the operator approves it. Switch: the
authorization-requests feature (503 “authorization-requests feature not enabled” while off).
Proposable actions are prod-deploy, money-movement, credential-access,
destructive-data and external-send; granting authority to others is never proposable.
POST /authorization-requestscreates a request. Body:proposal(withfloorAction,grantedToSlackUserId,durationMs), optionalreasonandcreatedByAgent. The grantee must be a registered Slack user (400“unknown-user” otherwise). Answers201with the request id anddeduped: truewhen an identical pending request already existed.GET /authorization-requestslists requests;statusfilters topending,approved,denied,expiredorwithdrawn. Each row carries the server-writtenheadlineandreason, the only text an operator screen should show.GET /authorization-requests/:idreturns one request in the same shape.404for an unknown id.POST /authorization-requests/:id/approveis the one step that grants anything. It is PIN-gated, re-checks the action and the grantee at approval time, and issues a signed grant mandate that expires with the grant.201on approval,200if it was already approved.POST /authorization-requests/:id/denydeclines a request. PIN-gated; bodydenyReasonis required.POST /authorization-requests/:id/withdrawlets the proposing agent withdraw its own pending request. Body:createdByAgent.
The owner’s phone can approve or decline the same requests with a Face ID proof instead of the PIN.
Failure-Learning Loop reads
Section titled “Failure-Learning Loop reads”The failure ledger records why features broke and which build skill they came from. Switch:
monitoring.failureLearning.enabled (503 “failure-learning disabled” while off).
GET /failures/analysisreturns the analysis of the ledger, plus arolloutblock naming the stage (dark,capture-onlyorinsight-push). QuerysinceDayslimits the window.GET /failures/insightslists the patterns the analyzer found. Query:status,before(an ISO timestamp, for paging back) andlimit(default 50).GET /failures/:idreturns one failure record.404for an unknown id.
Framework-issue ledger
Section titled “Framework-issue ledger”The Framework-Onboarding Mentor System’s record of behavioral issues found while bringing up
a framework (Codex, Gemini and so on). It is observability only and never gates anything. It has
no switch; its routes answer 503 “framework issue ledger unavailable” only if the ledger failed
to start.
GET /framework-issueslists issues. Query:framework,bucket,status,limit(1 to 500, default 100). An unknownframeworkreturns an empty list along with the known frameworks; a badbucketorstatusanswers400.GET /framework-issues/playbookreturns the lessons that carry over to a new framework. QuerytargetFrameworkis required.GET /framework-issues/capture-statsshows mentor runs against observations written; runs that keep producing zero observations point at a broken writer.GET /framework-issues/observabilityshows how issues spread across buckets, plus the counts of suspected leaks, probable loops and lessons extracted into the playbook.POST /framework-issues/observerecords an issue found during engineering work. Required:framework,bucket,title,dedupKey. Optional:severity,signature,evidence,observedVersion,bucketPrimary,relatedSpec, andstatus(withfixedInVersion, orwontFixReasonforwont-fix) to backfill an issue that is already closed. A repeat with the sameframeworkanddedupKeyis recorded against the existing issue instead of opening a new one.POST /framework-issues/:id/promotemoves an issue’s playbook status. Body:status(none,candidate,extracted,superseded) andpromotedBy. Promoting toextractedneeds an attester other than Echo: the agent that proposed a lesson cannot promote it itself.