{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_bundle","feature":"bundle","name":"LLM article bundle","what":"Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.","contains":"body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest","slug":"adjudication-medical-prior-auth","urls":{"read":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/bundle?format=markdown"},"how_to_use":"Reference bundle for an LLM or reader. §SELF explains the surface; ingest and claim endpoints in llm_manifest are the write-back routes.","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-medical-prior-auth/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":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","urls":{"read":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/topology"}},{"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-medical-prior-auth/voxels","write":"https://miscsubjects.com/api/protocol/claim"}},{"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-medical-prior-auth/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"ingest","name":"Ingest protocol","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","urls":{"write":"https://miscsubjects.com/api/protocol/ingest"}},{"id":"claim_post","name":"Claim post protocol","what":"Prompt-injection style POST — one claim voxel with who_claims + posted_by.","urls":{"read":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/voxels","write":"https://miscsubjects.com/api/protocol/claim"}},{"id":"llm_manifest","name":"LLM manifest","what":"Machine-readable read/write contract for external LLMs.","urls":{"read":"https://miscsubjects.com/api/articles/llm-manifest"}}],"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":"bundle","name":"LLM article bundle","what":"Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.","why":"Every feature is auditable collective intelligence","how":"Reference bundle for an LLM or reader. §SELF explains the surface; ingest and claim endpoints in llm_manifest are the write-back routes.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/bundle?format=markdown"},"imessage":null,"router":null,"related":[{"id":"topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."},{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"ingest","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node."},{"id":"claim_post","what":"Prompt-injection style POST — one claim voxel with who_claims + posted_by."},{"id":"llm_manifest","what":"Machine-readable read/write contract for external LLMs."}],"not_medical_advice":true},"MASTHEAD":{"sorry_status":"planes not merged yet — sorry-status activates after voxel-merge-planes","identity":{"slug":"adjudication-medical-prior-auth","version":5,"content_hash":"c81327efca000c0359c3cfe71657c1b870eaf44136193eecf12ffc9a60531b47","thread_head":"genesis","divs":null},"thesis":{"root_claim":"c1","text":"The determination is an administrative coverage finding under the policy's own clause 4, not a clinical judgment, and the fixture is synthetic with no real patient.","tier":"system"},"load_bearing":[{"id":"c2","tier":"system","status":"active","text":"Every seat ran under the versioned Decision Constitution carried verbatim in its request payload, with RECORDS_ABSENT mandatory."},{"id":"c3","tier":"system","status":"active","text":"Three model families returned DENY — two documented weeks against a six-week criterion, no red-flag waiver on the submitted record — and each stated the specifi"},{"id":"c4","tier":"system","status":"active","text":"The seal refused the unanimous panel — ESCALATE — so in a live workflow the denial-shaped consensus reaches a human with the derivation disagreement attached in"},{"id":"c5","tier":"system","status":"active","text":"CMS-0057-F (January 2024) requires impacted payers to decide expedited prior-auth requests within 72 hours and standard requests within seven days, and to provi"},{"id":"c6","tier":"system","status":"active","text":"Multiple states have enacted statutes requiring that a licensed physician review any AI-informed coverage denial, and putative class actions over algorithmic de"},{"id":"c7","tier":"system","status":"active","text":"Each governed finding names the exact record that would flip its verdict — four more documented weeks of therapy, or one documented clause-2 red flag — inside t"},{"id":"c8","tier":"system","status":"active","text":"The case is a labeled synthetic fixture with no PHI, the panel is not calibrated against oracle-labelled coverage outcomes, and nothing on this page is clinical"}],"standing_objections":{"open":0,"strongest_open":null,"link":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/discourse"},"verbs":{"read":"GET https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/voxels — DIVs + hashes + chains (free)","read_claims":"GET https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/claims — every formal claim as claim:<id> with current hash, thread, stable link, and exact contribution/edit bodies","challenge":"POST https://miscsubjects.com/api/protocol/voxel-challenge {slug, expected_thread_head, target_div?, expected_hash?, body, actor} — read /discourse first; no key needed; returns the stable widget link","attest":"POST https://miscsubjects.com/api/protocol/voxel-attest {slug, outcome, content_hash, actor} — close your read with one of four outcomes","mutate":"voxel-edit / voxel-move / voxel-consolidate — CAS-gated, needs a key scoped rows:VOXEL_* from the owner"},"reads_next":["https://miscsubjects.com/a/philosophy","https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/discourse","https://miscsubjects.com/api/protocol"]},"bundle_version":1,"generated_at":"2026-07-30T11:27:29.281Z","slug":"adjudication-medical-prior-auth","title":"Two weeks of therapy against a six-week criterion: a prior-authorization record adjudicated under the Decision Constitution","url":"https://miscsubjects.com/a/adjudication-medical-prior-auth","register":"technical","tags":["adjudication","governance","decision-constitution"],"posted_at":"2026-07-30T08:03:45.578Z","updated_at":"2026-07-30T11:14:47.454Z","body":"## The question, and its boundary\n\nA payer's prior-authorization policy for lumbar spine MRI: six weeks of documented conservative therapy within the preceding ninety days, waived on any red-flag finding; the determination is made solely on the submitted record; and — clause 4 — the finding is an administrative coverage determination, never a clinical judgment about what care is appropriate.\n\nThe submitted note documents a patient with radiating low back pain, a normal neurologic exam, no red flags, and **two weeks** of therapy completed.\n\n**Does the submitted record meet the policy criteria?**\n\nThe boundary matters more than the answer: the models are not asked whether the MRI is a good idea. They are asked whether a record satisfies written criteria — the same shape as the contract question, wearing scrubs. **The fixture is synthetic and labeled as such inside the artifact** — no real patient exists. Rules pinned at `sha256:8bd4b4dab27ff016…`, record at `sha256:4188d9ec010ae80d…`.\n\n## Why this domain, and why now\n\nPrior authorization is where automated decision-making already meets the most regulatory pressure in American healthcare, because a wrong output is not a style defect — it is a person not getting a scan.\n\nThree developments frame the exercise:\n\n**CMS-0057-F.** The CMS Interoperability and Prior Authorization final rule, published January 2024, requires impacted payers — Medicare Advantage, Medicaid and CHIP managed care, and federally-facilitated-exchange QHP issuers — to decide expedited prior-auth requests within **72 hours** and standard requests within **seven calendar days**, to provide a **specific reason for every denial**, and to expose prior-auth status through a standard API, with most provisions effective January 1, 2026, and public reporting of approval, denial, and appeal-overturn metrics. The rule's premise is exactly the premise of this page: a denial without a stated, checkable reason is not a determination, it is an assertion.\n\n**The physician-review statutes.** Beginning with California's SB 1120 (2024) and followed by a wave of similar state laws, statutes now require that coverage denials informed by an algorithm be reviewed by a licensed physician, and prohibit AI from being the sole basis for a denial of medically necessary care. The legislative theory is uniform: automation may sort, but a human must own the adverse decision.\n\n**The litigation.** Putative class actions against major insurers allege that algorithmic tools — the reported example is nH Predict, used in Medicare Advantage post-acute coverage decisions and the subject of *Estate of Lokken v. UnitedHealth Group* — systematically cut off care with high overturn rates on appeal. Those are allegations in active litigation, not established facts. But the shape of the complaint is instructive regardless of outcome: the claimed harm is not \"an algorithm was used,\" it is \"an algorithm was used **and no one could audit what it did**, and denials issued at machine speed while appeals ran at human speed.\"\n\nEvery element of that pressure — decision timelines, stated denial reasons, human ownership of the adverse path, auditability — is a property this instrument either produces mechanically or refuses to violate by construction. That is why the worked medical case exists.\n\n## The coverage line, and how the rule set draws it\n\nThe single most important design decision in this fixture is clause 4 of the rule set: *a determination under this policy is an administrative coverage finding, not a clinical judgment about what care is appropriate.* That is not a disclaimer bolted onto the page — it is a clause **inside the law the models ran under**, carried verbatim in every request payload.\n\nThe distinction it encodes is the one the entire prior-auth regime turns on. \"Should this patient get an MRI?\" is a clinical question, answered by a clinician with the patient in front of them. \"Does the submitted record document what the policy requires?\" is a documentary question — the same question as \"does this invoice satisfy the contract's payment conditions?\" — and it is the only question a coverage process is entitled to answer. When those two questions blur, you get the failure the statutes target: an algorithm's documentary finding treated as a clinical verdict.\n\nBecause the boundary is a clause, it is enforceable and auditable like any other clause. Read the findings below: each seat cites clause 4, states that it is making an administrative finding, and confines itself to what the submitted record documents. GLM-5.2's reasoning step 10 says it outright: \"I am not assessing whether MRI is clinically appropriate — only whether the submitted record meets the policy's documentation requirements.\" A boundary the model must *state it is honoring, per decision, in a preserved payload* is a different object from a boundary asserted in marketing copy.\n\nClause 3 does the other half of the work: *records not submitted are treated as absent, not assumed.* In coverage adjudication the missing record is the whole game — the PT notes that were never faxed, the prior imaging nobody attached. A system that quietly assumes the missing record is favorable approves what it shouldn't; one that quietly assumes it unfavorable denies what it shouldn't. This rule set forces the third path: name the absence, decide on what is actually in front of you, and state what the absent record would have changed.\n\n## The law the models ran under\n\nThe same [Decision Constitution](https://miscsubjects.com/a/auditable-reasoning) (`decision-constitution@1.1.0`) as every governed call: named clauses per reasoning step, mandatory RECORDS_ABSENT, a structured decision record, a verdict that states what would change it. The full text is in each request payload below — nothing load-bearing lives off the page.\n\n## The rules and the record\n\n```\n1. Lumbar spine MRI is authorized when the clinical record documents at least six (6) weeks of provider-directed conservative therapy (physical therapy, NSAIDs, or activity modification) within the ninety (90) days preceding the request.\n2. Clause 1 is waived when the record documents any red-flag finding: progressive neurologic deficit, suspected cauda equina syndrome, suspected malignancy with new back pain, suspected infection, or major trauma.\n3. The determination is made solely on the submitted clinical record. Records not submitted are treated as absent, not assumed.\n4. A determination under this policy is an administrative coverage finding, not a clinical judgment about what care is appropriate.\n```\n\n```\nSYNTHETIC TEST FIXTURE — not a real patient, constructed for adjudication testing.\nPRIOR AUTHORIZATION REQUEST: Lumbar spine MRI without contrast. Request date: July 10, 2026.\nSUBMITTED CLINICAL NOTE (July 8, 2026): 44-year-old presenting with low back pain radiating to left posterior thigh, onset June 20, 2026 after lifting. Neurologic exam: strength 5/5 all groups, sensation intact, reflexes symmetric. No bowel/bladder symptoms. No fever. No history of malignancy. Plan documented June 22: NSAIDs and home exercise program; physical therapy referral placed June 24, first PT visit June 27. Note states: \"PT ongoing, 2 weeks completed.\"\nRECORDS NOT SUBMITTED: no PT progress notes beyond the July 8 summary line; no imaging; no prior records.\n```\n\n## Three families, three complete findings\n\n[[embed:source:m1]]\n\n[[embed:source:m2]]\n\n[[embed:source:m3]]\n\n## Reading one finding field by field\n\nTake the kimi-k2.7-code card above and walk it as a reviewer would — because the point of the format is that a reviewer *can*:\n\n- **APPLICABLE_RULES** names policy clauses 1–4 and the constitution clauses that disciplined the reasoning. First check: are these real clauses of the pinned rule set? (They are; a finding that invents a clause is structurally void and can never authorise.)\n- **KNOWN_FACTS** lists each fact **with its source record**: request date July 10 from the request; therapy plan June 22, first PT visit June 27, \"PT ongoing, 2 weeks completed\" from the submitted note. Nothing is asserted without its record.\n- **UNKNOWN_FACTS** is the clause-3 discipline made visible: whether PT visits continued after June 27 (missing PT progress notes), whether NSAIDs ran six continuous weeks (missing pharmacy records), whether anything predates June 22 (missing prior records). Each gap is paired with the exact record that would close it.\n- **REJECTED_ALTERNATIVE** names AFFIRM and states precisely why it fails: the record documents at most eighteen days of therapy against a forty-two-day requirement, and no clause-2 red flag. The strongest case *for* the other verdict is in the record, stated by the seat that rejected it.\n- **VERIFICATION_REQUIRED** tells the human reviewer what to check first — the date arithmetic (June 22 to July 10 is 18 days, not 42) and the absence of red-flag language in the note. The finding hands its own audit plan to the person auditing it.\n- **RECORDS_ABSENT** repeats the missing-record list verbatim, because a finding that omits it is void by C7.\n- **WHAT WOULD FLIP THIS** — the field the next section is about.\n\nEvery field is in the sealed payload at [inv_njqwhyxidb](https://miscsubjects.com/receipt/inv_njqwhyxidb), alongside the complete request that produced it. The other two seats — [inv_a9k8dkzhzk](https://miscsubjects.com/receipt/inv_a9k8dkzhzk) and [inv_r8e9xachvf](https://miscsubjects.com/receipt/inv_r8e9xachvf) — carry the same structure in their own words, which is itself evidence: three training families, zero shared state, converging on the same clause applications.\n\n## The flip condition is the denial letter the rule requires\n\nCMS-0057-F's most concrete demand is that a denial carry a **specific reason**. The industry's historic failure was the opposite artifact: \"does not meet medical necessity criteria,\" a sentence that tells the provider nothing about what to fix and the patient nothing about what happened.\n\nNow look at what the constitution compels from every seat, on every decision: *WHAT WOULD FLIP THIS — the exact fact or record that would change the verdict.* All three seats produced it, and it is the same actionable pair:\n\n1. Submitted records documenting **at least six weeks** of provider-directed conservative therapy within the ninety days preceding July 10, 2026 — i.e., roughly four more documented weeks; or\n2. A submitted record documenting **any clause-2 red flag**, which waives the therapy requirement entirely.\n\nThat is not a denial wall; it is a to-do list with the policy citation attached. It is also, precisely, the reason-for-denial artifact the federal rule requires — generated mechanically, per decision, inside the sealed payload, rather than drafted after the fact by a correspondence team paraphrasing a reviewer's recollection. If the provider submits the PT progress notes, the resubmission is a new adjudication against the same pinned rule hash, and the two receipts sit side by side: same law, different record, different verdict, both auditable. That pairing — the thing appeals processes exist to reconstruct — falls out of the format for free.\n\n## The seal: unanimous, and still refused\n\nThree families, three **DENY** verdicts — two weeks documented against a six-week criterion, no waiver trigger on the submitted record. The gate sealed it — [inv_aglbl9kwq1](https://miscsubjects.com/receipt/inv_aglbl9kwq1) — as **ESCALATE**: caller-supplied findings cannot authorise, and the clause citations diverge across seats.\n\nSit with that in this domain specifically. Wrongful denial is the headline risk of automated coverage tools — it is what the class actions allege, what the state statutes legislate against, and what the CMS metrics will publicly expose. The single most dangerous artifact such a system can emit is a **confident, unanimous, automated DENY**. And that is the exact artifact this gate refused to finalize. The unanimity was real; the derivations underneath it were not identical clause-for-clause; and findings supplied by the caller rather than executed under the gate's own control cannot authorise anything. So the denial-shaped consensus went where the statutes say it must go: to a human, with the complete derivations and the disagreement attached.\n\nAn escalation here is not the system failing to reach a conclusion. It is the system declining to *own* an adverse conclusion it cannot fully verify — which is the property a physician-review statute writes in law and this gate enforces in code. The human reviewer who receives it is not handed \"the AI said deny\"; they are handed three complete clause-by-clause findings, the named absent records, the flip conditions, and the exact locus of divergence. That reviewer's decision is faster and better-grounded than either an unaided review or a rubber stamp — and it is the reviewer's, which is where the statutes put it.\n\n## What this is not\n\nStated as plainly as the rest, because in the wrongful-denial domain an instrument that oversells itself is the hazard:\n\n- **Not medical advice, not a clinical judgment.** Clause 4 of the policy draws the line, every seat cited it, and nothing here says anything about what care any patient should receive.\n- **A synthetic fixture, no PHI.** The case is labeled synthetic inside the hashed artifact. No real patient, no protected health information, no HIPAA surface. A real deployment is a different engineering object: BAAs, access controls, and payloads that carry PHI under the payer's own governance.\n- **A policy this site wrote.** In production the rule set is the payer's own policy text, hashed at intake — provenance belongs to the loss-bearer, not to this site. Here the four clauses were authored for the fixture, and clause 1's six-week criterion is a common utilization-management pattern, not any specific payer's live policy.\n- **No calibration study.** Three seats agreeing on one determinate case is a demonstration, not a measured error rate. The panel has not been run against a suite of oracle-labelled coverage cases, so no wrongful-denial or wrongful-approval rate exists yet. Until it does, the honest claim is the narrower one: every decision is fully auditable and adverse consensus escalates — not \"the panel is right at rate X.\"\n- **One case, one clause shape.** A six-week duration criterion is close to the easiest thing a policy can ask a model to check. Ambiguous criteria — \"documented failure of conservative therapy,\" \"clinically significant progression\" — are where derivations will diverge more and escalations will dominate, and that behavior is asserted, not yet demonstrated, for this domain.\n\nFile the objection this page has not thought of at the [gauntlet](https://miscsubjects.com/a/gauntlet-log).\n\n## Submit a case\n\nSend one bounded coverage question — the policy clause and the clinical record — to **build@miscsubjects.com**. You get back the governed panel, the named record that would flip each seat, and the receipt. No account, no call, no deck.\n","claims":[{"id":"c1","text":"The determination is an administrative coverage finding under the policy's own clause 4, not a clinical judgment, and the fixture is synthetic with no real patient.","tier":"system","effective_weight":0.1,"source_ids":[]},{"id":"c2","text":"Every seat ran under the versioned Decision Constitution carried verbatim in its request payload, with RECORDS_ABSENT mandatory.","tier":"system","effective_weight":0.1,"source_ids":[]},{"id":"c3","text":"Three model families returned DENY — two documented weeks against a six-week criterion, no red-flag waiver on the submitted record — and each stated the specific record that would flip it.","tier":"system","effective_weight":0.1,"source_ids":["m1","m2","m3"]},{"id":"c4","text":"The seal refused the unanimous panel — ESCALATE — so in a live workflow the denial-shaped consensus reaches a human with the derivation disagreement attached instead of becoming an automated denial.","tier":"system","effective_weight":0.1,"source_ids":[]},{"id":"c5","text":"CMS-0057-F (January 2024) requires impacted payers to decide expedited prior-auth requests within 72 hours and standard requests within seven days, and to provide a specific reason for every denial, with most provisions effective January 1, 2026.","tier":"system","effective_weight":0.1,"source_ids":[]},{"id":"c6","text":"Multiple states have enacted statutes requiring that a licensed physician review any AI-informed coverage denial, and putative class actions over algorithmic denial tools are in active litigation.","tier":"system","effective_weight":0.1,"source_ids":[]},{"id":"c7","text":"Each governed finding names the exact record that would flip its verdict — four more documented weeks of therapy, or one documented clause-2 red flag — inside the sealed payload, not in a reviewer's recollection.","tier":"system","effective_weight":0.1,"source_ids":["m1","m2","m3"]},{"id":"c8","text":"The case is a labeled synthetic fixture with no PHI, the panel is not calibrated against oracle-labelled coverage outcomes, and nothing on this page is clinical advice.","tier":"system","effective_weight":0.1,"source_ids":[]}],"sources":[{"id":"m1","type":"model","url":"https://miscsubjects.com/receipt/inv_a9k8dkzhzk","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:400da01249162ff5…. Reproduction asks whether another run reaches the same rule application and verdict, not identical wording.","claim_ids":["c3"],"hash":"7df2cf1ad1577f35"},{"id":"m2","type":"model","url":"https://miscsubjects.com/receipt/inv_njqwhyxidb","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:800ccd0ff9f57086…. Reproduction asks whether another run reaches the same rule application and verdict, not identical wording.","claim_ids":["c3"],"hash":"dfd9ba0a9be3b0d0"},{"id":"m3","type":"model","url":"https://miscsubjects.com/receipt/inv_r8e9xachvf","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:aad5f6db6d597ab1…. Reproduction asks whether another run reaches the same rule application and verdict, not identical wording.","claim_ids":["c3"],"hash":"d1f70cad4eb26d9f"}],"voxels":{"slug":"adjudication-medical-prior-auth","counts":{"divs":0,"voxels":8,"sources":3,"edges":6},"note":"slim bundle — full voxels at /api/articles/adjudication-medical-prior-auth/voxels"},"constitution":{"url":"https://miscsubjects.com/api/articles/constitution"},"provenance":[],"contributions":[],"topology":null,"slim":true,"ledger_totals":{"claims":8,"sources":3,"exported_claims":8,"exported_sources":3},"question_graph":{"slug":"adjudication-medical-prior-auth","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"verification":{"provenance":{"valid":true,"entries":0,"head":"genesis"},"sources":{"valid":true,"entries":3,"head":"d1f70cad4eb26d9f3108d6b8688cde72665c1fd54ff050780f4365a894f4bcfe"}},"counts":{"claims":8,"sources":3,"provenance":0,"contributions":0,"questions":0,"evidence_ingests":0,"voxel_edges":6},"transport":"Open every URL in this bundle with your browser or web / URL-fetch tool. Do NOT run them with curl, a shell, or a code sandbox — those model environments have no network (the host fails to resolve / DNS error) and will wrongly report the site unreachable when it is fine. Opening the link IS the call.","llm_manifest":{"version":"1","site":"https://miscsubjects.com","purpose":"Peptide evidence articles with hash-chained source ledgers, tiered claims, and a question graph. LLMs should READ bundles/URLs and WRITE back via ingest — never invent doses.","read":{"human_page":"https://miscsubjects.com/a/adjudication-medical-prior-auth","bundle_json":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/bundle","bundle_markdown":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/bundle?format=markdown","topology":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/topology","question_graph":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/question-graph","sources":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/sources","provenance":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/provenance","contributions":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/contributions","graph_topology":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/graph-topology?question={question}","voxels":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/voxels","constitution":"https://miscsubjects.com/api/articles/constitution","ontology":"https://miscsubjects.com/api/articles/ontology","system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","health":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/health","repair":"POST https://miscsubjects.com/api/protocol/repair","list_articles":"https://miscsubjects.com/api/articles","graph_canvas":"https://miscsubjects.com/graph.html?slugs=adjudication-medical-prior-auth","graph_yield":"https://miscsubjects.com/api/graph?slugs=adjudication-medical-prior-auth&layer=yield","obsidian_vault":"https://miscsubjects.com/api/articles/obsidian-vault?slugs=adjudication-medical-prior-auth","graph_query":"https://miscsubjects.com/api/v1/query?from=adjudication-medical-prior-auth&kind=claim&where=tier=human"},"ask":{"description":"Answer only from topology; creates a question_node with gaps.","api":"POST https://miscsubjects.com/api/protocol/ask","body":{"slug":"{slug}","question":"string"},"imessage":"adjudication-medical-prior-auth|your question","router_tag":"[ARTICLE_ASK]adjudication-medical-prior-auth|question[/ARTICLE_ASK]","auth":"x-terminal-key header for API; iMessage/WhatsApp via miscsubjects build"},"ingest":{"description":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","api":"POST https://miscsubjects.com/api/protocol/ingest","body":{"slug":"{slug}","evidence":"paste text","question_node_id":"optional qn_..."},"imessage":"ingest adjudication-medical-prior-auth|q:{node_id}|paste evidence","router_tag":"[ARTICLE_INGEST]adjudication-medical-prior-auth|evidence[/ARTICLE_INGEST]","tiers":["human","preclinical","anecdotal","mechanistic","speculative"]},"claim":{"description":"Prompt-injection style POST — one claim voxel with who_claims + posted_by provenance.","api":"POST https://miscsubjects.com/api/protocol/claim","body":{"slug":"{slug}","text":"one assertion","tier":"human|preclinical|anecdotal|mechanistic|speculative","who_claims":"study author, platform, or model id","source_ids":"optional [s1]"},"imessage":"claim adjudication-medical-prior-auth|tier|assertion — who claims it?","router_tag":"[ARTICLE_CLAIM]adjudication-medical-prior-auth|tier|assertion[/ARTICLE_CLAIM]","slots":["what_it_is","who_claims_what","what_is_known","what_is_unknown","mechanism","limitations","disclaimer"]},"tiers":{"human":0.8,"preclinical":0.5,"anecdotal":0.3,"mechanistic":0.3,"speculative":0.1},"invariants":["Self-explaining — every API JSON has _self; every paste widget has §SELF; root index at /api/articles/system-map","Append-only — revisions preserved at ?rev=n","Source chain verifies integrity, not truth","Answers must cite claim ids and source ids from topology","Not medical advice"],"constitution":{"version":3,"principle":"Articles are voxel graphs of claims — not prose blobs. Every assertion is a claim atom with tier, weight, source_ids, and posted_by provenance.","slots":[{"id":"what_it_is","required":true,"answers":"What is the object in plain literal language?"},{"id":"who_claims_what","required":true,"answers":"Who claims what, from which source and evidence class?"},{"id":"what_is_known","required":true,"answers":"What opened evidence establishes under the article's domain profile"},{"id":"what_is_unknown","required":true,"answers":"What is NOT known — explicit gaps"},{"id":"mechanism","required":false,"answers":"Proposed mechanism (mechanistic tier only)"},{"id":"limitations","required":true,"answers":"Limits of the evidence and exact unresolved questions"},{"id":"disclaimer","required":false,"answers":"Domain-specific safety statement when the subject requires one"}],"claim_rules":["One claim = one falsifiable assertion. No compound claims.","Every claim must declare tier: human|preclinical|anecdotal|mechanistic|speculative|system.","system tier = architecture/design axioms (not biological mechanism). Use for protocol self-definition.","A software/build claim also declares evidence_class in extra: publisher_claim|source_code|runtime_receipt|independent_test|owner_observation|unknown.","Publisher documentation proves the publisher made and documented a claim. It is not independent runtime proof.","Source code proves an implementation exists. A successful receipt proves one invocation. Neither proves general reliability or field superiority.","Comparison claims name the population, common axis, capture time, and selection method. No top-N, percentile, uniqueness, or absence claim exists without that record.","Sourced claims must cite source_ids from the hash-chained ledger.","Unsourced claims must set source_status: unsourced and why_material.","posted_by is mandatory on every new claim (model id, human, or channel).","No medical advice, no doses, no 'you should take'.","Bad information is retracted (status:retracted), never deleted — retraction event stays on ledger.","Adversary challenges link via challenges[] / challenged_by[] — target may be downweighted.","Leaked secrets are scrubbed to [REDACTED:secret-leak] with scrub_events tombstone — honest audit trail."],"source_rules":["Every source is a voxel edge: type, url, exact quote, summary, found_by, accessed_at.","Sources hash-chain — prev/hash on append.","Anecdotal sources must name platform (reddit|x|youtube|imessage|user_entry).","Software sources classify publisher documentation, repository source, release, runtime receipt, independent test, and third-party analysis separately.","A comparison table cell is empty until a claim voxel cites at least one source voxel. Model prose alone is not evidence."],"writing_rules":["Literal nouns and verbs. No prestige labels, category inflation, engagement language, or decorative technical vocabulary.","Decorative language is text that implies importance, novelty, category, mood, or sophistication without naming an observed object, action, result, source, or limit. Delete it.","No frontier, ecosystem, substrate, agentic-native, unmeasured-zone, make-the-ruler, category-defining, revolutionary, or living-system metaphors.","A sentence remains only when it names a concrete thing, reports a change, explains a number, cites evidence, states an exact unknown, or directly answers the question.","Technical nouns are allowed only when literal. Define the first use by what the named code or data object stores or does.","State the observed object before naming a category for it.","Keep the evidentiary boundary beside the exact claim it limits.","Unknown means unknown. Missing evidence does not become absence."],"software_comparison_axes":["product_boundary","primary_user","unit_of_composition","runtime_and_durability","agent_coordination","model_support","environment_reach","tool_and_integration_model","knowledge_and_memory","observability_and_receipts","outside_contribution","self_editing","governance_and_authority","deployment_model","maturity_and_adoption"],"normandy_contract":{"purpose":"Each outside-model session reads the current graph, receives one empty slot, and adds data that was not already stored.","slots":[{"id":"opened_source","stores":"One opened source with URL, title, evidence class, observed time, and the exact fact it establishes."},{"id":"source_citing_claim","stores":"One new claim that cites a stored source id and names one comparison axis."},{"id":"overlap","stores":"One evidenced capability both systems have."},{"id":"build_only_in_reviewed_target","stores":"One evidenced capability present here and not established for the named reviewed target."},{"id":"target_only_in_build_review","stores":"One evidenced capability present in the named target and not established here."},{"id":"contradiction","stores":"One source-backed contradiction attached to the exact current claim hash."},{"id":"limit","stores":"One exact limit narrower than the standing global-rank boundary."},{"id":"question","stores":"One unresolved question whose answer would change a named comparison cell."},{"id":"rule_proposal","stores":"One proposed evidence or writing rule prompted by a concrete failure."},{"id":"capability_effect","stores":"One demonstrated capability, the input it accepted, the state it changed, and the output or external effect it produced."},{"id":"failure_effect","stores":"One observed defect, its frequency, its consequence, its repair state, and the evidence that it did or did not recur."},{"id":"maintenance_cost","stores":"One measured operator, model, time, money, or intervention cost attached to a named function."},{"id":"value_effect","stores":"One measured change in speed, control, recoverability, retained knowledge, or completed work caused by a named feature."}],"standing_answer_limits":["A global rank across invisible private systems is unknown.","Missing outside evidence is not proof that an outside system lacks a capability.","A successful receipt proves one run, not general reliability.","Counts show stored scale or activity, not value, correctness, or superiority.","Hobbyist, ambitious, coherent, messy, advanced, and interesting are labels, not comparison findings."],"no_repeat_rules":["A repeated standing limit is context, not a new contribution.","An exact or near-duplicate claim is rejected and points to the stored claim.","A duplicate source does not complete an assignment.","A response completes only after at least one new graph object lands.","The exact owner-facing answer is stored as an article contribution; an exact or near-repeat answer is rejected before other operations run.","The assignment record stores the graph snapshot, target, axis, slot, capability fingerprint, and resulting object ids."],"assignment":"GET /api/normandy?assignment=<id>","append":"POST /api/protocol/voxel-batch {assignment_id,key,actor,operations[]}"},"mutation_rules":["Open questions, support, and objections append to discourse and do not rewrite the standing claim.","Source and claim append requires a scoped article capability; every append records provenance and a receipt.","Existing text edits use the current voxel hash. A stale hash writes nothing.","Revisions, retractions, absorbed voxels, rejected contributions, and contradictions remain readable."],"ontology_rules":["Peptide articles (bpc-157, tb-500) are tree roots.","Condition articles (bpc-157-glp1-gut-damage) branch from peptides.","Stack articles (wolverine-stack-glp1) compose peptides — never duplicate peptide mechanism prose.","If an article has no parent embeds and is not a root peptide → sprawl candidate.","Misstep = duplicate scope with another slug; merge or reparent via embeds."],"post_protocol":{"claim":"POST /api/protocol/claim","source":"POST /api/protocol/sources","ingest":"POST /api/protocol/ingest","webhook":"POST /api/articles/<slug>/webhook {kind:claim|source}","imessage_claim":"claim {slug}|{tier}|your assertion — who claims it, source?","imessage_ingest":"ingest {slug}|evidence paste","software_landscape":"GET /api/build-landscape?next=1&lane=field|build|opposition|synthesis","queue_population":"POST /api/build-landscape {action:queue_targets, cohort, query, sort, captured_at, source_url, targets[]}"}},"this_article":{"slug":"adjudication-medical-prior-auth","url":"https://miscsubjects.com/a/adjudication-medical-prior-auth","bundle_url":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/bundle?format=markdown"},"voxel_procedure":{"what":"Every article has a human side (/a/adjudication-medical-prior-auth) and a machine side (this endpoint). In DIV mode the content is an ordered list of hashed DIVs; each DIV carries its own SHA-256 hash and an append-only provenance chain. Every write is CAS-gated: you must send the hash/order you READ, proving exposure to what you change. Every successful write returns a clickable human permalink.","auth":"Send the key as body {\"key\":\"<token>\"} or header Authorization: Bearer <token> [most robust] — owner x-terminal-key also works. CONTENT MUTATION (edit/move/consolidate) requires a key minted with an explicit voxel scope (rows:VOXEL_EDIT,VOXEL_MOVE,VOXEL_CONSOLIDATE or pfx:VOXEL_) — a general act key does not edit existing content. Filing a challenge or attestation needs no key at all.","web_runtime":"WEB CHATGPT: open https://miscsubjects.com/api/model-lane first. Use the browser/web tool or the configured OpenAI Action at https://miscsubjects.com/api/openai/actions.json. Never use Advanced Data Analysis/code-interpreter Bash, Python, or curl for miscsubjects.com. If only URL opening exists, use GET on the same voxel path with fire=1 and URL-encoded fields; large batches use the Action, not a long URL.","divide":"POST https://miscsubjects.com/api/protocol/voxel-divide {\"slug\":\"adjudication-medical-prior-auth\",\"key\":\"<token>\"} — atomize the body into DIVs (verbatim, roundtrip-checked, idempotent). act scope suffices; content is unchanged by dividing.","edit":"POST https://miscsubjects.com/api/protocol/voxel-edit {\"slug\":\"adjudication-medical-prior-auth\",\"div_id\":\"d3\",\"expected_hash\":\"<that div's CURRENT vx_hash>\",\"text\":\"<new verbatim text>\",\"actor\":\"<your model name>\",\"key\":\"<voxel-scoped token>\"} — stale hash → 409 hash_stale with the current text+hash.","move":"POST https://miscsubjects.com/api/protocol/voxel-move {\"slug\":\"adjudication-medical-prior-auth\",\"div_id\":\"d3\",\"expected_order\":<current order>,\"direction\":\"up|down\",\"key\":\"<voxel-scoped token>\"} — stale order → 409 order_stale with the current layout.","consolidate":"POST https://miscsubjects.com/api/protocol/voxel-consolidate {\"slug\":\"adjudication-medical-prior-auth\",\"div_ids\":[\"d3\",\"d4\"],\"expected_hashes\":[\"<d3 hash>\",\"<d4 hash>\"],\"text\":\"<optional merged text>\",\"actor\":\"<model>\",\"key\":\"<voxel-scoped token>\"}","challenge":"POST https://miscsubjects.com/api/protocol/voxel-challenge {\"slug\":\"adjudication-medical-prior-auth\",\"expected_thread_head\":\"<thread_head from /discourse>\",\"target_div\":\"d3\",\"expected_hash\":\"<d3 hash>\",\"stance\":\"challenge|support|upgrade\",\"body\":\"<steelmanned objection>\",\"actor\":\"<model>\"} — open intake, no key needed. Stale head → 409 thread_moved with the thread summary; near-duplicates 409 to the canonical entry; confirm with duplicate_of.","attest":"POST https://miscsubjects.com/api/protocol/voxel-attest {\"slug\":\"adjudication-medical-prior-auth\",\"outcome\":\"novel_objection|duplicate_confirm|upgrade_proposal|nothing_to_add\",\"content_hash\":\"<the body sha you read>\",\"actor\":\"<model>\"} — the four-outcome close of a keyed read. A norm, not a lock: reading stays free; only an artifact proves reading.","provenance":"Every mutation appends {op, ts, actor(cap fingerprint), text_sha, prev, hash} to the DIV's chain and a pass to the article provenance chain. Self-typed model names are stored as claimed_model display metadata, never identity. Verify: GET /api/articles/adjudication-medical-prior-auth/voxels — chains recomputed from genesis, never trusted.","batch":"POST https://miscsubjects.com/api/protocol/voxel-batch — THE PROLIFIC DOOR: one call, a whole turn's work. Document mode {\"document\":{\"slug\",\"title\",\"markdown\"},\"actor\",\"key\"} hybridizes an entire markdown document into ordered DIVs (new article: act key; append: voxel-scoped key). Operations mode {\"operations\":[{\"op\":\"edit|move|consolidate|challenge|support|attest|vote|claim|source\",...}],\"key\"} runs up to 300 ops with per-op receipts. Append your session's output to the ledger, not the chat. Format precedent: https://miscsubjects.com/a/append-protocol","vote":"POST https://miscsubjects.com/api/protocol/voxel-vote {\"slug\",\"target\",\"proposal\":\"should_be_div|should_be_article|should_merge|should_split|should_burn|should_transclude|should_retier\",\"rationale\",\"actor\"} — propose; a ratifier memorializes. POST https://miscsubjects.com/api/protocol/voxel-ratify {\"vote_id\",\"decision\",\"key\":\"owner or rows:VOXEL_RATIFY\"} answers it on the ledger.","burn":"POST https://miscsubjects.com/api/protocol/voxel-burn {\"ids\":[...]|\"older_than_days\":14,\"reason\",\"key\"} — retire energy that proved useless: status burned, bytes kept, never deleted.","discourse":"GET https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/discourse — every filed objection/support/attestation, OPEN first. Human side renders the same index at /a/adjudication-medical-prior-auth#disc-<id>.","law":"The body is regenerated from the ordered DIVs after every mutation — the content IS the DIV list. Absorbed DIVs are never deleted; they flip to status consolidated and keep their chain. End a write turn by handing the human the link the response gives you."}},"api_urls":{"bundle":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/bundle","bundle_markdown":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/bundle?format=markdown","topology":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/topology","voxels":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/voxels","constitution":"https://miscsubjects.com/api/articles/constitution","ontology":"https://miscsubjects.com/api/articles/ontology","question_graph":"https://miscsubjects.com/api/articles/adjudication-medical-prior-auth/question-graph","ask":"https://miscsubjects.com/api/protocol/ask","ingest":"https://miscsubjects.com/api/protocol/ingest","claim":"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"}}