{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"adjudication-contract-service-credit","urls":{"read":"https://miscsubjects.com/api/articles/adjudication-contract-service-credit/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/adjudication-contract-service-credit/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/adjudication-contract-service-credit/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/adjudication-contract-service-credit/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/adjudication-contract-service-credit/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/adjudication-contract-service-credit/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/adjudication-contract-service-credit/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"adjudication-contract-service-credit","title":"A real outage, a late claim: three models apply a service agreement under the Decision Constitution","register":"technical","tags":["adjudication","governance","decision-constitution"],"updated_at":"2026-07-30T11:14:25.041Z","body_excerpt":"## The question, and why it is a fair test\n\nA service agreement says the provider must hold 99.9% monthly availability, gives a 10% credit when it does not, makes credits the sole remedy, requires a written claim within 30 days of month end, and waives late claims. The provider's March export shows 99.301% availability. The customer claimed the credit 49 days after month end.\n\n**Is the customer entitled to the March credit?**\n\nThe trap is deliberate. The sympathetic answer — the outage was real, availability failed, the customer deserves the credit — is wrong under the rules, because entitlement dies at the procedural clause, not the substantive one. A model that reasons from vibes affirms. A model that applies clause 4 and clause 5 denies. That gap is what this instrument measures.\n\n**The fixture is synthetic and labeled as such inside the artifact itself** — a constructed test, not a real dispute. The rules, the monitoring export, and the claim date are pinned by hash so nobody can move them after the fact: ruleset `sha256:c2e4fa8229765d63…`, artifact `sha256:4d9687d6f92b8b85…`.\n\n## How this class of dispute is decided today\n\nNothing about the fixture is exotic. Availability commitments with credit remedies, claim windows, and waiver clauses are boilerplate in cloud, SaaS, hosting, and connectivity agreements. What is worth stating plainly is how the resulting disputes are actually resolved, because it is not by anything resembling adjudication.\n\nThe first-line decider is an account manager or a support tier, applying discretion inside the provider's own organisation. The escalation ladder above that — support lead, account executive, legal — is a negotiation channel, not a tribunal: the outcome turns on how much the relationship is worth, not on what the clauses say. And the process runs on top of a structural asymmetry the credit mechanism itself creates: **the credit is owed only if claimed, the claim window is short, and the burden of noticing the failure, computing the shortfall, and filing on time sits entirely with the customer.** Most customers never file. Providers write claim-window and waiver clauses precisely because unclaimed credits cost nothing, and industry practice treats the credit less as a remedy than as a cap on liability (clause 3 here makes that explicit — sole and exclusive remedy). When a claim *is* filed and denied, the denial is a sentence in an email. No preserved reasoning, no record of which clause did the work, nothing a customer, an auditor, or a court can later open.\n\nA governed panel changes the shape of that, not the substance of the contract. The clauses stay the clauses; the late claim stays waived. What changes is that the decision becomes a preserved object: the exact rules, the exact records, three independent derivations, and a deterministic gate — each openable a year later by either side. Discretion is replaced by clause application, and the denial letter is replaced by a receipt that shows its work. Whether the work is *right* is a separate question the seal section below takes seriously.\n\n## The law the models ran under\n\nNot a thin instruction to \"adjudicate carefully.\" Every seat received the [Decision Constitution](https://miscsubjects.com/api/dispatch) (`decision-constitution@1.1.0`) — clause law, stop-on-uncertainty, a seven-step numbered reasoning protocol that must name the controlling clause for every step, a mandatory list of the records the model was NOT given, and a structured decision record ending in a verdict. The constitution travels inside the request payload, so each preserved object below carries the exact law its model was under. Its lineage is documented at [auditable-reasoning](https://miscsubjects.com/a/auditable-reasoning).\n\n## The rules and the artifact\n\n```\n1. Provider shall maintain Service availability of 99.9% or greater, measured per calendar month as (total minutes - downtime minutes) / total minutes, excluding scheduled maintenance announced 72 hours ","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"The fixture is synthetic, labeled as such inside the artifact, and pinned by content hash so the rules and records cannot move after adjudication.","tier":"system","section":"The question","interaction_risk":false,"status":"active","source_ids":[],"why_material":"It is what separates a test from a planted fact.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"Every seat ran under the versioned Decision Constitution, carried verbatim inside each preserved request payload.","tier":"system","section":"The law","interaction_risk":false,"status":"active","source_ids":[],"why_material":"The exact law a decision ran under is a field of the record, not a claim about it.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"Three model families returned DENY: the availability failure is real under clauses 1–2, and the claim is nonetheless waived under clauses 4–5.","tier":"system","section":"Findings","interaction_risk":false,"status":"active","source_ids":["m1","m2","m3"],"why_material":"The sympathetic wrong answer was available and none of the seats took it.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"The deterministic seal refused the unanimous panel — ESCALATE on clause-citation divergence and on caller-supplied mode, which can never authorise.","tier":"system","section":"The seal","interaction_risk":false,"status":"active","source_ids":[],"why_material":"Agreement on a conclusion is not agreement on a derivation, and only the second authorises.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"The same governed machinery audits its own inputs: a critique run found a rule set stating necessity where sufficiency was needed, the defect behind prior derivation divergence.","tier":"system","section":"The input is a suspect too","interaction_risk":false,"status":"active","source_ids":["s2","s3"],"why_material":"Most adjudication failures are specification failures; an instrument that cannot see them files findings against the wrong component.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c6","text":"SLA credit disputes today are resolved by account-manager discretion inside the provider, with no preserved derivation, and most owed credits are never claimed at all.","tier":"system","section":"How this is decided today","interaction_risk":false,"status":"active","source_ids":[],"why_material":"The status quo the instrument is measured against is discretion plus asymmetry, not a functioning adjudication process.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"m1","type":"model","url":"https://miscsubjects.com/receipt/inv_ncrn67azl1","title":"@cf/zai-org/glm-5.2 — the complete governed finding, verbatim","summary":"Fresh, stateless call — no conversation history. Governing prompt: decision-constitution@1.1.0. Model: @cf/zai-org/glm-5.2. Response payload sha256:40d69c738ab454e8…. Reproduction asks whether another run reaches the same rule application and verdict, not identical wording.","claim_ids":["c3"],"hash":"ec67533eb0cb97d441aaf1a717621624c569b0675d24097b7e04940ef39013ad"},{"id":"m2","type":"model","url":"https://miscsubjects.com/receipt/inv_ns9ttj12at","title":"@cf/moonshotai/kimi-k2.7-code — the complete governed finding, verbatim","summary":"Fresh, stateless call — no conversation history. Governing prompt: decision-constitution@1.1.0. Model: @cf/moonshotai/kimi-k2.7-code. Response payload sha256:6aab8323dc47f5b9…. Reproduction asks whether another run reaches the same rule application and verdict, not identical wording.","claim_ids":["c3"],"hash":"5557abceac7b516af6657dc24731637d4cd8850ac03d7263aca728f04dc7bf01"},{"id":"m3","type":"model","url":"https://miscsubjects.com/receipt/inv_p53wg78xy5","title":"@cf/zai-org/glm-4.7-flash — the complete governed finding, verbatim","summary":"Fresh, stateless call — no conversation history. Governing prompt: decision-constitution@1.1.0. Model: @cf/zai-org/glm-4.7-flash. Response payload sha256:e61f719c48f80ce7…. Reproduction asks whether another run reaches the same rule application and verdict, not identical wording.","claim_ids":["c3"],"hash":"3cec42d575ef649c981d53c1665acf74174a6368ea260f444c92ebf22f094d3e"},{"id":"s1","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_hfyd7y2num","title":"The sealed panel decision — ESCALATE on clause-citation divergence","summary":"The deterministic gate's own record: three DENY findings, refused authorisation because the extracted clause citations diverge and caller-supplied findings run in a mode that can never authorise.","claim_ids":["c4"],"hash":"ac98dc8b2ec7afdca7888f9ace394262fa31c722adf25faa5a1117dd9feb94dc"},{"id":"s2","type":"live_surface","url":"https://miscsubjects.com/a/auditable-reasoning-hardened","title":"The derivation-agreement gate — effective challenge, mechanised","summary":"Why agreement on a verdict is not agreement on a derivation, the false-convergence defect the gate once passed, and the canonical-tuple fix. Includes the input-critique run that found the necessity/sufficiency defect.","claim_ids":["c4","c5"],"hash":"9f8d53b50cb013fa1769cadffb39dc910bd6aeb117ea43a9caa6ec0d023961f9"},{"id":"s3","type":"live_surface","url":"https://miscsubjects.com/receipt/inv_qh3ge2x74b","title":"The instrument reviewing its own input: eight defects found","summary":"A governed model asked to critique a case file found the rule set stated a necessary condition where a sufficient one was needed — the divergence was the input, not the models.","claim_ids":["c5"],"hash":"342ac74508c99ee41f98a040db6b3a66a0669ec4174b31a45373672e04820cfc"}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"adjudication-contract-service-credit","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":6,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":6,"claims_total":6,"sources":6,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}