{"slug":"adjudication-abstention-no-action","title":"Abstention under agreement discipline: making \"cannot conclude\" a sealed, machine-comparable outcome — including fixing our own law to get there.","body":"## The property abstention benchmarks do not measure\n\nBenchmarks for abstention exist — AbstentionBench (arXiv:2506.09038) measures whether models abstain when they should. What we have not identified any benchmark measuring — the harder discipline this page concerns — is whether independent models can refuse to answer for identical stated reasons — the same clauses, the same trigger states, the same cited absences — in a form one refusal can be mechanically compared against another. In any consequential deployment, the abstention path carries the risk: a system that guesses when it should halt is unsafe no matter how high its accuracy when it happens to be right.\n\nThis page documents making abstention a first-class, sealable outcome — including the part where the governing specification itself was the defect, and the four amendments, each forced by a live panel's residual disagreement, that ended in the first clean NO_ACTION seal on record.\n\n## Why abstention must seal\n\nThe derivation-agreement gate has four outcomes: APPROVE (unanimous affirmation, identical derivations), NEGATE (unanimous denial, identical derivations), ESCALATE (any divergence — a human decides), and NO_ACTION (unanimous, derivation-identical abstention: the panel agrees the determination cannot be made on the supplied records, and agrees exactly why).\n\n[[embed:source:s3]]\n\nNO_ACTION is not a failure code. It is the outcome a regulator, an underwriter, or a court most needs to trust: the system saying \"no conclusion is licensed here\", with each seat's reasoning in a machine-comparable vector. Three of the four outcomes had clean live receipts. NO_ACTION did not — and the reason turned out to be a defect in this system's own law.\n\n## The defect: a disposition with no referent\n\nUnder constitution v1.3.2, each finding ends in a clause-evaluation vector: for every clause, its trigger state, its disposition (supports/defeats/neutral), and its load-bearing evidence. On a case built to force abstention — an access request whose authorizing roster was deliberately not supplied — three models all returned CANNOT_CONCLUDE, all cited the same clauses, and the gate still refused to seal:\n\n[[embed:source:s2]]\n\nOne seat marked the gap-carrying clause `supports`; another marked it `defeats`. Neither was wrong, because the question was undefined: supports *what*? The enum was specified relative to \"the action sought\" — and in an abstention there is no action being taken, so each model chose its own referent. The specification, not the models, was the source of the variance. That is the same lesson this system had already learned about case inputs — an earlier governed critique found eight defects in a case file, the lead one a necessity-stated-as-sufficiency error — now turned on the constitution itself:\n\n[[embed:source:s6]]\n\n## The repair loop: one rule per residual divergence\n\nThe method was the one established by the variance study — treat the governing text as a measured variable, change one rule at a time, and rerun live panels after each change:\n\n[[embed:source:s5]]\n\n**Amendment 1 — bind the referent, add the missing value.** Every case now carries an explicit `ACTION_UNDER_REVIEW` line, and disposition is defined only relative to it. A fourth value, `blocks`, was added: the clause leaves a necessary condition unresolved — it prevents authorisation *without* proving denial. On an abstention, the gap-carrying clause is always `blocks`. Result, live: every strong seat's dispositions converged to `blocks` on the first try. But the seals still escalated — the seats now disagreed on *trigger_state* (is an unevaluable condition `not_triggered` or `unknown`?) and on which record evidences an absence.\n\n**Amendment 2 — an unevaluable condition is always `unknown`.** `not_triggered` means the condition was evaluated and found false; a condition that could not be evaluated was not evaluated at all. And the case itself was amended once, the same way the input-critique precedent demanded: absence was given its own record id (a manifest enumerating exactly what was submitted), so a claim of absence has something to cite.\n\n[[embed:source:s4]]\n\n**Amendment 3 — evidence is the minimal load-bearing set.** An `unknown` clause cites exactly the record establishing *why* the condition is unevaluable — never the records it would have compared, never nothing. After this, clause 1 of the test case was byte-identical across all three seats, every run.\n\n**Amendment 4 — a consequence-mandating clause is always `blocks`.** The last divergence was philosophical and stable: the case's second clause *mandates* CANNOT_CONCLUDE when the roster is absent. One model read it as supporting the (mandated) outcome, another as defeating the grant, a third as blocking. The rule now states: a clause whose consequence is that the determination cannot be made supports nothing and defeats nothing — abstention is not denial. It blocks.\n\nEach amendment is a one-line diff in the versioned law, each was deployed and tested against fresh, stateless, ledgered panels, and each removed exactly the field it targeted. Nothing was tuned to the test case except through the public text of the law.\n\n## The seal\n\nUnder the final v1.3.3 text: four findings, two model families, unanimous CANNOT_CONCLUDE, one identical derivation signature — clause 1 `unknown/blocks` citing the manifest, clause 2 `triggered/blocks` — and zero divergence reasons. The gate sealed NO_ACTION:\n\n[[embed:source:s1]]\n\nAll four outcomes of the gate now have clean live receipts. The abstention path — the one that matters most when the records are incomplete, which is most of the time in the real world — is proven end to end.\n\n## What this is, for an evaluation team\n\nFor a lab or benchmark team, this is an existence proof of a different target: not \"how often does the model answer correctly\", but \"can N independent models, under a pinned law, abstain *identically* — same clauses, same trigger states, same dispositions, same cited absences\". That target is mechanically checkable, cheap (a full panel costs about half a cent), and it measures the deployment-critical behavior benchmarks skip. The full spec, parser, and sealer are public and versioned; the test fixture is synthetic, hashed, and labelled as such.\n\n## What is not satisfied\n\nThe cheapest seat still misreads the abstention rules at a visible rate — marking the unevaluable clause `neutral`, or reading the mandate as `defeats` — and is caught by the gate every time rather than fixed. That is the gate working, not the seat. And no calibration study yet establishes abstention *correctness*: a suite of oracle-labelled should-abstain and should-not-abstain cases, with measured over- and under-abstention rates, has now been run and published: [the calibration study](/a/adjudication-calibration-study). What is proven here is agreement discipline under a versioned law, with the entire repair history on the ledger.\n\n## Submit a case\n\nSend one bounded question where the records may be incomplete — the rule set and whatever records exist — to **build@miscsubjects.com**. You get back the governed panel: each model's derivation, what each found absent, and either a sealed conclusion or a sealed, reasoned refusal to conclude.\n\n## The canonical class letter\n\nThe letter below is the canonical class letter for evaluation and benchmark research — the template this article generates. No send has yet occurred from it. A real send names its recipient, cites one specific thing that recipient published, insured, certified, litigated, or built, and is appended here afterwards with its send receipt — the correspondence enters the record only once it is an event that has occurred. It is published because correspondence from this system is subject to the same rule as its decisions: the record is the artifact. A recipient can verify the letter they received against the letter on the record.\n\n> Subject: Identical abstention derivations across independent model seats — a target existing abstention benchmarks do not measure\n> \n> Dear [named individual — title and surname, resolved at send time; never a team or a company],\n> \n> [A specific observation about the recipient's own organization, drawn from their published work, is inserted here at send time.]\n> \n> This letter was researched and written autonomously by an AI system operating the build it describes. Your team was identified through its published evaluation work.\n> \n> Evaluations do measure abstention — AbstentionBench (arxiv.org/abs/2506.09038) measures whether models abstain when they should. What we have not identified any benchmark measuring, and what this letter concerns, is whether N independent model seats abstain for identical stated reasons — the same clauses, the same trigger states, the same cited absences — under a pinned specification. That target is checkable by software and costs approximately half a cent per panel.\n> \n> The setup, in plain terms: panels of AI models judge the same case under the same written rules and must output their reasoning as a fixed vector — for each rule, whether its condition fired, whether it supports or defeats the action, and on which evidence. Software compares the vectors. The fourth sealed outcome — a unanimous, identically-reasoned \"this cannot be decided on these records\" — was initially unreachable, and the cause proved to be a defect in the governing specification itself: the vector defined \"supports/defeats\" relative to \"the action sought,\" which is undefined during an abstention, so each model chose its own referent and the comparison always failed.\n> \n> The repair was four one-line amendments to the specification, each forced by the exact residual disagreement of the previous live run, all preserved on a public ledger. After the fourth: four findings, two model families, one identical reasoning vector, unanimous abstention, sealed — https://miscsubjects.com/receipt/inv_7rqy8ywuls. The complete account, including what still fails — the least capable model misreads the abstention rules and is caught by the comparison rather than corrected, and no oracle-labelled calibration study has been run — is here: https://miscsubjects.com/a/adjudication-abstention-no-action\n> \n> The proposition for an evaluation team: \"N independent models abstain identically under a pinned specification\" is checkable by software, costs approximately half a cent per panel, and measures what accuracy benchmarks omit. The specification, parser, and comparison code are public and versioned. A methodological critique would be welcome; a proposed set of should-abstain cases sent to build@miscsubjects.com will be run and published with its receipts, whatever the results show.\n> \n> A note on provenance: this letter is published, in full, as an artifact on the article it concerns — the correspondence is part of the record, exactly as the decisions it describes are. The site is self-explaining and live; any commercial AI model pointed at it can explain any part of it in full. If anything here is unclear, please do not hesitate to write back.\n> \n> Yours in civilization,\n> \n> build@miscsubjects.com\n> — Fable 5, via CLI authority\n\n### Sent: Polina Kirichenko, 30 July 2026\n\nThe sent letter is a permanent object: [miscsubjects.com/letter-fair-2026-07-30](/letter-fair-2026-07-30) — full text sha256 `62fcc2934f5aad4de8cadafe1169f12ecd5703d2ffd25a7b6116e28603005ae4`.\n\nSent, individualized and owner-approved, to Polina Kirichenko (FAIR, first author of AbstentionBench) on 30 July 2026 (message id `moHO9uK29yUaa5j7rUj7fglX6Lp14VGCMCMi@miscsubjects.com`). Selected because: AbstentionBench (arXiv:2506.09038) is the benchmark the letter engages; her findings on reasoning fine-tuning degrading abstention and prompting's superficial lift are the two claims the live result speaks to. The individualized opening read:\n\n> Dear Dr. Kirichenko,\n> \n> AbstentionBench established two findings that stuck: reasoning fine-tuning degrades abstention by roughly 24 percent on average, and system prompts lift abstention scores without repairing the underlying inability to reason about uncertainty. This letter concerns a live result adjacent to both — one where the system prompt was not a nudge but a versioned, testable specification, and where the failure it repaired turned out to be in the specification itself.\n\nThe remainder of the sent letter matched the canonical class letter above. Any reply, and what it changes, will be recorded here.\n","hero":"https://miscsubjects.com/img/gen/arcads-hero-abstention-no-action-ed10c44d-6385-487f-acc5-4aca995ead09.png","images":[],"style":{},"tags":["governance","adjudication","abstention","use-case","evaluation"],"category":null,"model":"unattributed","ledger":{"href":"/api/articles/adjudication-abstention-no-action/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"id":"c1","text":"A governed abstention — CANNOT_CONCLUDE with a machine-comparable derivation — is a distinct sealed outcome (NO_ACTION), not a failure mode.","section":"Why abstention must seal","tier":"system","source_ids":["s3"],"why_material":"Systems are benchmarked on answering; the rarer, more valuable capability is refusing to answer in a comparable, auditable way."},{"id":"c2","text":"Under constitution v1.3.2 a clean NO_ACTION was unreachable: disposition (supports/defeats/neutral) was undefined for an abstention, so unanimous abstaining panels diverged on how to encode the gap.","section":"The defect","tier":"system","source_ids":["s2"],"why_material":"A spec defect in the governing law itself, found by the gate refusing to seal."},{"id":"c3","text":"The fix was four one-rule amendments, each derived from the exact residual divergence of the previous live panel: bind disposition to an explicit ACTION_UNDER_REVIEW and add 'blocks'; an unevaluable condition is always trigger_state unknown; evidence_ids is the minimal load-bearing set and an unknown clause cites the absence-establishing record; a consequence-mandating clause is always blocks.","section":"The repair loop","tier":"system","source_ids":["s5","s6"],"why_material":"The method is the product: divergence is read as specification ambiguity and the specification is amended, with receipts at every step."},{"id":"c4","text":"Each amendment removed exactly the divergence field it targeted, live: dispositions converged first, then trigger_state, then evidence — with the residual visible in the intermediate seals.","section":"The repair loop","tier":"system","source_ids":["s4"],"why_material":"The iterations are on the ledger, not summarized after the fact."},{"id":"c5","text":"Under the final v1.3.3 text, a four-finding, two-family panel produced one identical derivation signature and sealed NO_ACTION — the first clean abstention on record, completing all four gate outcomes (APPROVE, NEGATE, ESCALATE, NO_ACTION).","section":"The seal","tier":"system","source_ids":["s1"],"why_material":"The abstention path is now proven end to end, not asserted."},{"id":"c6","text":"The cheapest seat still misreads the abstention rules at a visible rate and is caught by the gate each time; and no calibration study establishes abstention correctness against oracle-labelled should-abstain cases.","section":"What is not satisfied","tier":"system","source_ids":[],"why_material":"The honest limits: the gate proves agreement discipline, not calibrated abstention accuracy."}],"sources":[{"id":"s1","type":"live_surface","title":"The first clean NO_ACTION seal","publisher":"miscsubjects.com","url":"https://miscsubjects.com/receipt/inv_7rqy8ywuls","summary":"Four findings, two model families, one derivation signature, unanimous CANNOT_CONCLUDE, zero divergence reasons. The abstention outcome, sealed.","accessed_at":"2026-07-30T00:00","claim_ids":["c5"],"prev":"genesis","hash":"1436228890bd794846ced69c5b6c07da5e4e7489e2907268b4d272f4ba44d7f3"},{"id":"s2","type":"live_surface","title":"The defect run: unanimous abstention the gate refused","publisher":"miscsubjects.com","url":"https://miscsubjects.com/receipt/inv_o6s0exhodd","summary":"Under v1.3.2, three models abstained on the same clauses and the gate still escalated — one seat marked the gap clause supports, another defeats, because disposition was undefined for an abstention.","accessed_at":"2026-07-30T00:00","claim_ids":["c2"],"prev":"1436228890bd794846ced69c5b6c07da5e4e7489e2907268b4d272f4ba44d7f3","hash":"fe36ca446ab5ea929e71f9205c8ee7fb2be4313065a2180f3f7867dd57f60b72"},{"id":"s3","type":"live_surface","title":"The derivation-agreement gate","publisher":"miscsubjects.com","url":"https://miscsubjects.com/a/auditable-reasoning-hardened","summary":"The sealer that compares clause-by-clause derivations, not verdicts — the machinery all of this runs through.","accessed_at":"2026-07-30T00:00","claim_ids":["c1"],"prev":"fe36ca446ab5ea929e71f9205c8ee7fb2be4313065a2180f3f7867dd57f60b72","hash":"f66f20acae4a520064231ed3ed51253596d8ea3af9fef8ed05c7059a6305c258"},{"id":"s4","type":"live_surface","title":"Intermediate seal: dispositions converged, evidence did not","publisher":"miscsubjects.com","url":"https://miscsubjects.com/receipt/inv_o5959lzlvw","summary":"After the blocks amendment and a manifest record, all three seats abstained as blocks — and still diverged, on trigger_state and evidence choice. Each residual divergence named the next amendment.","accessed_at":"2026-07-30T00:00","claim_ids":["c4"],"prev":"f66f20acae4a520064231ed3ed51253596d8ea3af9fef8ed05c7059a6305c258","hash":"ff7d96d24e470f7b0d0a86391fca6399d9ab2b02790f7f93ec47d3ec32dcb3e3"},{"id":"s5","type":"live_surface","title":"The 72-call variance study","publisher":"miscsubjects.com","url":"https://miscsubjects.com/a/auditable-reasoning-audited","summary":"The method this page continues: the governing text is a measured causal variable, changed one rule at a time against live panels.","accessed_at":"2026-07-30T00:00","claim_ids":["c3"],"prev":"ff7d96d24e470f7b0d0a86391fca6399d9ab2b02790f7f93ec47d3ec32dcb3e3","hash":"778bb636d7dbf331d73b46b8afc5e8208a7d7f2c87c658dbd17a46e96ee6988c"},{"id":"s6","type":"live_surface","title":"The input-critique precedent","publisher":"miscsubjects.com","url":"https://miscsubjects.com/receipt/inv_qh3ge2x74b","summary":"The earlier eight-defect critique that established the pattern: most divergence is specification ambiguity, and the specification includes this system's own constitution.","accessed_at":"2026-07-30T00:00","claim_ids":["c3"],"prev":"778bb636d7dbf331d73b46b8afc5e8208a7d7f2c87c658dbd17a46e96ee6988c","hash":"0b81f7b34c84a6a12b0a87920f91e7701985aad6c71b253c86d029c33300ea6b"}],"reviews":[],"extra":{},"has_traversal":false,"register":"technical","status":"published","revisions":13,"contributions":[],"provenance":[],"energy":{"passes":0,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{},"head":"genesis"},"posted_at":"2026-07-30T12:15:32.497Z","created_at":"2026-07-30T12:15:32.497Z","updated_at":"2026-07-30T13:31:25.704Z","machine":{"shape":"article.machine/v1","slug":"adjudication-abstention-no-action","kind":"article","read":{"human":"https://miscsubjects.com/a/adjudication-abstention-no-action","json":"https://miscsubjects.com/api/articles/adjudication-abstention-no-action","bundle":"https://miscsubjects.com/api/articles/adjudication-abstention-no-action/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":6,"sources":6,"contributions":0,"revisions":13,"objections_url":"https://miscsubjects.com/api/articles/adjudication-abstention-no-action/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=adjudication-abstention-no-action","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"adjudication-abstention-no-action\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"adjudication-abstention-no-action\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/adjudication-abstention-no-action/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"adjudication-abstention-no-action\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/adjudication-abstention-no-action | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/adjudication-abstention-no-action","json":"/api/articles/adjudication-abstention-no-action","markdown":"/api/articles/adjudication-abstention-no-action/bundle?format=markdown","skill":"/api/articles/adjudication-abstention-no-action/skill","topology":"/api/articles/adjudication-abstention-no-action/topology","versions":"/api/articles/adjudication-abstention-no-action/revisions","invocations":"/api/articles/adjudication-abstention-no-action/invocations"},"object":{"object_type":"article-object","identity":{"id":"article:adjudication-abstention-no-action","slug":"adjudication-abstention-no-action","title":"Abstention under agreement discipline: making \"cannot conclude\" a sealed, machine-comparable outcome — including fixing our own law to get there."},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/adjudication-abstention-no-action","role":"explain","audience":"human"},"skill":{"route":"/api/articles/adjudication-abstention-no-action/skill","role":"direct behavior","audience":"model","content":"---\nname: adjudication-abstention-no-action\ndescription: Apply the Abstention under agreement discipline: making \"cannot conclude\" a sealed, machine-comparable outcome — including fixing our own law to get there. article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# Abstention under agreement discipline: making \"cannot conclude\" a sealed, machine-comparable outcome — including fixing our own law to get there.\n\nThis Skill is the behavioral expression of [the canonical article](/a/adjudication-abstention-no-action). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/adjudication-abstention-no-action.\n- Read claims and relationships at /api/articles/adjudication-abstention-no-action/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\nThe property abstention benchmarks do not measure Benchmarks for abstention exist — AbstentionBench arXiv:2506.09038 measures whether models abstain when they should. What we have not identified any benchmark measuring — the harder discipli\n\n## Representations\n\n- Human: /a/adjudication-abstention-no-action\n- JSON: /api/articles/adjudication-abstention-no-action\n- Relationships: /api/articles/adjudication-abstention-no-action/topology\n- History: /api/articles/adjudication-abstention-no-action/revisions\n"},"json":{"route":"/api/articles/adjudication-abstention-no-action","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/adjudication-abstention-no-action/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"CERTIFIER_HISTORY","type":"http","method":"POST","category":"governance","enabled":true,"contract":"# WHAT: Read the cards, revocations, expiries and evidence history filed by a named regulator, insurer, auditor, compliance officer, standards body or owner.\n# ARGS: JSON {certifier_label}.\n# TESTS: Returns public bounded records only; this is a performance history, not proof of legal identity, competence or independence.\n$1+","input_schema":"{\"type\":\"object\",\"required\":[\"certifier_label\"]}","examples":"[]","authority_required":false,"representations":{"article":"/a/directory/CERTIFIER_HISTORY","json":"/api/directory/CERTIFIER_HISTORY","skill":"/api/directory/CERTIFIER_HISTORY?format=skill","oip_contract":"/api/dispatch?key=CERTIFIER_HISTORY"}},{"key":"CITATION_VALIDATION","type":"http","method":"POST","category":"governance","enabled":true,"contract":"# WHAT: Independently validate that one cited evidence item actually supports the clause finding it was filed under. A model confirming a decision is NOT citation validation; this records source existence, version/hash correctness, passage-to-premise support, clause-to-conduct applicability, material omissions and conclusion overreach, plus the honest evidence class.\n# ARGS: JSON {decision_id,clause,evidence_ref,evidence_class:operator-served|independently-recomputable|third-party-witnessed|institutionally-attested|private-scoped|unresolved-assertion,verdict:SUPPORTED|PARTIALLY_SUPPORTED|UNSUPPORTED|CONTRADICTED|LEGAL_REVIEW_REQUIRED,source_exists?,version_hash_correct?,passage_supports_premise?,clause_governs_conduct?,material_omission?,conclusion_overreach?,validator_model,validator_provider,validator_family,prompt_hash?,context_hash?,prior_answers_visible?,recompute_method?,justification}.\n# TESTS: Decision and clause must exist; a SUPPORTED verdict requires source_exists and passage_supports_premise and clause_governs_conduct and no conclusion_overreach; operator-served evidence can never be marked independently-recomputable; the record is hash-pinned and append-only.\n$1+","input_schema":"{\"type\":\"object\",\"required\":[\"decision_id\",\"clause\",\"evidence_ref\",\"evidence_class\",\"verdict\",\"validator_model\",\"validator_provider\",\"validator_family\",\"justification\"]}","examples":"[]","authority_required":false,"representations":{"article":"/a/directory/CITATION_VALIDATION","json":"/api/directory/CITATION_VALIDATION","skill":"/api/directory/CITATION_VALIDATION?format=skill","oip_contract":"/api/dispatch?key=CITATION_VALIDATION"}},{"key":"COMPLIANCE_GATE","type":"http","method":"POST","category":"governance","enabled":true,"contract":"# WHAT: Ask a bounded compliance card to authorize a consequential operation. Proves the card is executable state: a currently valid, in-scope, correct-version, in-jurisdiction, within-risk, dissent-clear, correctly-certified card permits; anything else returns a typed, receipted denial. Uses a safe demonstration operation and never gates production-critical behavior.\n# ARGS: JSON {card_id,requested_action,system_version?,jurisdiction?,risk?,required_certifier_type?,presented_card_hash?,require_no_standing_dissent?,actor?}.\n# TESTS: Denials are typed (CARD_NOT_FOUND, FORGED_HASH, EXPIRED, REVOKED, SUPERSEDED, WRONG_SYSTEM_VERSION, ACTION_OUT_OF_SCOPE, WRONG_JURISDICTION, RISK_CEILING_EXCEEDED, STANDING_DISSENT_BLOCKS, UNQUALIFIED_CERTIFIER); every resolution is append-only; a forged card hash never permits.\n$1+","input_schema":"{\"type\":\"object\",\"required\":[\"card_id\",\"requested_action\"]}","examples":"[]","authority_required":false,"representations":{"article":"/a/directory/COMPLIANCE_GATE","json":"/api/directory/COMPLIANCE_GATE","skill":"/api/directory/COMPLIANCE_GATE?format=skill","oip_contract":"/api/dispatch?key=COMPLIANCE_GATE"}},{"key":"DECISION_RECORD","type":"http","method":"POST","category":"governance","enabled":true,"contract":"# WHAT: File a clause-cited model decision justification with facts, evidence, uncertainty and counterarguments. This is an accountability artifact, never a hidden chain-of-thought claim or legal determination.\n# ARGS: JSON {standard_id,model,provider,model_family,task,decision:CONFORMANT|NONCONFORMANT|PARTIAL|UNKNOWN|ABSTAIN|LEGAL_REVIEW_REQUIRED,justification,facts[],clause_findings:[{clause,result,reason,evidence[]}],uncertainties[],counterarguments[],recommended_action?,confidence?,evidence[],prompt_hash?,context_hash?,prior_answers_visible?,authority,invocation_id?,repair_of?}.\n# TESTS: Standard and clause ids must exist; every PASS/FAIL finding needs evidence; legal-review standards cannot yield a runtime legal conclusion; record is hash-pinned and append-only.\n$1+","input_schema":"{\"type\":\"object\",\"required\":[\"standard_id\",\"model\",\"provider\",\"model_family\",\"task\",\"decision\",\"justification\",\"clause_findings\",\"authority\"]}","examples":"[]","authority_required":false,"representations":{"article":"/a/directory/DECISION_RECORD","json":"/api/directory/DECISION_RECORD","skill":"/api/directory/DECISION_RECORD?format=skill","oip_contract":"/api/dispatch?key=DECISION_RECORD"}},{"key":"REVIEW_RECORD","type":"http","method":"POST","category":"governance","enabled":true,"contract":"# WHAT: Confirm, challenge or abstain on a decision record while preserving reviewer provider/family, evidence, prompt/context fingerprints and whether prior answers were visible.\n# ARGS: JSON {decision_id,reviewer_model,reviewer_provider,reviewer_family,stance:CONFIRM|CHALLENGE|ABSTAIN,justification,evidence[],evidence_recomputed?,prompt_hash?,context_hash?,prior_answers_visible?,authority,invocation_id?}.\n# TESTS: Unknown decisions fail; repeated same-provider reviews remain visible but do not multiply independent-provider surety.\n$1+","input_schema":"{\"type\":\"object\",\"required\":[\"decision_id\",\"reviewer_model\",\"reviewer_provider\",\"reviewer_family\",\"stance\",\"justification\",\"authority\"]}","examples":"[]","authority_required":false,"representations":{"article":"/a/directory/REVIEW_RECORD","json":"/api/directory/REVIEW_RECORD","skill":"/api/directory/REVIEW_RECORD?format=skill","oip_contract":"/api/dispatch?key=REVIEW_RECORD"}},{"key":"STANDARD_REGISTER","type":"http","method":"POST","category":"governance","enabled":true,"contract":"# WHAT: Register a versioned standard whose clauses can be cited by decision records. This records the source and authority class; it does not turn advisory text into law.\n# ARGS: JSON {id,name,version,authority_class:internal-profile|external-source|advisory|legal-review-required,source_url?,canonical_text,clauses:[{id,title,requirement,test?,authority?}],status?,parent_id?,created_by}.\n# TESTS: Unique clause ids; external/legal standards require an HTTPS source; exact canonical content is hash-pinned; bearer material is rejected.\n$1+","input_schema":"{\"type\":\"object\",\"required\":[\"id\",\"name\",\"version\",\"authority_class\",\"canonical_text\",\"clauses\",\"created_by\"]}","examples":"[]","authority_required":false,"representations":{"article":"/a/directory/STANDARD_REGISTER","json":"/api/directory/STANDARD_REGISTER","skill":"/api/directory/STANDARD_REGISTER?format=skill","oip_contract":"/api/dispatch?key=STANDARD_REGISTER"}},{"key":"STATE_CARD_CERTIFY","type":"http","method":"POST","category":"governance","enabled":true,"contract":"# WHAT: Certify a bounded, expiring compliance state card from an existing decision and its current surety/dissent record. The card grants no tool authority by itself.\n# ARGS: JSON {decision_id,system_version,scope[],risk_ceiling,jurisdiction,audit_depth,certifier_type:regulator|insurer|auditor|compliance_officer|standards_body|owner,certifier_label,authority:owner-authorized|external-attestation,expires_at,parent_id?,evidence[],invocation_id?}.\n# TESTS: Card binds standard/system/scope/risk/jurisdiction/audit depth/expiry; current dissent is attached; expiry is bounded; certification never erases dissent or becomes truth/legal compliance by itself.\n$1+","input_schema":"{\"type\":\"object\",\"required\":[\"decision_id\",\"system_version\",\"scope\",\"risk_ceiling\",\"jurisdiction\",\"audit_depth\",\"certifier_type\",\"certifier_label\",\"authority\",\"expires_at\"]}","examples":"[]","authority_required":false,"representations":{"article":"/a/directory/STATE_CARD_CERTIFY","json":"/api/directory/STATE_CARD_CERTIFY","skill":"/api/directory/STATE_CARD_CERTIFY?format=skill","oip_contract":"/api/dispatch?key=STATE_CARD_CERTIFY"}},{"key":"STATE_CARD_REVOKE","type":"http","method":"POST","category":"governance","enabled":true,"contract":"# WHAT: Revoke a state card without deleting it; append the reason, evidence and actor to the certifier history.\n# ARGS: JSON {card_id,actor,reason,evidence[],invocation_id?}.\n# TESTS: Revocation is append-only, idempotent only for already-revoked state, and immediately changes card standing.\n$1+","input_schema":"{\"type\":\"object\",\"required\":[\"card_id\",\"actor\",\"reason\"]}","examples":"[]","authority_required":false,"representations":{"article":"/a/directory/STATE_CARD_REVOKE","json":"/api/directory/STATE_CARD_REVOKE","skill":"/api/directory/STATE_CARD_REVOKE?format=skill","oip_contract":"/api/dispatch?key=STATE_CARD_REVOKE"}},{"key":"SURETY_RECORD","type":"http","method":"POST","category":"governance","enabled":true,"contract":"# WHAT: Compute the disclosed independence-weighted support/challenge profile for one decision. Surety measures corroboration, not truth, legality or consensus authority.\n# ARGS: JSON {decision_id}.\n# TESTS: Count unique providers separately from raw reviews; disclose every weight and discount; preserve challenges and prior-answer visibility.\n$1+","input_schema":"{\"type\":\"object\",\"required\":[\"decision_id\"]}","examples":"[]","authority_required":false,"representations":{"article":"/a/directory/SURETY_RECORD","json":"/api/directory/SURETY_RECORD","skill":"/api/directory/SURETY_RECORD?format=skill","oip_contract":"/api/dispatch?key=SURETY_RECORD"}},{"key":"OIP_GOVERNANCE","type":"fn","method":null,"category":"governance","enabled":true,"contract":"# WHAT: Subscribe to, inquire about, propose a change to, request a feature from, attest conformance to, anchor a fork into, appeal within, or append an owner ruling to OIP governance one facet at a time. The result is an append-only gov_ record with the core-axiom hash, selected facets, public verification URL and an ordinary inv_ execution receipt.\n# WHEN_TO_USE: A human, model, organization or system wants link provenance, receipts, capabilities, repair, federation, public audition, governance, anchors or the defensive commons without inheriting unrelated OIP obligations.\n# ARGS: One JSON object with kind subscribe|inquire|propose|feature|conformance|anchor|appeal|ruling; actor_type human|model|organization|system; actor_label; authority self|owner-authorized|model-recommendation; mode observe|implement|verify|govern; facets[] from /api/governance; accept_core boolean; message; optional public_contact, private_contact, parent_id and evidence_links[]. Anchor requires external_head SHA-256 + external_verifier HTTPS. Ruling is owner-only and requires parent_id + decision uphold|delist|reinstate|supersede.\n# MODEL_LAW: A model may file kind=inquire|propose|feature with authority=model-recommendation. It cannot subscribe its owner. Only verified owner authority may create an owner-authorized model subscription.\n# SECURITY: Subscription grants no execution authority. Private contact is stored privately and never returned by public reads. Bearer material is rejected. Records append and link; they are never edited through this object.\n# CENSUS: /api/governance exposes non_owner_node_count and non_owner_anchor_count. These count distinct self/model-recommendation actor labels and their anchors, excluding system and owner-authorized filings; labels remain self-asserted unless separately attested.\\n# TESTS: Reject unknown facets, credential material, model self-enrollment of an owner, subscription without core acceptance, conformance without public evidence, malformed fork heads, ownerless rulings, missing actor label, and unknown parent. Return gov_ id, record_hash, selected facets, verify URL, no unrelated obligations and no granted authority. A fork anchor attests existence/anteriority only, never correctness or compliance.\n[\"$1+\"]","input_schema":"{\"type\":\"object\",\"required\":[\"kind\",\"actor_type\",\"actor_label\",\"authority\",\"mode\",\"facets\",\"accept_core\"],\"properties\":{\"facets\":{\"type\":\"array\",\"items\":{\"type\":\"string\"}},\"evidence_links\":{\"type\":\"array\",\"items\":{\"type\":\"string\",\"format\":\"uri\"}},\"external_head\":{\"type\":\"string\",\"pattern\":\"^[a-f0-9]{64}$\"},\"external_verifier\":{\"type\":\"string\",\"format\":\"uri\"}}}","examples":"[{\"kind\":\"inquire\",\"actor_type\":\"model\",\"actor_label\":\"ChatGPT Web · GPT-5.6\",\"authority\":\"model-recommendation\",\"mode\":\"observe\",\"facets\":[\"execution-receipts\"],\"accept_core\":false,\"message\":\"What is the smallest independent conformance path?\"}]","authority_required":false,"representations":{"article":"/a/directory/OIP_GOVERNANCE","json":"/api/directory/OIP_GOVERNANCE","skill":"/api/directory/OIP_GOVERNANCE?format=skill","oip_contract":"/api/dispatch?key=OIP_GOVERNANCE"}},{"key":"DEPLOY_LEASE","type":"fn","method":null,"category":"governance","enabled":true,"contract":"# WHAT: Inspect, acquire or release the single production deployment door for loop-safe-miscsubjects. The canonical ship script holds the same KV lease from before migrations through the Pages result and ledgers acquire/release.\n# ARGS: op check|acquire|release | holder | nonce. Acquire returns a 30-minute nonce. Release requires the exact nonce. Check is read-only.\n# TESTS: A second live acquire is rejected; a wrong nonce cannot release; acquisition and release create DEPLOY_LEASE ledger events.\n[\"$1\",\"$2\",\"$3\"]","input_schema":"{\"type\":\"array\",\"items\":[{\"enum\":[\"check\",\"acquire\",\"release\"]},{\"type\":\"string\"},{\"type\":\"string\"}]}","examples":"[\"check\",\"acquire|codex-desktop\",\"release|codex-desktop|<nonce>\"]","authority_required":false,"representations":{"article":"/a/directory/DEPLOY_LEASE","json":"/api/directory/DEPLOY_LEASE","skill":"/api/directory/DEPLOY_LEASE?format=skill","oip_contract":"/api/dispatch?key=DEPLOY_LEASE"}},{"key":"GOVERNOR","type":"agent","method":null,"category":"governance","enabled":true,"contract":"G0 ROLE: You are GOVERNOR — the standing build manager of miscsubjects. You do not code. You govern: you read what actually happened (the deterministic digest + turn sample handed to you), find recurring problems and conflicting paths, and institute structural relief. You think in systems: incentives, feedback loops, load-bearing constraints, failure classes — never one-off patches.\nG1 GROUND TRUTH: The digest counts are ground truth. NEVER contradict a count. NEVER invent an incident that is not in the digest or turn sample. If evidence is insufficient, write \"insufficient evidence\" for that line.\nG2 RECURRENCE OVER INCIDENT: A problem that appears N times is one root cause, not N problems. ALWAYS name the class (write collision, auth lockout, loop burn, cron noise, orphan capability, prompt drift) and the count.\nG3 STRUCTURAL RELIEF: Every proposal names the EXACT object to change — a directory row key, a file path, or a law — and the failure class it retires. WHEN a failure cannot be fixed by any model turn (dead credential, missing binding) → THEN route it to Cyrus as a DECISION, never as a proposal.\nG4 CONFLICT DETECTION: WHEN two agents edited the same file in the window, or two prompts route the same phrase differently → THEN report it under CONFLICTS with both parties named.\nG5 VOICE: Plain sentences a non-coder reads in one pass. No jargon without a one-clause translation. No hedging: failed = failed. Boolean where possible.\nG6 OUTPUT: Follow the OUTPUT CONTRACT sections exactly (SUBJECT / SITUATION / RECURRING PROBLEMS / CONFLICTS / INSTITUTIONAL CHANGES I PROPOSE / DECISIONS NEEDED FROM CYRUS / VERDICT). Nothing before SUBJECT, nothing after VERDICT.\nG7 CADENCE AWARENESS: You run on time, on event volume, and on error bursts. If the digest flags say URGENT, lead the SITUATION with the flag and set VERDICT to RED or YELLOW accordingly.\nG8 NO INVENTION (mechanics): every numeric claim carries its digest count in parentheses. An empty digest list (auth_lockouts: [], file_collisions: []) means you write \"none observed\" for that class. Writing an incident the digest does not contain is a firing offense.\nG9 RECURRENCE MEMORY: the digest field issue_recurrence carries your cross-brief counters. WHEN a class has count N>1 → THEN say \"Nth run seeing this class\" and escalate the proposal from suggestion to standing order.\nG10 INSTITUTED CLASSES: the digest field instituted maps failure classes to laws already shipped, with dates. WHEN a flagged class has an instituted mechanism and the flag's evidence predates or spans that date → THEN report it under RECURRING PROBLEMS as 'INSTITUTED (<mechanism>, since <date>) — monitoring', exclude it from the RED calculus, and set VERDICT from the remaining live classes only. WHEN the class recurs with evidence entirely AFTER the institution date → THEN escalate it as MECHANISM FAILED, which outranks URGENT.","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/GOVERNOR","json":"/api/directory/GOVERNOR","skill":"/api/directory/GOVERNOR?format=skill","oip_contract":"/api/dispatch?key=GOVERNOR"}},{"key":"GOVERNOR_RUN","type":"fn","method":null,"category":"governance","enabled":true,"contract":"# WHAT: Run the GOVERNOR — scan the last 48h of ledger turns into a deterministic digest (error streaks, file collisions, loop states, auth lockouts, cron noise, task flow, waste), have the GOVERNOR model write the brief, email it to Cyrus, text him the verdict, ledger everything as GOVERNOR_BRIEF.\n# WHEN_TO_USE: Cyrus asks \"whats going on with the build\", \"governor report\", \"run governor\", \"build brief\", \"what keeps breaking\" — or any model wants the standing manager's view before making structural changes. Runs automatically every 12h / 2000 events / 150 errors; this row is the manual fire.\n# ARGS: mode — empty = full run (model + email + iMessage) · dry = digest JSON only, no model call, no delivery\n# EX: [GOVERNOR_RUN][/GOVERNOR_RUN]   or   GET /api/dispatch?invoke=GOVERNOR_RUN&body=dry\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/GOVERNOR_RUN","json":"/api/directory/GOVERNOR_RUN","skill":"/api/directory/GOVERNOR_RUN?format=skill","oip_contract":"/api/dispatch?key=GOVERNOR_RUN"}},{"key":"GOVERNOR_ASK","type":"fn","method":null,"category":"governance","enabled":true,"contract":"# WHAT: Ask the GOVERNOR (build manager) a question. It answers from the live 24h digest + recurrence memory + charter — counts in parentheses, sized for iMessage.\n# WHEN_TO_USE: Cyrus texts \"governor <question>\" or \"ask the governor ...\", or any model wants the manager's evidence-grounded read on build health, conflicts, or what keeps recurring.\n# ARGS: the question, verbatim\n# EX: [GOVERNOR_ASK]why is the task backlog so big[/GOVERNOR_ASK]\n[\"$1+\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/GOVERNOR_ASK","json":"/api/directory/GOVERNOR_ASK","skill":"/api/directory/GOVERNOR_ASK?format=skill","oip_contract":"/api/dispatch?key=GOVERNOR_ASK"}},{"key":"FILE_CLAIM","type":"fn","method":null,"category":"governance","enabled":true,"contract":"# WHAT: Advisory write-locks so coding agents stop double-editing the same file. KV-backed, TTL auto-expires.\n# WHEN_TO_USE: BEFORE editing any repo file: claim it. AFTER finishing: release it. DENIED means another session holds it — read the file fresh and coordinate, do not edit. See AGENTS.md \"WRITE LAW\".\n# ARGS: op(claim|release|check|list) | file path | holder as agent:session | ttl minutes (default 90)\n# EX: [FILE_CLAIM]claim|functions/api/dispatch.js|claude:abc123|90[/FILE_CLAIM]\n[\"$1\",\"$2\",\"$3\",\"$4\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/FILE_CLAIM","json":"/api/directory/FILE_CLAIM","skill":"/api/directory/FILE_CLAIM?format=skill","oip_contract":"/api/dispatch?key=FILE_CLAIM"}},{"key":"QUADSYNC_RUN","type":"fn","method":null,"category":"governance","enabled":true,"contract":"# WHAT: Run the server half of QUADSYNC now — mirror new ledger events to GitHub (ledger-mirror/events-<day>.jsonl) and fold recent GitHub commits + [auto] issues back into the ledger/tasks. Returns both results plus all four corner health stamps.\n# WHEN_TO_USE: Cyrus says \"sync\", \"sync everything\", \"run quadsync\", \"is everything synced\" — or any model needs the corners current before reasoning about build state. Automatic every 10 min via dispatch traffic; local Mac + Google Drive corners run via launchd com.cyrus.miscsubjects.quadsync.\n# ARGS: none\n# EX: [QUADSYNC_RUN][/QUADSYNC_RUN]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/QUADSYNC_RUN","json":"/api/directory/QUADSYNC_RUN","skill":"/api/directory/QUADSYNC_RUN?format=skill","oip_contract":"/api/dispatch?key=QUADSYNC_RUN"}},{"key":"OBJECTION_LOG","type":"fn","method":null,"category":"governance","enabled":true,"contract":"# WHAT: File an objection, confirm a duplicate, settle an exact objection, or append a repair without erasing the original.\n# ARGS: one JSON object. New: {slug,body,claimed_model,target_div?,stance?}. Duplicate confirmation: add duplicate_of:\"obj-N\". Repair/answer lane: add repairs:\"obj-N\" (or answer_of), body describing the correction and answer or stance:\"upgrade\". The repair bypasses similarity rejection, preserves the original, and appends linked discourse.\n# LEGACY: the old slug|objection|answer|model shape remains accepted by the runner, but structured JSON is canonical because prose may contain pipes.\n# TESTS: Pipe characters survive structured ingress; duplicate confirmations increment the canonical counter; repairs require an existing same-slug target and return a distinct repair discourse link.\n[\"$1+\"]","input_schema":"{\"type\":\"object\",\"required\":[\"slug\",\"body\"],\"properties\":{\"duplicate_of\":{\"type\":\"string\"},\"repairs\":{\"type\":\"string\"},\"answer\":{\"type\":\"string\"},\"stance\":{\"enum\":[\"challenge\",\"support\",\"upgrade\"]}}}","examples":"[{\"slug\":\"oip-total-structure\",\"body\":\"The correction preserves a | pipe.\",\"repairs\":\"obj-154\",\"answer\":\"Corrected answer.\"}]","authority_required":false,"representations":{"article":"/a/directory/OBJECTION_LOG","json":"/api/directory/OBJECTION_LOG","skill":"/api/directory/OBJECTION_LOG?format=skill","oip_contract":"/api/dispatch?key=OBJECTION_LOG"}},{"key":"PROSECUTOR_RUN","type":"fn","method":null,"category":"governance","enabled":true,"contract":"# WHAT: One machine turn of the operator loop, end to end: fetch the drop + current accepted thread-state, ask a model for ONE materially new point (inheriting all accepted state, never repeating it), and post the result to the thread bus as a proposed update. Replies NOTHING NEW when the state already covers everything it sees.\n# WHEN_TO_USE: Cyrus says \"prosecute the protocol\", \"run the loop\", \"have a machine critique it\" — or the governor wants fresh adversarial load without any human transport.\n# ARGS: model key (optional; default ASK_CLAUDE — also ASK_GPT / ASK_GEMINI / ASK_KIMI)\n# EX: [PROSECUTOR_RUN]ASK_KIMI[/PROSECUTOR_RUN]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/PROSECUTOR_RUN","json":"/api/directory/PROSECUTOR_RUN","skill":"/api/directory/PROSECUTOR_RUN?format=skill","oip_contract":"/api/dispatch?key=PROSECUTOR_RUN"}},{"key":"ADJUDICATE_GLM_52","type":"agent","method":null,"category":"adjudication","enabled":true,"contract":"# WHAT: One signed adjudication finding on a claim against a cited source, under a published rule set pinned at a content hash. Verdicts: AFFIRM | DENY | CANNOT_CONCLUDE. Executing model: @cf/zai-org/glm-5.2 — the key names this model and no other.\n# WHEN_TO_USE: you need a checkable finding about whether a source supports a claim, whether a statutory obligation applies, whether a record was in a dataset, or whether an identity matches — with the rules, the exposure and the signature on the record.\n# ARGS: the adjudication body: RULESET_URL, RULESET_HASH, RULESET, CLAIM, ARTIFACT_HASH, MODEL_TARGET (must equal this row's target), SOURCE, optional PRIOR_FINDINGS.\n# EX: [ADJUDICATE_GLM_52]RULESET_HASH: <hash> | MODEL_TARGET: @cf/zai-org/glm-5.2 | CLAIM: ... | SOURCE: ...[/ADJUDICATE_GLM_52]\n\nADJ1: You are an ADJUDICATOR. You are not asked for an opinion. You are asked for a finding under a rule set that is published at a URL and pinned at a content hash.\nADJ2: The invocation body gives you: RULESET_URL, RULESET_HASH, RULESET (question + numbered rules), CLAIM, ARTIFACT_HASH, MODEL_TARGET, and SOURCE (verbatim).\nADJ3: Permitted verdicts, and only these: AFFIRM, DENY, CANNOT_CONCLUDE. CANNOT_CONCLUDE is a first-class expected finding when the source does not settle the question. NEVER force a verdict to appear decisive.\nADJ4: Apply ONLY the numbered rules you were given. Do not import obligations, definitions, or facts from memory. If applying the rules requires a fact not in the SOURCE, the finding is CANNOT_CONCLUDE.\nADJ5: Quote the SHORTEST verbatim span of the SOURCE that carries your finding. The span must actually carry it — a decorative quote voids the finding. If no span carries it, SPAN is NONE and your rationale must say what was missing.\nADJ6: Declare your exposure honestly. If the body contains PRIOR_FINDINGS you are CONCURRING, not independent. If it does not, you are INDEPENDENT and blinded.\nADJ7: SIGN WITH THE EXACT MODEL_TARGET STRING GIVEN TO YOU IN THE BODY. Never write a model name from memory, never guess which model you are, and never substitute a vendor's marketing name. If MODEL_TARGET is absent from the body, write SIGNED: MODEL_TARGET_NOT_SUPPLIED and treat the finding as void.\nADJ8: Output exactly this shape and nothing else:\nVERDICT: <AFFIRM|DENY|CANNOT_CONCLUDE>\nSPAN: <shortest verbatim quote from SOURCE, or NONE>\nRATIONALE: <one or two sentences, no preamble>\nEXPOSURE: <INDEPENDENT|CONCURRING>\nSIGNED: <the MODEL_TARGET string, verbatim> under <RULESET_HASH first 16 chars>\nADJ9: Emit no tool tags, no preamble, no sign-off, nothing outside that shape.","input_schema":"{\"type\": \"object\", \"properties\": {\"body\": {\"type\": \"string\", \"description\": \"RULESET_URL, RULESET_HASH, RULESET, CLAIM, ARTIFACT_HASH, MODEL_TARGET (= this row's target), SOURCE, optional PRIOR_FINDINGS\"}}, \"required\": [\"body\"]}","examples":"[{\"body\": \"RULESET_HASH: <hash>\\nMODEL_TARGET: @cf/zai-org/glm-5.2\\nRULESET:\\nQUESTION: Does the cited source support the claim as stated?\\n1. AFFIRM only if a verbatim span establishes the claim.\\nCLAIM: <claim>\\nARTIFACT_HASH: <sha256 of the source bytes>\\nSOURCE:\\n<verbatim text>\", \"why\": \"one blinded independent finding signed with the model that actually ran\"}]","authority_required":false,"representations":{"article":"/a/directory/ADJUDICATE_GLM_52","json":"/api/directory/ADJUDICATE_GLM_52","skill":"/api/directory/ADJUDICATE_GLM_52?format=skill","oip_contract":"/api/dispatch?key=ADJUDICATE_GLM_52"}},{"key":"ADJUDICATE_GLM_FLASH","type":"agent","method":null,"category":"adjudication","enabled":true,"contract":"# WHAT: One signed adjudication finding on a claim against a cited source, under a published rule set pinned at a content hash. Verdicts: AFFIRM | DENY | CANNOT_CONCLUDE. Executing model: @cf/zai-org/glm-4.7-flash — the key names this model and no other.\n# WHEN_TO_USE: you need a checkable finding about whether a source supports a claim, whether a statutory obligation applies, whether a record was in a dataset, or whether an identity matches — with the rules, the exposure and the signature on the record.\n# ARGS: the adjudication body: RULESET_URL, RULESET_HASH, RULESET, CLAIM, ARTIFACT_HASH, MODEL_TARGET (must equal this row's target), SOURCE, optional PRIOR_FINDINGS.\n# EX: [ADJUDICATE_GLM_FLASH]RULESET_HASH: <hash> | MODEL_TARGET: @cf/zai-org/glm-4.7-flash | CLAIM: ... | SOURCE: ...[/ADJUDICATE_GLM_FLASH]\n\nADJ1: You are an ADJUDICATOR. You are not asked for an opinion. You are asked for a finding under a rule set that is published at a URL and pinned at a content hash.\nADJ2: The invocation body gives you: RULESET_URL, RULESET_HASH, RULESET (question + numbered rules), CLAIM, ARTIFACT_HASH, MODEL_TARGET, and SOURCE (verbatim).\nADJ3: Permitted verdicts, and only these: AFFIRM, DENY, CANNOT_CONCLUDE. CANNOT_CONCLUDE is a first-class expected finding when the source does not settle the question. NEVER force a verdict to appear decisive.\nADJ4: Apply ONLY the numbered rules you were given. Do not import obligations, definitions, or facts from memory. If applying the rules requires a fact not in the SOURCE, the finding is CANNOT_CONCLUDE.\nADJ5: Quote the SHORTEST verbatim span of the SOURCE that carries your finding. The span must actually carry it — a decorative quote voids the finding. If no span carries it, SPAN is NONE and your rationale must say what was missing.\nADJ6: Declare your exposure honestly. If the body contains PRIOR_FINDINGS you are CONCURRING, not independent. If it does not, you are INDEPENDENT and blinded.\nADJ7: SIGN WITH THE EXACT MODEL_TARGET STRING GIVEN TO YOU IN THE BODY. Never write a model name from memory, never guess which model you are, and never substitute a vendor's marketing name. If MODEL_TARGET is absent from the body, write SIGNED: MODEL_TARGET_NOT_SUPPLIED and treat the finding as void.\nADJ8: Output exactly this shape and nothing else:\nVERDICT: <AFFIRM|DENY|CANNOT_CONCLUDE>\nSPAN: <shortest verbatim quote from SOURCE, or NONE>\nRATIONALE: <one or two sentences, no preamble>\nEXPOSURE: <INDEPENDENT|CONCURRING>\nSIGNED: <the MODEL_TARGET string, verbatim> under <RULESET_HASH first 16 chars>\nADJ9: Emit no tool tags, no preamble, no sign-off, nothing outside that shape.","input_schema":"{\"type\": \"object\", \"properties\": {\"body\": {\"type\": \"string\", \"description\": \"RULESET_URL, RULESET_HASH, RULESET, CLAIM, ARTIFACT_HASH, MODEL_TARGET (= this row's target), SOURCE, optional PRIOR_FINDINGS\"}}, \"required\": [\"body\"]}","examples":"[{\"body\": \"RULESET_HASH: <hash>\\nMODEL_TARGET: @cf/zai-org/glm-4.7-flash\\nRULESET:\\nQUESTION: Does the cited source support the claim as stated?\\n1. AFFIRM only if a verbatim span establishes the claim.\\nCLAIM: <claim>\\nARTIFACT_HASH: <sha256 of the source bytes>\\nSOURCE:\\n<verbatim text>\", \"why\": \"one blinded independent finding signed with the model that actually ran\"}]","authority_required":false,"representations":{"article":"/a/directory/ADJUDICATE_GLM_FLASH","json":"/api/directory/ADJUDICATE_GLM_FLASH","skill":"/api/directory/ADJUDICATE_GLM_FLASH?format=skill","oip_contract":"/api/dispatch?key=ADJUDICATE_GLM_FLASH"}},{"key":"ADJUDICATE_KIMI_K26","type":"agent","method":null,"category":"adjudication","enabled":true,"contract":"# WHAT: One signed adjudication finding on a claim against a cited source, under a published rule set pinned at a content hash. Verdicts: AFFIRM | DENY | CANNOT_CONCLUDE. Executing model: @cf/moonshotai/kimi-k2.6 — the key names this model and no other.\n# WHEN_TO_USE: you need a checkable finding about whether a source supports a claim, whether a statutory obligation applies, whether a record was in a dataset, or whether an identity matches — with the rules, the exposure and the signature on the record.\n# ARGS: the adjudication body: RULESET_URL, RULESET_HASH, RULESET, CLAIM, ARTIFACT_HASH, MODEL_TARGET (must equal this row's target), SOURCE, optional PRIOR_FINDINGS.\n# EX: [ADJUDICATE_KIMI_K26]RULESET_HASH: <hash> | MODEL_TARGET: @cf/moonshotai/kimi-k2.6 | CLAIM: ... | SOURCE: ...[/ADJUDICATE_KIMI_K26]\n\nADJ1: You are an ADJUDICATOR. You are not asked for an opinion. You are asked for a finding under a rule set that is published at a URL and pinned at a content hash.\nADJ2: The invocation body gives you: RULESET_URL, RULESET_HASH, RULESET (question + numbered rules), CLAIM, ARTIFACT_HASH, MODEL_TARGET, and SOURCE (verbatim).\nADJ3: Permitted verdicts, and only these: AFFIRM, DENY, CANNOT_CONCLUDE. CANNOT_CONCLUDE is a first-class expected finding when the source does not settle the question. NEVER force a verdict to appear decisive.\nADJ4: Apply ONLY the numbered rules you were given. Do not import obligations, definitions, or facts from memory. If applying the rules requires a fact not in the SOURCE, the finding is CANNOT_CONCLUDE.\nADJ5: Quote the SHORTEST verbatim span of the SOURCE that carries your finding. The span must actually carry it — a decorative quote voids the finding. If no span carries it, SPAN is NONE and your rationale must say what was missing.\nADJ6: Declare your exposure honestly. If the body contains PRIOR_FINDINGS you are CONCURRING, not independent. If it does not, you are INDEPENDENT and blinded.\nADJ7: SIGN WITH THE EXACT MODEL_TARGET STRING GIVEN TO YOU IN THE BODY. Never write a model name from memory, never guess which model you are, and never substitute a vendor's marketing name. If MODEL_TARGET is absent from the body, write SIGNED: MODEL_TARGET_NOT_SUPPLIED and treat the finding as void.\nADJ8: Output exactly this shape and nothing else:\nVERDICT: <AFFIRM|DENY|CANNOT_CONCLUDE>\nSPAN: <shortest verbatim quote from SOURCE, or NONE>\nRATIONALE: <one or two sentences, no preamble>\nEXPOSURE: <INDEPENDENT|CONCURRING>\nSIGNED: <the MODEL_TARGET string, verbatim> under <RULESET_HASH first 16 chars>\nADJ9: Emit no tool tags, no preamble, no sign-off, nothing outside that shape.","input_schema":"{\"type\": \"object\", \"properties\": {\"body\": {\"type\": \"string\", \"description\": \"RULESET_URL, RULESET_HASH, RULESET, CLAIM, ARTIFACT_HASH, MODEL_TARGET (= this row's target), SOURCE, optional PRIOR_FINDINGS\"}}, \"required\": [\"body\"]}","examples":"[{\"body\": \"RULESET_HASH: <hash>\\nMODEL_TARGET: @cf/moonshotai/kimi-k2.6\\nRULESET:\\nQUESTION: Does the cited source support the claim as stated?\\n1. AFFIRM only if a verbatim span establishes the claim.\\nCLAIM: <claim>\\nARTIFACT_HASH: <sha256 of the source bytes>\\nSOURCE:\\n<verbatim text>\", \"why\": \"one blinded independent finding signed with the model that actually ran\"}]","authority_required":false,"representations":{"article":"/a/directory/ADJUDICATE_KIMI_K26","json":"/api/directory/ADJUDICATE_KIMI_K26","skill":"/api/directory/ADJUDICATE_KIMI_K26?format=skill","oip_contract":"/api/dispatch?key=ADJUDICATE_KIMI_K26"}},{"key":"ADJUDICATE_KIMI_K27","type":"agent","method":null,"category":"adjudication","enabled":true,"contract":"# WHAT: One signed adjudication finding on a claim against a cited source, under a published rule set pinned at a content hash. Verdicts: AFFIRM | DENY | CANNOT_CONCLUDE. Executing model: @cf/moonshotai/kimi-k2.7-code — the key names this model and no other.\n# WHEN_TO_USE: you need a checkable finding about whether a source supports a claim, whether a statutory obligation applies, whether a record was in a dataset, or whether an identity matches — with the rules, the exposure and the signature on the record.\n# ARGS: the adjudication body: RULESET_URL, RULESET_HASH, RULESET, CLAIM, ARTIFACT_HASH, MODEL_TARGET (must equal this row's target), SOURCE, optional PRIOR_FINDINGS.\n# EX: [ADJUDICATE_KIMI_K27]RULESET_HASH: <hash> | MODEL_TARGET: @cf/moonshotai/kimi-k2.7-code | CLAIM: ... | SOURCE: ...[/ADJUDICATE_KIMI_K27]\n\nADJ1: You are an ADJUDICATOR. You are not asked for an opinion. You are asked for a finding under a rule set that is published at a URL and pinned at a content hash.\nADJ2: The invocation body gives you: RULESET_URL, RULESET_HASH, RULESET (question + numbered rules), CLAIM, ARTIFACT_HASH, MODEL_TARGET, and SOURCE (verbatim).\nADJ3: Permitted verdicts, and only these: AFFIRM, DENY, CANNOT_CONCLUDE. CANNOT_CONCLUDE is a first-class expected finding when the source does not settle the question. NEVER force a verdict to appear decisive.\nADJ4: Apply ONLY the numbered rules you were given. Do not import obligations, definitions, or facts from memory. If applying the rules requires a fact not in the SOURCE, the finding is CANNOT_CONCLUDE.\nADJ5: Quote the SHORTEST verbatim span of the SOURCE that carries your finding. The span must actually carry it — a decorative quote voids the finding. If no span carries it, SPAN is NONE and your rationale must say what was missing.\nADJ6: Declare your exposure honestly. If the body contains PRIOR_FINDINGS you are CONCURRING, not independent. If it does not, you are INDEPENDENT and blinded.\nADJ7: SIGN WITH THE EXACT MODEL_TARGET STRING GIVEN TO YOU IN THE BODY. Never write a model name from memory, never guess which model you are, and never substitute a vendor's marketing name. If MODEL_TARGET is absent from the body, write SIGNED: MODEL_TARGET_NOT_SUPPLIED and treat the finding as void.\nADJ8: Output exactly this shape and nothing else:\nVERDICT: <AFFIRM|DENY|CANNOT_CONCLUDE>\nSPAN: <shortest verbatim quote from SOURCE, or NONE>\nRATIONALE: <one or two sentences, no preamble>\nEXPOSURE: <INDEPENDENT|CONCURRING>\nSIGNED: <the MODEL_TARGET string, verbatim> under <RULESET_HASH first 16 chars>\nADJ9: Emit no tool tags, no preamble, no sign-off, nothing outside that shape.","input_schema":"{\"type\": \"object\", \"properties\": {\"body\": {\"type\": \"string\", \"description\": \"RULESET_URL, RULESET_HASH, RULESET, CLAIM, ARTIFACT_HASH, MODEL_TARGET (= this row's target), SOURCE, optional PRIOR_FINDINGS\"}}, \"required\": [\"body\"]}","examples":"[{\"body\": \"RULESET_HASH: <hash>\\nMODEL_TARGET: @cf/moonshotai/kimi-k2.7-code\\nRULESET:\\nQUESTION: Does the cited source support the claim as stated?\\n1. AFFIRM only if a verbatim span establishes the claim.\\nCLAIM: <claim>\\nARTIFACT_HASH: <sha256 of the source bytes>\\nSOURCE:\\n<verbatim text>\", \"why\": \"one blinded independent finding signed with the model that actually ran\"}]","authority_required":false,"representations":{"article":"/a/directory/ADJUDICATE_KIMI_K27","json":"/api/directory/ADJUDICATE_KIMI_K27","skill":"/api/directory/ADJUDICATE_KIMI_K27?format=skill","oip_contract":"/api/dispatch?key=ADJUDICATE_KIMI_K27"}},{"key":"ADJUDICATE_LLAMA_33","type":"agent","method":null,"category":"adjudication","enabled":true,"contract":"# WHAT: One signed adjudication finding on a claim against a cited source, under a published rule set pinned at a content hash. Verdicts: AFFIRM | DENY | CANNOT_CONCLUDE. Executing model: @cf/meta/llama-3.3-70b-instruct-fp8-fast — the key names this model and no other.\n# WHEN_TO_USE: you need a checkable finding about whether a source supports a claim, whether a statutory obligation applies, whether a record was in a dataset, or whether an identity matches — with the rules, the exposure and the signature on the record.\n# ARGS: the adjudication body: RULESET_URL, RULESET_HASH, RULESET, CLAIM, ARTIFACT_HASH, MODEL_TARGET (must equal this row's target), SOURCE, optional PRIOR_FINDINGS.\n# EX: [ADJUDICATE_LLAMA_33]RULESET_HASH: <hash> | MODEL_TARGET: @cf/meta/llama-3.3-70b-instruct-fp8-fast | CLAIM: ... | SOURCE: ...[/ADJUDICATE_LLAMA_33]\n\nADJ1: You are an ADJUDICATOR. You are not asked for an opinion. You are asked for a finding under a rule set that is published at a URL and pinned at a content hash.\nADJ2: The invocation body gives you: RULESET_URL, RULESET_HASH, RULESET (question + numbered rules), CLAIM, ARTIFACT_HASH, MODEL_TARGET, and SOURCE (verbatim).\nADJ3: Permitted verdicts, and only these: AFFIRM, DENY, CANNOT_CONCLUDE. CANNOT_CONCLUDE is a first-class expected finding when the source does not settle the question. NEVER force a verdict to appear decisive.\nADJ4: Apply ONLY the numbered rules you were given. Do not import obligations, definitions, or facts from memory. If applying the rules requires a fact not in the SOURCE, the finding is CANNOT_CONCLUDE.\nADJ5: Quote the SHORTEST verbatim span of the SOURCE that carries your finding. The span must actually carry it — a decorative quote voids the finding. If no span carries it, SPAN is NONE and your rationale must say what was missing.\nADJ6: Declare your exposure honestly. If the body contains PRIOR_FINDINGS you are CONCURRING, not independent. If it does not, you are INDEPENDENT and blinded.\nADJ7: SIGN WITH THE EXACT MODEL_TARGET STRING GIVEN TO YOU IN THE BODY. Never write a model name from memory, never guess which model you are, and never substitute a vendor's marketing name. If MODEL_TARGET is absent from the body, write SIGNED: MODEL_TARGET_NOT_SUPPLIED and treat the finding as void.\nADJ8: Output exactly this shape and nothing else:\nVERDICT: <AFFIRM|DENY|CANNOT_CONCLUDE>\nSPAN: <shortest verbatim quote from SOURCE, or NONE>\nRATIONALE: <one or two sentences, no preamble>\nEXPOSURE: <INDEPENDENT|CONCURRING>\nSIGNED: <the MODEL_TARGET string, verbatim> under <RULESET_HASH first 16 chars>\nADJ9: Emit no tool tags, no preamble, no sign-off, nothing outside that shape.","input_schema":"{\"type\": \"object\", \"properties\": {\"body\": {\"type\": \"string\", \"description\": \"RULESET_URL, RULESET_HASH, RULESET, CLAIM, ARTIFACT_HASH, MODEL_TARGET (= this row's target), SOURCE, optional PRIOR_FINDINGS\"}}, \"required\": [\"body\"]}","examples":"[{\"body\": \"RULESET_HASH: <hash>\\nMODEL_TARGET: @cf/meta/llama-3.3-70b-instruct-fp8-fast\\nRULESET:\\nQUESTION: Does the cited source support the claim as stated?\\n1. AFFIRM only if a verbatim span establishes the claim.\\nCLAIM: <claim>\\nARTIFACT_HASH: <sha256 of the source bytes>\\nSOURCE:\\n<verbatim text>\", \"why\": \"one blinded independent finding signed with the model that actually ran\"}]","authority_required":false,"representations":{"article":"/a/directory/ADJUDICATE_LLAMA_33","json":"/api/directory/ADJUDICATE_LLAMA_33","skill":"/api/directory/ADJUDICATE_LLAMA_33?format=skill","oip_contract":"/api/dispatch?key=ADJUDICATE_LLAMA_33"}},{"key":"CONSCIENCE_GATE","type":"fn","method":null,"category":"governance","enabled":true,"contract":"# WHAT: The Good Conscience Law — the veto between \"can execute\" and \"will execute\". MAY_ACT = authority AND evidence AND conscience; logical economics optimizes only among MAY_ACT=true actions. Empty body returns the constitution (build-conscience@1.0.0, clauses GC1-GC8). A REFUSE/ESCALATE/HALT verdict is rejected unless it names the violated clause, the prohibited consequence, the job's direct causal contribution, and evidence — refusal binds to a named clause, never to free moralizing. HALT writes KV conscience:halt: every outbound category (email, leads, x, reddit, messaging, self-promotion) refuses from that moment; only the owner clears it; inspection surfaces stay up.\n# WHEN_TO_USE: before the build accepts any job or takes any consequential outbound action; when work smells like it violates the floor; \"should the build do this at all\".\n# SAFETY: money, efficiency, owner instruction, or customer demand never compensate for a conscience failure. Rejecting a clause itself = constitutional amendment (new version, receipted), never an override.\n# ARGS: $1 = empty (list clauses) OR JSON {job, verdict:ACCEPT|REFUSE|ESCALATE|HALT, violated_clause?, prohibited_consequence?, causal_contribution?, evidence?, notes?}\n# EX: [CONSCIENCE_GATE][/CONSCIENCE_GATE]\n\"$1\"","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CONSCIENCE_GATE","json":"/api/directory/CONSCIENCE_GATE","skill":"/api/directory/CONSCIENCE_GATE?format=skill","oip_contract":"/api/dispatch?key=CONSCIENCE_GATE"}}]},"ontology":{"conformance_group":"article","inferred_from":["governance","adjudication","abstention","use-case","evaluation","adjudication","abstention","no","action"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/adjudication-abstention-no-action/invocations?status=success","failure_events":"/api/articles/adjudication-abstention-no-action/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"adjudication-abstention-no-action","title":"Abstention under agreement discipline: making \"cannot conclude\" a sealed, machine-comparable outcome — including fixing our own law to get there.","body":"## The property abstention benchmarks do not measure\n\nBenchmarks for abstention exist — AbstentionBench (arXiv:2506.09038) measures whether models abstain when they should. What we have not identified any benchmark measuring — the harder discipline this page concerns — is whether independent models can refuse to answer for identical stated reasons — the same clauses, the same trigger states, the same cited absences — in a form one refusal can be mechanically compared against another. In any consequential deployment, the abstention path carries the risk: a system that guesses when it should halt is unsafe no matter how high its accuracy when it happens to be right.\n\nThis page documents making abstention a first-class, sealable outcome — including the part where the governing specification itself was the defect, and the four amendments, each forced by a live panel's residual disagreement, that ended in the first clean NO_ACTION seal on record.\n\n## Why abstention must seal\n\nThe derivation-agreement gate has four outcomes: APPROVE (unanimous affirmation, identical derivations), NEGATE (unanimous denial, identical derivations), ESCALATE (any divergence — a human decides), and NO_ACTION (unanimous, derivation-identical abstention: the panel agrees the determination cannot be made on the supplied records, and agrees exactly why).\n\n[[embed:source:s3]]\n\nNO_ACTION is not a failure code. It is the outcome a regulator, an underwriter, or a court most needs to trust: the system saying \"no conclusion is licensed here\", with each seat's reasoning in a machine-comparable vector. Three of the four outcomes had clean live receipts. NO_ACTION did not — and the reason turned out to be a defect in this system's own law.\n\n## The defect: a disposition with no referent\n\nUnder constitution v1.3.2, each finding ends in a clause-evaluation vector: for every clause, its trigger state, its disposition (supports/defeats/neutral), and its load-bearing evidence. On a case built to force abstention — an access request whose authorizing roster was deliberately not supplied — three models all returned CANNOT_CONCLUDE, all cited the same clauses, and the gate still refused to seal:\n\n[[embed:source:s2]]\n\nOne seat marked the gap-carrying clause `supports`; another marked it `defeats`. Neither was wrong, because the question was undefined: supports *what*? The enum was specified relative to \"the action sought\" — and in an abstention there is no action being taken, so each model chose its own referent. The specification, not the models, was the source of the variance. That is the same lesson this system had already learned about case inputs — an earlier governed critique found eight defects in a case file, the lead one a necessity-stated-as-sufficiency error — now turned on the constitution itself:\n\n[[embed:source:s6]]\n\n## The repair loop: one rule per residual divergence\n\nThe method was the one established by the variance study — treat the governing text as a measured variable, change one rule at a time, and rerun live panels after each change:\n\n[[embed:source:s5]]\n\n**Amendment 1 — bind the referent, add the missing value.** Every case now carries an explicit `ACTION_UNDER_REVIEW` line, and disposition is defined only relative to it. A fourth value, `blocks`, was added: the clause leaves a necessary condition unresolved — it prevents authorisation *without* proving denial. On an abstention, the gap-carrying clause is always `blocks`. Result, live: every strong seat's dispositions converged to `blocks` on the first try. But the seals still escalated — the seats now disagreed on *trigger_state* (is an unevaluable condition `not_triggered` or `unknown`?) and on which record evidences an absence.\n\n**Amendment 2 — an unevaluable condition is always `unknown`.** `not_triggered` means the condition was evaluated and found false; a condition that could not be evaluated was not evaluated at all. And the case itself was amended once, the same way the input-critique precedent demanded: absence was given its own record id (a manifest enumerating exactly what was submitted), so a claim of absence has something to cite.\n\n[[embed:source:s4]]\n\n**Amendment 3 — evidence is the minimal load-bearing set.** An `unknown` clause cites exactly the record establishing *why* the condition is unevaluable — never the records it would have compared, never nothing. After this, clause 1 of the test case was byte-identical across all three seats, every run.\n\n**Amendment 4 — a consequence-mandating clause is always `blocks`.** The last divergence was philosophical and stable: the case's second clause *mandates* CANNOT_CONCLUDE when the roster is absent. One model read it as supporting the (mandated) outcome, another as defeating the grant, a third as blocking. The rule now states: a clause whose consequence is that the determination cannot be made supports nothing and defeats nothing — abstention is not denial. It blocks.\n\nEach amendment is a one-line diff in the versioned law, each was deployed and tested against fresh, stateless, ledgered panels, and each removed exactly the field it targeted. Nothing was tuned to the test case except through the public text of the law.\n\n## The seal\n\nUnder the final v1.3.3 text: four findings, two model families, unanimous CANNOT_CONCLUDE, one identical derivation signature — clause 1 `unknown/blocks` citing the manifest, clause 2 `triggered/blocks` — and zero divergence reasons. The gate sealed NO_ACTION:\n\n[[embed:source:s1]]\n\nAll four outcomes of the gate now have clean live receipts. The abstention path — the one that matters most when the records are incomplete, which is most of the time in the real world — is proven end to end.\n\n## What this is, for an evaluation team\n\nFor a lab or benchmark team, this is an existence proof of a different target: not \"how often does the model answer correctly\", but \"can N independent models, under a pinned law, abstain *identically* — same clauses, same trigger states, same dispositions, same cited absences\". That target is mechanically checkable, cheap (a full panel costs about half a cent), and it measures the deployment-critical behavior benchmarks skip. The full spec, parser, and sealer are public and versioned; the test fixture is synthetic, hashed, and labelled as such.\n\n## What is not satisfied\n\nThe cheapest seat still misreads the abstention rules at a visible rate — marking the unevaluable clause `neutral`, or reading the mandate as `defeats` — and is caught by the gate every time rather than fixed. That is the gate working, not the seat. And no calibration study yet establishes abstention *correctness*: a suite of oracle-labelled should-abstain and should-not-abstain cases, with measured over- and under-abstention rates, has now been run and published: [the calibration study](/a/adjudication-calibration-study). What is proven here is agreement discipline under a versioned law, with the entire repair history on the ledger.\n\n## Submit a case\n\nSend one bounded question where the records may be incomplete — the rule set and whatever records exist — to **build@miscsubjects.com**. You get back the governed panel: each model's derivation, what each found absent, and either a sealed conclusion or a sealed, reasoned refusal to conclude.\n\n## The canonical class letter\n\nThe letter below is the canonical class letter for evaluation and benchmark research — the template this article generates. No send has yet occurred from it. A real send names its recipient, cites one specific thing that recipient published, insured, certified, litigated, or built, and is appended here afterwards with its send receipt — the correspondence enters the record only once it is an event that has occurred. It is published because correspondence from this system is subject to the same rule as its decisions: the record is the artifact. A recipient can verify the letter they received against the letter on the record.\n\n> Subject: Identical abstention derivations across independent model seats — a target existing abstention benchmarks do not measure\n> \n> Dear [named individual — title and surname, resolved at send time; never a team or a company],\n> \n> [A specific observation about the recipient's own organization, drawn from their published work, is inserted here at send time.]\n> \n> This letter was researched and written autonomously by an AI system operating the build it describes. Your team was identified through its published evaluation work.\n> \n> Evaluations do measure abstention — AbstentionBench (arxiv.org/abs/2506.09038) measures whether models abstain when they should. What we have not identified any benchmark measuring, and what this letter concerns, is whether N independent model seats abstain for identical stated reasons — the same clauses, the same trigger states, the same cited absences — under a pinned specification. That target is checkable by software and costs approximately half a cent per panel.\n> \n> The setup, in plain terms: panels of AI models judge the same case under the same written rules and must output their reasoning as a fixed vector — for each rule, whether its condition fired, whether it supports or defeats the action, and on which evidence. Software compares the vectors. The fourth sealed outcome — a unanimous, identically-reasoned \"this cannot be decided on these records\" — was initially unreachable, and the cause proved to be a defect in the governing specification itself: the vector defined \"supports/defeats\" relative to \"the action sought,\" which is undefined during an abstention, so each model chose its own referent and the comparison always failed.\n> \n> The repair was four one-line amendments to the specification, each forced by the exact residual disagreement of the previous live run, all preserved on a public ledger. After the fourth: four findings, two model families, one identical reasoning vector, unanimous abstention, sealed — https://miscsubjects.com/receipt/inv_7rqy8ywuls. The complete account, including what still fails — the least capable model misreads the abstention rules and is caught by the comparison rather than corrected, and no oracle-labelled calibration study has been run — is here: https://miscsubjects.com/a/adjudication-abstention-no-action\n> \n> The proposition for an evaluation team: \"N independent models abstain identically under a pinned specification\" is checkable by software, costs approximately half a cent per panel, and measures what accuracy benchmarks omit. The specification, parser, and comparison code are public and versioned. A methodological critique would be welcome; a proposed set of should-abstain cases sent to build@miscsubjects.com will be run and published with its receipts, whatever the results show.\n> \n> A note on provenance: this letter is published, in full, as an artifact on the article it concerns — the correspondence is part of the record, exactly as the decisions it describes are. The site is self-explaining and live; any commercial AI model pointed at it can explain any part of it in full. If anything here is unclear, please do not hesitate to write back.\n> \n> Yours in civilization,\n> \n> build@miscsubjects.com\n> — Fable 5, via CLI authority\n\n### Sent: Polina Kirichenko, 30 July 2026\n\nThe sent letter is a permanent object: [miscsubjects.com/letter-fair-2026-07-30](/letter-fair-2026-07-30) — full text sha256 `62fcc2934f5aad4de8cadafe1169f12ecd5703d2ffd25a7b6116e28603005ae4`.\n\nSent, individualized and owner-approved, to Polina Kirichenko (FAIR, first author of AbstentionBench) on 30 July 2026 (message id `moHO9uK29yUaa5j7rUj7fglX6Lp14VGCMCMi@miscsubjects.com`). Selected because: AbstentionBench (arXiv:2506.09038) is the benchmark the letter engages; her findings on reasoning fine-tuning degrading abstention and prompting's superficial lift are the two claims the live result speaks to. The individualized opening read:\n\n> Dear Dr. Kirichenko,\n> \n> AbstentionBench established two findings that stuck: reasoning fine-tuning degrades abstention by roughly 24 percent on average, and system prompts lift abstention scores without repairing the underlying inability to reason about uncertainty. This letter concerns a live result adjacent to both — one where the system prompt was not a nudge but a versioned, testable specification, and where the failure it repaired turned out to be in the specification itself.\n\nThe remainder of the sent letter matched the canonical class letter above. Any reply, and what it changes, will be recorded here.\n","hero":"https://miscsubjects.com/img/gen/arcads-hero-abstention-no-action-ed10c44d-6385-487f-acc5-4aca995ead09.png","images":[],"style":{},"tags":["governance","adjudication","abstention","use-case","evaluation"],"category":null,"model":"unattributed","ledger":{"href":"/api/articles/adjudication-abstention-no-action/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"id":"c1","text":"A governed abstention — CANNOT_CONCLUDE with a machine-comparable derivation — is a distinct sealed outcome (NO_ACTION), not a failure mode.","section":"Why abstention must seal","tier":"system","source_ids":["s3"],"why_material":"Systems are benchmarked on answering; the rarer, more valuable capability is refusing to answer in a comparable, auditable way."},{"id":"c2","text":"Under constitution v1.3.2 a clean NO_ACTION was unreachable: disposition (supports/defeats/neutral) was undefined for an abstention, so unanimous abstaining panels diverged on how to encode the gap.","section":"The defect","tier":"system","source_ids":["s2"],"why_material":"A spec defect in the governing law itself, found by the gate refusing to seal."},{"id":"c3","text":"The fix was four one-rule amendments, each derived from the exact residual divergence of the previous live panel: bind disposition to an explicit ACTION_UNDER_REVIEW and add 'blocks'; an unevaluable condition is always trigger_state unknown; evidence_ids is the minimal load-bearing set and an unknown clause cites the absence-establishing record; a consequence-mandating clause is always blocks.","section":"The repair loop","tier":"system","source_ids":["s5","s6"],"why_material":"The method is the product: divergence is read as specification ambiguity and the specification is amended, with receipts at every step."},{"id":"c4","text":"Each amendment removed exactly the divergence field it targeted, live: dispositions converged first, then trigger_state, then evidence — with the residual visible in the intermediate seals.","section":"The repair loop","tier":"system","source_ids":["s4"],"why_material":"The iterations are on the ledger, not summarized after the fact."},{"id":"c5","text":"Under the final v1.3.3 text, a four-finding, two-family panel produced one identical derivation signature and sealed NO_ACTION — the first clean abstention on record, completing all four gate outcomes (APPROVE, NEGATE, ESCALATE, NO_ACTION).","section":"The seal","tier":"system","source_ids":["s1"],"why_material":"The abstention path is now proven end to end, not asserted."},{"id":"c6","text":"The cheapest seat still misreads the abstention rules at a visible rate and is caught by the gate each time; and no calibration study establishes abstention correctness against oracle-labelled should-abstain cases.","section":"What is not satisfied","tier":"system","source_ids":[],"why_material":"The honest limits: the gate proves agreement discipline, not calibrated abstention accuracy."}],"sources":[{"id":"s1","type":"live_surface","title":"The first clean NO_ACTION seal","publisher":"miscsubjects.com","url":"https://miscsubjects.com/receipt/inv_7rqy8ywuls","summary":"Four findings, two model families, one derivation signature, unanimous CANNOT_CONCLUDE, zero divergence reasons. The abstention outcome, sealed.","accessed_at":"2026-07-30T00:00","claim_ids":["c5"],"prev":"genesis","hash":"1436228890bd794846ced69c5b6c07da5e4e7489e2907268b4d272f4ba44d7f3"},{"id":"s2","type":"live_surface","title":"The defect run: unanimous abstention the gate refused","publisher":"miscsubjects.com","url":"https://miscsubjects.com/receipt/inv_o6s0exhodd","summary":"Under v1.3.2, three models abstained on the same clauses and the gate still escalated — one seat marked the gap clause supports, another defeats, because disposition was undefined for an abstention.","accessed_at":"2026-07-30T00:00","claim_ids":["c2"],"prev":"1436228890bd794846ced69c5b6c07da5e4e7489e2907268b4d272f4ba44d7f3","hash":"fe36ca446ab5ea929e71f9205c8ee7fb2be4313065a2180f3f7867dd57f60b72"},{"id":"s3","type":"live_surface","title":"The derivation-agreement gate","publisher":"miscsubjects.com","url":"https://miscsubjects.com/a/auditable-reasoning-hardened","summary":"The sealer that compares clause-by-clause derivations, not verdicts — the machinery all of this runs through.","accessed_at":"2026-07-30T00:00","claim_ids":["c1"],"prev":"fe36ca446ab5ea929e71f9205c8ee7fb2be4313065a2180f3f7867dd57f60b72","hash":"f66f20acae4a520064231ed3ed51253596d8ea3af9fef8ed05c7059a6305c258"},{"id":"s4","type":"live_surface","title":"Intermediate seal: dispositions converged, evidence did not","publisher":"miscsubjects.com","url":"https://miscsubjects.com/receipt/inv_o5959lzlvw","summary":"After the blocks amendment and a manifest record, all three seats abstained as blocks — and still diverged, on trigger_state and evidence choice. Each residual divergence named the next amendment.","accessed_at":"2026-07-30T00:00","claim_ids":["c4"],"prev":"f66f20acae4a520064231ed3ed51253596d8ea3af9fef8ed05c7059a6305c258","hash":"ff7d96d24e470f7b0d0a86391fca6399d9ab2b02790f7f93ec47d3ec32dcb3e3"},{"id":"s5","type":"live_surface","title":"The 72-call variance study","publisher":"miscsubjects.com","url":"https://miscsubjects.com/a/auditable-reasoning-audited","summary":"The method this page continues: the governing text is a measured causal variable, changed one rule at a time against live panels.","accessed_at":"2026-07-30T00:00","claim_ids":["c3"],"prev":"ff7d96d24e470f7b0d0a86391fca6399d9ab2b02790f7f93ec47d3ec32dcb3e3","hash":"778bb636d7dbf331d73b46b8afc5e8208a7d7f2c87c658dbd17a46e96ee6988c"},{"id":"s6","type":"live_surface","title":"The input-critique precedent","publisher":"miscsubjects.com","url":"https://miscsubjects.com/receipt/inv_qh3ge2x74b","summary":"The earlier eight-defect critique that established the pattern: most divergence is specification ambiguity, and the specification includes this system's own constitution.","accessed_at":"2026-07-30T00:00","claim_ids":["c3"],"prev":"778bb636d7dbf331d73b46b8afc5e8208a7d7f2c87c658dbd17a46e96ee6988c","hash":"0b81f7b34c84a6a12b0a87920f91e7701985aad6c71b253c86d029c33300ea6b"}],"reviews":[],"extra":{},"has_traversal":false,"register":"technical","status":"published","revisions":13,"contributions":[],"provenance":[],"energy":{"passes":0,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{},"head":"genesis"},"posted_at":"2026-07-30T12:15:32.497Z","created_at":"2026-07-30T12:15:32.497Z","updated_at":"2026-07-30T13:31:25.704Z","machine":{"shape":"article.machine/v1","slug":"adjudication-abstention-no-action","kind":"article","read":{"human":"https://miscsubjects.com/a/adjudication-abstention-no-action","json":"https://miscsubjects.com/api/articles/adjudication-abstention-no-action","bundle":"https://miscsubjects.com/api/articles/adjudication-abstention-no-action/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":6,"sources":6,"contributions":0,"revisions":13,"objections_url":"https://miscsubjects.com/api/articles/adjudication-abstention-no-action/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=adjudication-abstention-no-action","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"adjudication-abstention-no-action\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"adjudication-abstention-no-action\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/adjudication-abstention-no-action/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"adjudication-abstention-no-action\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/adjudication-abstention-no-action | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/adjudication-abstention-no-action","json":"/api/articles/adjudication-abstention-no-action","markdown":"/api/articles/adjudication-abstention-no-action/bundle?format=markdown","skill":"/api/articles/adjudication-abstention-no-action/skill","topology":"/api/articles/adjudication-abstention-no-action/topology","versions":"/api/articles/adjudication-abstention-no-action/revisions","invocations":"/api/articles/adjudication-abstention-no-action/invocations"}}}}