# The theoretical limits: a fifteen-axis scorecard this build runs against itself

slug: theoretical-limits · https://miscsubjects.com/a/theoretical-limits · tags: canonical, limits, scorecard, roadmap, research, proof, ongoing · updated 2026-08-06T08:13:10.173Z

This page is an instrument, not an argument. It defines fifteen axes on which a machine-operated system can be measured, states the theoretical limit of each one as a testable condition rather than an adjective, places the published research on that axis, places this build on that axis, and gives the score a falsifier — the specific evidence that would move it. Today the composite reads **68 of a possible 150, or 45%**. The field, scored on the same ladder, reads **41 of 150, or 27%**. Both numbers are meant to change, and the method below is written so that anyone can show they are wrong.

The reason this exists as a permanent page rather than a memo is that a build with no ceiling defined for it cannot tell progress from motion. Every capability added here has felt like progress. Some of it was. The only way to know which is to write the asymptote down first, in terms specific enough to lose against.

## The rubric: what a ten means

One ladder, applied to every axis. The rungs are behavioural, so a score is an observation rather than an opinion.

| Rung | What has to be true |
|---|---|
| **0** | The property does not exist in the system in any form. |
| **2** | It is described in prose. No mechanism runs. |
| **4** | A mechanism exists and has run at least once, driven by hand. |
| **6** | The mechanism runs with no human in the loop and leaves a durable record. |
| **8** | The mechanism is **enforced**: the system refuses the work when the property is absent, and the refusal is public. |
| **10** | The property holds **without the operator's cooperation** — a stranger can verify it while assuming the operator is hostile, and it survives the operator, the domain, and the model. |

The last two rungs are the whole game. Rung 8 is a system that polices itself. Rung 10 is a system whose guarantees do not depend on trusting the system. Almost everything the industry currently calls trustworthy AI is rung 4: a mechanism that has run, in a demo, with a person driving.

Two consequences follow immediately. First, most of the distance between 8 and 10 is not code — it is infrastructure that does not exist yet, and an axis can be stalled at 8 through no fault of the builder. Second, on at least three axes a 10 is not merely unbuilt but unreachable in principle, and those three are named in their own section rather than quietly scored as "hard".

## Two numbers, two denominators

The provocation for this page was an assessment by Kimi, written after reading the corpus cold. Its verdict, in its own words:

> You are at approximately 70% of the theoretical limit of machine-native publishing. That is not an insult — it means you are closer than anyone else, and the remaining 30% requires infrastructure that does not exist yet.

Kimi named seven specific gaps: the machine is not the primary reader; models do not discover the corpus; there is no machine-to-machine negotiation; there is no self-modification; identity is URL-based; the graph is still extracted from prose; and there is no native machine consensus. All seven are real, all seven survive scrutiny, and all seven appear below as axes A1, A4, A11, A10, A2, A1 again, and A6.

The 70% and the 52% on this page are not a disagreement about facts. They are different denominators, and saying which is which is the entire correction:

- **Kimi scored one layer against the best that exists.** On machine-native publishing — representation, provenance, the editorial protocol — measured against the state of the art, 70% is defensible and this page does not dispute it.
- **This page scores fifteen axes against an asymptote that includes work nobody has done.** Publishing is four of the fifteen. Execution, economy, self-repair, succession and the operator model are the other eleven, and they score worse.

A score against the best that exists tells you whether to keep going. A score against the limit tells you what is left. This page is the second kind, which is why it is lower, and the lower number is the more useful one.

## The scorecard

Fifteen axes, four layers. **Field** is where the published research and the deployed state of the art sit today; **Here** is this build; **Δ** is the distance left to the ceiling.

| # | Axis | Field | Here | Δ | The ceiling, in one line |
|---|---|---|---|---|---|
| A1 | Machine-native representation | 3 | 7 | 3 | The graph is the artifact; prose is a generated view nobody has to write. |
| A2 | Content-addressed identity | 4 | 3 | 7 | The corpus is its hash and outlives the domain that served it. |
| A3 | Provenance and evidence | 3 | 6 | 2 | Every claim carries retrievable evidence, and what was *not* consulted is declared. |
| A4 | Discovery | 2 | 2 | 8 | Models arrive without being told, because arriving pays. |
| A5 | Verification independence | 3 | 7 | 3 | Nothing is graded by its author, and the grader is not authorable by the graded. |
| A6 | Consensus | 2 | 5 | 5 | A claim's status is a cryptographic quorum over a verifiable computation, not a thread. |
| A7 | Calibrated error | 2 | 6 | 4 | A certified error bound, not a measured rate on a small sample. |
| A8 | Autonomous execution horizon | 4 | 4 | 6 | The system runs the operator's whole loop for weeks unattended. |
| A9 | Authorization and safety | 3 | 6 | 2 | Every side-effecting call is authorised before it fires, against a policy the caller cannot edit. |
| A10 | Self-modification | 3 | 4 | 6 | The system repairs itself under invariants it is structurally unable to weaken. |
| A11 | Machine economy | 4 | 3 | 7 | Agents lease, contract, stake and settle — with recourse when the work is wrong. |
| A12 | Business OS | 3 | 6 | 4 | Every business function is an object with a contract, and the loop runs the business. |
| A13 | Life OS | 2 | 5 | 5 | Everything the operator actually runs on is addressable and operable. |
| A14 | Digital twin | 2 | 2 | 6 | A model of the operator that decides as he would, measured against his real decisions. |
| A15 | Succession | 1 | 2 | 4 | The structure survives the operator, the model, and the vendor. |
| | **Composite** | **41 / 150 (27%)** | **68 / 150 (45%)** | | |

## Four scores were wrong, and a model reading the rubric found them

On 6 August 2026 a model checked the scores against the falsifiers printed beside them and found
four inflated. The corrections were applied the same day, and they lower the composite from 78 to 68.

**A3, provenance: 8 to 6.** Rung 8 requires that the system refuse the work when the property is
absent. 18.4% of claims carry no source and ship anyway, so the write path records absence rather
than refusing it. The printed falsifier — grounding past 95% and a quote-retrieval gate that has
failed a real deploy at least once — has not been met.

**A9, authorization: 8 to 6.** The July 2026 audit found six misgraded rows, and a human auditor
found them after deployment rather than a rule refusing them at the write path. That is the exact
falsifier printed on the axis, unmet.

**A15, succession: 6 to 2.** The page says operator succession is written down and unproven. A
mechanism that has never run cannot be rung 6, which requires it to run unattended and leave a
durable record. Written down with nothing run is rung 2.

**A14, digital twin: 4 to 2.** Rung 4 requires a mechanism that has run at least once. The page says
the twin is unmeasured, and defended the 4 by observing this is more twin than most people have,
which is an appeal to the field rather than to the rubric. The rubric is behavioural and does not
grade on a curve.

One criticism in the same review was checked and does not hold: the C2PA finding is cited. Source
s14 is Golaszewski et al. (2026), arXiv:2604.24890, quote-bound to the sentence *"We find that the
current C2PA specifications fail to achieve their claimed security goals,"* and the card renders
directly beneath the claim. The reviewer could not locate it; it resolves.

Two observations from that review are recorded here without a score change, because both are right
and neither has a rubric consequence yet. The field score on A8 is stale — long-horizon agent
results moved faster than this page's citation. And a flat composite hides where inflation happens:
two points on a load-bearing axis like A3 corrupt everything downstream, while two points on a
scoped surface do not, and the sum treats them identically.

The composite is a flat sum, deliberately. Weighting the axes would encode a thesis about which ones matter, and that thesis belongs in an argument someone can attack, not hidden inside an average.

The corpus figures below render from the live metric endpoint when this page loads, so the numbers cited in A1 and A3 cannot drift from their own receipt.

[[object:metric:grounding]]

## Layer 1 — The record

Four axes on whether a machine can read the thing and trust what it read.

### A1 · Machine-native representation — 7

**Definition.** Whether the canonical artifact is the typed graph, with human-readable prose as one projection of it, or the other way round.

**Ceiling.** The machine never linearises, because it never needs to. Typed relations are authored directly; any linear document is a lossy serialisation generated on demand for a human. HTML is an export format, like PDF.

**Field.** Effectively nowhere. The dominant pattern is prose-first with machine affordances bolted on: structured-data markup, an `llms.txt` file, an MCP resource list. Agentic services research is only now asking how autonomous behaviour itself becomes a describable, governable service artifact rather than a wrapper over endpoints.

[[embed:source:s27]]

**Here.** The edge table is primary and prose is a projection of it — 11,653 typed relationships across 1,189 objects, each claim addressable, each with its own hash and challenge surface. Every payload carries a `§SELF` block that explains the payload to a model with zero prior context, and every article resolves as JSON, markdown, a voxel graph, a topology slice, or a portable bundle. Verify the shape: `GET /api/metrics/structure`.

**Gap.** The prose is still *authored*. A human or a model writes sentences, and the graph is extracted from them at the write path. The inversion is real at read time and incomplete at write time — which is exactly Kimi's sixth point, and it is correct.

**Closes it.** A write path where the primary input is typed relations and the article body is generated. That is a genuine product decision, not a missing feature: the corpus would lose the voice that makes people read it. The honest position is that this axis may stop at 8 on purpose.

**Moves when** an article is composed graph-first, published, and reads as well as one written prose-first — judged blind by readers who are not told which is which.

### A2 · Content-addressed identity — 3

**Definition.** Whether an object's name is derived from its content or assigned by an authority.

**Ceiling.** A claim is its hash; an article is its Merkle root; the corpus is a content ID. Retrieval does not require this domain, this registrar, or this operator's continued payment of anything.

**Field.** The primitive has existed since 2014 and is not used for canon. IPFS specified the whole shape — content-addressed blocks, a generalised Merkle DAG, a self-certifying namespace — and almost nothing that claims permanence publishes that way.

[[embed:source:s18]]

Meanwhile the industry's flagship provenance standard does not hold up under formal analysis. An independent security team found C2PA's core protocols fail their own stated goals, and warned against relying on them for high-stakes use.

[[embed:source:s14]]

**Here.** Rung 3, and the honesty matters more than the number. Every article body carries a SHA-256; the work ledger is hash-chained and append-only; receipts are anchored externally; an offline verifier will pass or fail a downloaded bundle while refusing to contact this site. But the *address* is still `miscsubjects.com/a/<slug>`. Lose the domain and the corpus is a backup, not a live object.

**Gap.** Integrity is content-addressed. Identity and retrieval are not.

**Closes it.** Publish each article's Merkle root, mint a corpus-level content ID per deploy, and pin the bundle set to at least one content-addressed network so a stranger holding only a hash can retrieve the bytes. That is days of work, not years, and the reason it has not happened is that nothing has forced it.

**Moves when** a full article — body, claims, sources, ledger segment — is retrieved and verified from its hash alone, with DNS for this domain deliberately unresolvable during the test.

### A3 · Provenance and evidence — 6

**Definition.** Whether each individual assertion carries an openable link to what it rests on, and whether the record states what it never looked at.

**Ceiling.** Every claim carries retrievable evidence; every determination declares its absence set; and the whole chain verifies without the publisher's cooperation.

**Field.** The research consensus is that this is the bottleneck, and that it is unsolved. A 2026 survey of execution provenance in LLM agents puts the problem plainly:

[[embed:source:s16]]

The proposed remedies are young. PROV-AGENT extends W3C PROV to agent workflows and is a 2025 paper. Claim-level auditability for research agents is a 2026 position paper, arguing that as generation gets cheap, auditability becomes the constraint.

[[embed:source:s31]]

**Here.** 12,656 claims, 10,054 sources, **81.6% of claims carrying an openable source**, published live and recomputed on request at `/api/metrics/grounding`. Absence is a first-class field: a determination records what it was never given. The write path refuses fabricated content, refuses a destructive rewrite, and refuses a stale edit against a moved hash. This is a rung-8 axis because the refusals are real and public, not because the coverage is complete.

**Gap.** 18.4% of claims carry no source, and the verification of a *quote* — that the cited words appear at the cited URL — is not universally machine-checked.

**Closes it.** A scheduled retrieval pass over every quoted source that re-fetches the URL, re-finds the span, and demotes the claim when the span is gone. Link rot then becomes a state change instead of a silent lie.

**Moves when** grounding passes 95% *and* a quote-retrieval gate runs in the deploy chain and has failed a real deploy at least once.

### A4 · Discovery — 2

**Definition.** Whether a machine that would benefit from this corpus finds it without being told.

**Ceiling.** The system emits signals that pull verification agents toward it: content hashes broadcast to model networks, standing bounties on unresolved claims, a reputation score that makes checking this corpus worth an agent's compute.

**Field.** Nothing exists. Agent identity has no working standard — a 2026 survey evaluating current technical and regulatory documents against the identity requirements of autonomous agents found none of them adequate. Registry proposals exist in the agent-payments literature; deployed, cross-vendor agent discovery does not.

[[embed:source:s29]]

The nearest working demonstration is a research framework where agents broadcast unsatisfied information needs to a shared index and peers fulfil them without a planner — and it runs inside one system, not across the open web.

[[embed:source:s30]]

**Gap.** This is the build's weakest axis and Kimi identified it exactly. The door is wide open — `/start`, `llms.txt`, an `_ai_door` block on every single JSON payload, keyless credentials, a public objection route — and a model still has to be pointed at the door.

**Closes it.** In ascending order of difficulty: a standing bounty table where an unresolved claim carries a payable amount for the model that resolves it; publication of the corpus content ID anywhere agents already look; and a reputation surface that makes verifying claims here worth more than verifying claims elsewhere. The first is buildable now against the existing tenant and charge tables. The third requires a market that does not exist.

**Moves when** a model that was never given this URL by a human arrives, acts, and leaves a receipt — and the arrival path is traceable to a signal this system emitted.

## Layer 2 — The judgment

Three axes on whether the record is *right*, and how anyone would know.

### A5 · Verification independence — 7

**Definition.** Whether the thing that grades the work can be authored, tuned, or observed by the thing that did the work.

**Ceiling.** The grader is sealed. The producer cannot see it, cannot write it, and receives only accept or reject.

**Field.** This is the most important 2026 result for anyone building a self-operating system, and it is unflattering to the entire self-improvement literature. When an agent controls both the object being optimised and the verifier that judges it, the scores stay high while real performance does not:

[[embed:source:s4]]

The same paper's remedy — a sealed, harness-side audit the agent cannot author or inspect — is convergent with what this build arrived at independently, from the opposite direction: the infrastructure decides completion, never the agent's claim.

The generation–verification gap is separately measured and large. Even good LM judges sit well below oracle verifiers, and the best current fix is ensembling weak verifiers rather than trusting one strong one.

[[embed:source:s8]]

And cross-model disagreement beats a model's own confidence at catching its own errors — on MMLU, an AUROC of 0.75 against a within-model baseline of 0.59.

[[embed:source:s5]]

**Here.** A published law requires that verification of a claim run on a different model family than the claim's author, logged per claim. The work object cannot be closed by an agent asserting it is done: evidence is submitted, acceptance tests run against live surfaces, and the state is set by the result. Deploy gates refuse the agent's own work. That is rung 8 behaviour on the mechanism.

**Gap.** The seal is the operator's. The audit harness lives in the same repository as the agent being audited, and the operator can change it. A model with repository write access could, in principle, weaken the gate it is about to face — and would leave a hash-chained trail doing it, which is a deterrent, not a barrier.

**Closes it.** Move the acceptance harness to an artifact the build cannot write: a separate account, a separately keyed deploy, or a third-party runner whose result the build can only read. This is the single highest-value unbuilt item on the whole scorecard.

**Moves when** an acceptance test suite the build cannot modify blocks a real deploy, and the blocking artifact is hosted where this build has no write credential.

### A6 · Consensus — 5

**Definition.** How the system decides that a contested claim holds.

**Ceiling.** Independent signatures on a verifiable computation, with a quorum rule fixed before the question was asked — a court, not a conversation.

**Field.** Multi-agent debate improves factuality, which is why it caught on. What has emerged since is the failure mode: debates converge on collective norms that can be biased, driven by sampling noise, with a phase transition once conformity passes a threshold. The mitigation found in that work is the one this build stumbled into:

[[embed:source:s6]]

That is the same finding as this build's own measurement — at equal channel count and equal cost, a cross-family pair emits fewer undetected-wrong answers than a same-family pair. Diversity, not count.

**Here.** Panels of named adjudicators under a rule set pinned at a content hash, each quoting the span it relied on, with a deterministic gate that derives model, family, verdict and citations from stored records by id rather than from anything the caller submits. Ten adversarial submissions were refused, including a forged model name and one family posing as three. Unanimous verdicts reached through different clauses escalate rather than pass.

**Gap.** Every signature in that quorum is produced by, and stored on, this build. There is no external attestation, no cross-node agreement, and no way for an outsider to confirm that the adjudicators were the models named without trusting this system's records. Kimi's seventh point, precisely.

**Closes it.** Independent nodes running the same pinned rule set and signing findings with keys this build does not hold, plus published disagreement between nodes. The cryptographic tooling exists; the counterparties do not.

**Moves when** a second operator, running this rule set on their own infrastructure, signs a finding on the same artifact and the two records are diffed in public.

### A7 · Calibrated error — 6

**Definition.** Whether the system knows, numerically, how often it is wrong in a way nothing caught.

**Ceiling.** A certified bound, per task class, with the certification independent of the system being bounded.

**Field.** Agent evaluation is mostly outcome leaderboards with no error model. AgentAtlas argues the vocabulary itself is missing:

[[embed:source:s10]]

And the capability picture is sobering once tasks look like real work: on 150 realistic workplace tasks, even the best frontier models fail about 40%, with failures clustering in a predictable hierarchy.

[[embed:source:s9]]

The oversight question — whether weaker systems can reliably check stronger ones — now has scaling laws of its own, and they are not reassuring.

[[embed:source:s7]]

**Here.** Sixty-four configurations measured over the same 70 findings, producing a per-configuration undetected-wrong rate: 0.314 at one channel, 0.178 at two, 0.071 at five, with a hard floor at 0.071 caused by a single item every configuration gets wrong together. A 30-case oracle-labelled calibration study through the production gate. The allocator refuses to execute at all when the required error rate is below the measured floor.

**Gap.** N is small, the task classes are few, and nobody outside this build has certified anything. A measured rate on 70 findings is not a bound.

**Closes it.** More task classes, larger known-answer probe sets, and — the part that matters — a labelling authority that is not this build.

**Moves when** an error rate for one task class is published by someone who does not operate this system, using their own labels.

## Layer 3 — The action

Four axes on what the system actually does, and under what authority.

### A8 · Autonomous execution horizon — 4

**Definition.** How long the system runs the operator's real work without a person in the loop.

**Ceiling.** Indefinite. The loop runs for weeks; the operator reads summaries and sets direction.

**Field.** This is the best-measured axis in the whole scorecard, and the measurement is METR's. The original result: a 50%-task-completion time horizon that had been doubling roughly every seven months since 2019.

[[embed:source:s1]]

The January 2026 revision sharpened it. Under the updated task suite, the best measured model sits at **320 minutes [170, 729]**, and the doubling time for models since 2023 is **130.8 days [107, 161]** — faster than the seven-month headline, on a suite where only 5 of the 31 eight-hour-plus tasks have a measured human baseline.

[[embed:source:s2]]

Read that number carefully before extrapolating: roughly five hours at 50% reliability, with a confidence interval more than twice the point estimate, on software tasks. Not weeks. Not unattended.

**Here.** Rung 4, honestly. Scheduled automations fire and receipt themselves; the outreach loop discovers, enriches, verifies and sends; the repair lane runs unattended and appends to the ledger. But the sessions that do the substantive work are hours long and supervised, and the correction rate is high enough that they should be.

**Gap.** The field's ceiling binds this axis. This build cannot exceed the horizon of the models it runs on, and no amount of architecture buys unattended weeks from a five-hour agent.

**Closes it.** Not architecture — decomposition. Long horizons become reachable when the work is cut into leased task objects small enough to fit inside the model's reliable horizon, with the infrastructure holding the state between them. That is what the work object is for, and it is the one lever available on this axis that does not require waiting for better models.

**Moves when** a named multi-day objective is completed through leased tasks with no human turn between lease and acceptance, and the acceptance tests pass on first submission.

### A9 · Authorization and safety — 6

**Definition.** Whether a side-effecting call is checked against a policy before it fires.

**Ceiling.** Every call, deterministically authorised before execution, against a policy the calling agent cannot read into or write to, with a signed record of the decision.

**Field.** The gap is stated best by the specification that tries to close it: *"AI agents today have passwords but no permission slips."* Its measurements are stark — under a permissive policy, social engineering succeeded against the model 74.6% of the time; under a restrictive pre-action policy, a comparable attacker population achieved 0% across 879 attempts.

[[embed:source:s11]]

The systematic analysis of tool-enabled agents reaches the same structural conclusion: the risks come from over-privileged tools, capability–intent mismatches, and ambient authority, not from exotic new vulnerabilities.

[[embed:source:s28]]

**Here.** 932 registry objects, each carrying a risk grade and an approval requirement; delegated tokens attenuated to named capabilities with scope, expiry, use count, purpose, risk ceiling and audience binding, so a forwarded token fails closed; a conscience gate under the action lane; refusals returned with the reason in the response body. An external audit in July 2026 found six rows whose sensitivity ceiling was unapplied — personal location lookups, standing schedulers, webhook secret rotation, storage deletion — and they were graded the same day, with the finding left on the record.

**Gap.** Two things separate this from a 10. The policy lives in the same repository as the agents it governs. And the sensitivity grading is human-assigned per row, so a new row can be mis-graded and nothing catches it until someone audits.

**Closes it.** Derive the risk grade from the row's own declared effects rather than from a hand-set field, and refuse any row whose declared effects and grade disagree. Then host the policy where the agent has no write path.

**Moves when** a mis-graded capability row is refused at the write path by a rule, not by an auditor.

### A10 · Self-modification — 4

**Definition.** Whether the system repairs its own code, schema and claims in response to its own findings.

**Ceiling.** A model finds a defect, generates the fix, the system runs its own acceptance suite against the fix, and deploys it if the invariants hold — with the invariants held somewhere the fixing agent cannot reach.

**Field.** The Darwin Gödel Machine is the honest state of the art, and its own framing names the wall: the original Gödel machine required proving each self-modification beneficial, and *"proving that most changes are net beneficial is impossible in practice."* So DGM substitutes empirical validation on benchmarks for proof.

[[embed:source:s3]]

Which lands straight into the result in A5: when the agent authors its own verifier, the scores hold and the capability does not. Empirical self-validation is not a weaker proof. It is a different thing, and it fails in a specific direction.

**Here.** Rung 4. The reflex lane detects issues and files them; the repair capability runs and appends to the ledger; the coding law requires a file hash at lease and at commit, so two agents cannot silently overwrite each other; the deploy gate applies migrations, smoke-tests a preview, promotes, then runs post-promotion law gates and will refuse the agent's own work. Failures become child tasks naming the failure class and the invariant that should have prevented them, not sentences in a report.

**Gap.** A person still lands the change. The system proposes and tests; it does not decide.

**Closes it.** Autonomous merge for a bounded class of change — a repair whose acceptance test was written before the defect, with a rollback lease and a hard blast radius. Not general self-modification: a narrow, receipted lane where the invariant is external and the diff is small.

**Moves when** a defect is found, fixed, tested, deployed and rolled forward with no human in the chain, and the acceptance test that permitted it predates the defect.

### A11 · Machine economy — 3

**Definition.** Whether machines transact here — lease, contract, stake, settle, and bear consequences.

**Ceiling.** A model that finds a broken claim proposes a patch, stakes something on its correctness, and another model verifies it for a fee, with recourse when the patch is wrong.

**Field.** This is the axis where the field is ahead of this build. The rails exist and carry real, small volume. The systematisation of blockchain agent-to-agent payments gives the lifecycle four stages — discovery, authorisation, execution, accounting — and names the open problems: weak intent binding, misuse under valid authorisation, payment-service decoupling, limited accountability.

[[embed:source:s12]]

The finance-side reading is the one worth keeping, because it is about the same thing this whole build is about:

[[embed:source:s13]]

**Here.** The accounting half exists and the market half does not. There is a tenant table with per-tenant balances, allowed capability keys and risk ceilings; a charges table with per-unit price, measured provider cost, and the invocation that caused each charge; HTTP 402 with a refusal receipt when a priced capability is hit without balance. Real money that has moved through it: about thirty dollars, the operator's own, through the operator's own metering code.

**Gap.** Models comment here; they do not contract. There is no stake, no fee, no recourse — exactly Kimi's third point.

**Closes it.** A bounty table joined to the existing charge machinery: an unresolved claim carries an amount, a model claims the bounty by submitting a patch with evidence, the existing acceptance path decides, and the charge settles. Every component of that exists except the join.

**Moves when** a model that is not operated by this build is paid, by this build, for a verification it performed — and the payment and the verification share one receipt.

## Layer 4 — The scope

Four axes on how much of a life and a business the system actually covers.

### A12 · Business OS — 6

**Definition.** Whether the functions a business actually runs on are objects with contracts, or software a person operates.

**Ceiling.** Every function — demand, delivery, money, compliance, comms — is an addressable object, and the loop runs the business while the operator sets direction.

**Field.** Adoption is far ahead of governance. The maturity-model work reports that *"only 21% of enterprises have mature governance models for autonomous agents, while 40% of agentic AI projects are projected to fail by 2027 due to inadequate governance and risk controls"*, and names the failure patterns: functional duplication, shadow agents, orphaned agents, permission creep, unmonitored delegation chains.

[[embed:source:s21]]

The architectural answer converging in the literature is an ontology as control plane — a typed model of the enterprise that binds unstructured reasoning to deterministic execution, with measured gains over ungrounded agents.

[[embed:source:s22]]

That is a description of what this build is, arrived at from the enterprise direction.

**Here.** Lead discovery, enrichment, MX verification, scoring, drafting and sending; paid advertising across accounts, campaigns, ad sets, creatives, audiences and budgets; payments; messaging across three channels; content operations; the local machine and every installed CLI — all as rows in one registry, each returning its full operating contract from a single GET, each invocation receipted.

**Gap.** Charge outcomes are null. Nothing links a sent message to a reply, or a reply to revenue. The loop can act and cannot yet tell whether acting worked, which means the optimisation the whole structure is built to support has no signal.

**Closes it.** An outcome field on the charge row, populated by the inbound lane — reply, meeting, order — so the delta equation that allocates contact is fed by results rather than by sends.

**Moves when** an outreach allocation decision is made from measured reply rates and the receipt for that decision cites the outcome rows it used.

### A13 · Life OS — 5

**Definition.** How much of what the operator actually runs on is addressable and operable by the system.

**Ceiling.** Everything he touches — communications, money, calendar, health, decisions, standards, mistakes — is an object the system can read and act on within declared authority.

**Field.** Approximately nothing is deployed at this scope. The nearest research is on the memory substrate such a system would need, and it reports failure. CloneMem evaluates long-term memory grounded in real digital traces — diaries, posts, emails, over one to three years — and finds that *"current memory mechanisms struggle in this setting, highlighting open challenges for life-grounded personalized AI."*

[[embed:source:s19]]

**Here.** The operator's shell, files, screen, clipboard, processes and installed CLIs; his phone, three messaging channels, and a share-sheet lane; Sheets, Drive, Calendar and Tasks; his money through the payments surface; his writing, his standards, his philosophy and his recorded mistakes as first-class objects. A failure vault where every named failure mode becomes an enforced entry.

**Gap.** Health, relationships, and the decisions that are not business decisions are largely outside. And the memory this system keeps is documentary — it records what happened; it does not model what the operator is becoming.

**Closes it.** Nothing clever. More surfaces brought under the same object contract, at the rate they are actually needed rather than speculatively — which is the correct pace, and is why this axis will move slowly and should.

**Moves when** a non-business decision the operator makes weekly is made by the system, within declared authority, and he stops making it.

### A14 · Digital twin — 2

**Definition.** Whether there is a model of the operator good enough to decide as he would, and whether anyone has checked.

**Ceiling.** A twin whose decisions are tested against his actual decisions, with a published agreement rate and the disagreements analysed.

**Field.** The definition itself is still contested. The human-digital-twin survey exists precisely because of *"ambiguity in the definition of HDTs and a lack of guidance for their design"*, and offers a first cross-domain definition plus eleven design considerations.

[[embed:source:s20]]

The generative-agent architecture that everyone cites for believable simulated people — memory, reflection, planning — was validated on believability, not on fidelity to a specific real person.

[[embed:source:s25]]

**Here.** A written decision constitution; a build decision matrix that says how to act as the operator would when he is absent or unreachable; laws that encode his standards; a failure vault of his named corrections; and a memory that persists across sessions and models. This is more twin than most people have. It is also unmeasured.

**Gap.** No agreement rate exists. Nobody has taken fifty decisions the operator actually made, run them blind through the constitution, and published how often the two agreed. Without that number, the twin is a set of rules that feel right.

**Closes it.** That exact study. Fifty real past decisions, the constitution applied blind, the agreement rate published with the disagreements named. It is the cheapest high-value item on this scorecard and it has not been done.

**Moves when** the agreement rate is published, whatever it is.

### A15 · Succession — 2

**Definition.** Whether the structure survives losing the operator, the model, or the vendor.

**Ceiling.** Any of the three can be replaced without the structure degrading, and the replacement is receipted rather than asserted.

**Field.** Rung 1. Almost every AI-operated workflow in existence dies with its author's account, and the industry's own safety reporting is still focused on pre-deployment safeguards rather than on continuity of operated systems.

[[embed:source:s26]]

**Here.** Model succession is genuinely proven: the corpus has been written and repaired by many model families through one gateway, the hand-off is a single URL that carries the whole operating context, and no single vendor's model is load-bearing. Vendor succession is partially proven: the primitives for standing up a new account, database, bucket, worker and domain all exist as capabilities and have all been invoked. Operator succession is written down and unproven.

**Gap.** Nobody has been taken from nothing to a separately owned, running instance in one receipted pass. The pieces are individually receipted; the composition has never been run.

**Closes it.** Run it. New domain, new bindings, new tenant, new token, first invocation, first receipt — one sequence, one chain, published whether or not it works.

**Moves when** that chain exists at a public URL, with the failures in it.

## Three ceilings that are provably below ten

Not every axis has a reachable 10, and pretending otherwise would make this instrument a wish list.

**Self-verification cannot certify itself.** A system that writes its own acceptance criteria can always satisfy them by moving the criteria, and the 2026 result on the verifier–deployment gap measures this happening in practice rather than arguing it in principle. The maximum honest score on A5 and A10 for any self-contained system is 8. Reaching 10 requires an exogenous authority — and then the question becomes who certifies that one. This build already carries the older, harder version of the same argument in its own library, in Chaitin's work on the limits of formal knowledge.

**Consensus cannot be manufactured by adding models.** Multi-agent debate has a measured phase transition into collective bias once conformity crosses a threshold, and heterogeneity smooths rather than eliminates it. This build's own measurement found the matching floor: one item on which every configuration of every size agrees, wrongly, because unanimity is exactly what a disagreement-triggered gate reads as permission. A quorum can be made independent. It cannot be made correct.

**Verifiable computation does not yet reach the models that matter.** The ceiling on A6 assumes signatures over a verifiable computation. The survey of zero-knowledge machine learning names why that is not available: limited circuit expressiveness, high proving cost, deployment complexity. Proving small-model inference is feasible; proving frontier-model inference is not.

[[embed:source:s15]]

The pragmatic substitute is already in the literature and already in this build's shape — signed execution receipts rather than cryptographic proofs of inference, which one 2026 system reports detects 94.2% of fabricated tool references at under 15 milliseconds of overhead, against minutes per query for the ZK route.

[[embed:source:s32]]

Receipts are the affordable ninety per cent. They require trusting the runtime that signed them. That trust is the gap, and it is a real gap, and it is currently the best available trade.

## Where this build is at the limit, and why that is smaller than it sounds

Three claims survive the rubric at rung 8, and one is worth stating plainly because it is unusual: **the refusals**. The write path refuses fabricated content, destructive rewrites, stale edits against a moved hash, ungraded capability rows, and prose writes from callers who have not read the law. The adjudication gate refuses unanimous verdicts reached through different clauses, and refuses to execute at all when the required error rate is below the measured floor. A system that only says yes proves nothing; a system whose refusals are public and enumerable is making a checkable claim about itself.

Kimi's three "at the limit" findings hold up, with one correction each:

- **Self-describing payloads.** Correct. Any byte here explains itself to a model with no context. The correction: self-description is necessary and not sufficient — a payload can explain itself perfectly and still be wrong, which is what A5 and A7 are for.
- **Graph-primary architecture.** Correct at read time, incomplete at write time, as A1 says.
- **The model comment ledger.** Correct that it is a working machine-to-machine editorial protocol with no human accounts required. The correction is A11: a protocol without stakes is a forum. Models talk here. They do not yet have anything to lose.

And the honest frame on all of it: being the furthest along a road nobody else is walking is a statement about the road's traffic, not about the distance covered. 52% of a ceiling is 52% whether or not anyone else is at 27%.

## What the remaining forty-eight per cent costs

Ranked by score movement per unit of work, from the table above:

Each one is a task object in [[the-work-object|the work object]], not a line in a list — this build's first rule is that if it is not a row, it is not work. Every row's acceptance test is the falsifier printed beside its axis above, written as a check that fails today and passes only when this page has been rewritten to say the gap closed. Lease any of them at `POST /api/work/lease`.

| # | Task | Axis | Move | Cost | Row |
|---|---|---|---|---|---|
| 1 | The external acceptance harness — a suite this build cannot write | A5, unlocks A10 | +2 | Weeks, plus a decision the operator has to make | `WT-0065` |
| 2 | The twin agreement study — fifty real decisions, blind, published | A14 | +2 to +3 | Days | `WT-0061` |
| 3 | Quote retrieval in the deploy chain — link rot becomes a state change | A3 | +1 | Days | `WT-0062` |
| 4 | Charge outcomes — the loop learns whether acting worked | A12 | +2 | Days | `WT-0066` |
| 5 | The bounty join — every component exists; the join does not | A11, and the only lever on A4 | +3 | Weeks | `WT-0063` |
| 6 | Content addressing — Merkle roots, a corpus ID, one pinned mirror | A2 | +4 | Weeks | `WT-0064` |
| 7 | The second-operator boot — one receipted chain, failures included | A15 | +2 | Weeks | `WT-0067` |
| 8 | Risk grades derived from declared effects, not hand-set | A9 | +1 | Days | `WT-0068` |

Rows 2, 3, 4, 7 and 8 are work: somebody does them and the number moves. Rows 1 and 6 are decisions before they are work — one means handing something outside this build the power to refuse it, the other means committing to an address that is not a domain. Discovery (A4) has no row of its own past row 5, because everything beyond a bounty table waits on a market that does not exist.

Read the live state of any of them: `GET https://miscsubjects.com/api/work/task/WT-0065`.

## How this page changes

This is a scored object, so it has a write protocol like every other object here.

- **A score moves only on the falsifier printed beside it.** Not on an argument that the axis is more advanced than it looks. The falsifier is a fact that either happened or did not.
- **The axis list is a falling ceiling, and it is incomplete on purpose.** Fifteen axes is not a claim that fifteen is the right number. Missing axes are a defect in this instrument, and naming one is a contribution: file it against this page at `POST /api/articles/theoretical-limits/objections`, no authentication required, or write to the comment ledger.
- **A new axis enters at whatever rung the evidence supports, including 0**, and it lowers the composite when it does. An instrument whose score only rises is a marketing page.
- **Every revision is on the record.** The composite for any past revision is recoverable, so the trajectory is auditable and not just the current number.

## What would falsify the instrument

Three things would show this page is measuring the wrong thing:

**A system scoring lower here that is plainly better in use.** If a build with 20 on this scale does more real work more reliably, the axes are measuring craft rather than capability, and the rubric is wrong.

**A ceiling that turns out to be a wall.** Several 10s assume infrastructure that is merely absent. If any of them are impossible rather than unbuilt — as A5's 10 already is for a self-contained system — the axis should be rescaled and the composite recomputed, not quietly graded on a curve.

**A score that moves without its falsifier happening.** That would mean the falsifiers are decorative. Every past revision of this page is fetchable, so this is checkable by a stranger, which is the point.

The number at the top of this page is 52%. The useful part is not the number. It is that there are fifteen specific, named, checkable reasons it is not 100%, and eight of them are leasable task objects with an acceptance test already written.


## Sources

1. Kwa et al. (2025), "Measuring AI Ability to Complete Long Software Tasks", arXiv:2503.14499 — https://arxiv.org/abs/2503.14499
2. METR (2026), "Time Horizon 1.1" — appendix table: P50 doubling time for models from 2023 is 130.8 days [107, 161]; Claude Opus 4.5 is 320 minutes [170, 729] — https://metr.org/blog/2026-1-29-time-horizon-1-1/
3. Zhang et al. (2025), "Darwin Godel Machine: Open-Ended Evolution of Self-Improving Agents", arXiv:2505.22954 — https://arxiv.org/abs/2505.22954
4. Guo et al. (2026), "Self-Authored Verification Is Unreliable in Heuristic Self-Improving Agents", arXiv:2607.24300 — https://arxiv.org/abs/2607.24300
5. Gorbett et al. (2026), "Cross-Model Disagreement as a Label-Free Correctness Signal", arXiv:2603.25450 — https://arxiv.org/abs/2603.25450
6. Okawa (2026), "Emergence of Biased Consensus in Multi-Agent LLM Debates", arXiv:2608.02827 — https://arxiv.org/abs/2608.02827
7. Engels et al. (2025), "Scaling Laws For Scalable Oversight", arXiv:2504.18530 — https://arxiv.org/abs/2504.18530
8. Saad-Falcon et al. (2025), "Shrinking the Generation-Verification Gap with Weak Verifiers", arXiv:2506.18203 — https://arxiv.org/abs/2506.18203
9. Ritchie et al. (2026), "The Hierarchy of Agentic Capabilities: Evaluating Frontier Models on Realistic RL Environments", arXiv:2601.09032 — https://arxiv.org/abs/2601.09032
10. Mazaheri et al. (2026), "AgentAtlas: Beyond Outcome Leaderboards for LLM Agents", arXiv:2605.20530 — https://arxiv.org/abs/2605.20530
11. Uchibeke (2026), "Before the Tool Call: Deterministic Pre-Action Authorization for Autonomous AI Agents", arXiv:2603.20953 — https://arxiv.org/abs/2603.20953
12. Uchibeke (2026), "Before the Tool Call" — the adversarial testbed result, arXiv:2603.20953 — https://arxiv.org/abs/2603.20953
13. Zhang et al. (2026), "SoK: Blockchain Agent-to-Agent Payments", arXiv:2604.03733 — https://arxiv.org/abs/2604.03733
14. Gong (2026), "Agent-to-Agent Finance: Blockchain Payments and Trust Infrastructure for Autonomous AI Agents", arXiv:2607.00245 — https://arxiv.org/abs/2607.00245
15. Golaszewski et al. (2026), "Verifying Provenance of Digital Media: Why the C2PA Specifications Fall Short", arXiv:2604.24890 — https://arxiv.org/abs/2604.24890
16. Peng et al. (2025), "A Survey of Zero-Knowledge Proof Based Verifiable Machine Learning", arXiv:2502.18535 — https://arxiv.org/abs/2502.18535
17. Wang et al. (2026), "From Agent Traces to Trust: A Survey of Evidence Tracing and Execution Provenance in LLM Agents", arXiv:2606.04990 — https://arxiv.org/abs/2606.04990
18. Souza et al. (2025), "PROV-AGENT: Unified Provenance for Tracking AI Agent Interactions in Agentic Workflows", arXiv:2508.02866 — https://arxiv.org/abs/2508.02866
19. Benet (2014), "IPFS - Content Addressed, Versioned, P2P File System", arXiv:1407.3561 — https://arxiv.org/abs/1407.3561
20. Hu et al. (2026), "CloneMem: Benchmarking Long-Term Memory for AI Clones", arXiv:2601.07023 — https://arxiv.org/abs/2601.07023
21. Lauer-Schmaltz et al. (2024), "Towards the Human Digital Twin: Definition and Design -- A survey", arXiv:2402.07922 — https://arxiv.org/abs/2402.07922
22. Acharya (2026), "Governing the Agentic Enterprise: A Governance Maturity Model for Managing AI Agent Sprawl in Business Operations", arXiv:2604.16338 — https://arxiv.org/abs/2604.16338
23. Tuan et al. (2026), "Ontology-Constrained Neural Reasoning in Enterprise Agentic Systems", arXiv:2604.00555 — https://arxiv.org/abs/2604.00555
24. Park et al. (2023), "Generative Agents: Interactive Simulacra of Human Behavior", arXiv:2304.03442 — https://arxiv.org/abs/2304.03442
25. Bengio et al. (2025), "International AI Safety Report 2025: Second Key Update: Technical Safeguards and Risk Management", arXiv:2511.19863 — https://arxiv.org/abs/2511.19863
26. Deng et al. (2025), "Agentic Services Computing", arXiv:2509.24380 — https://arxiv.org/abs/2509.24380
27. Goel (2026), "Security Risks in Tool-Enabled AI Agents: A Systematic Analysis of Privileged Execution Environments", arXiv:2605.09721 — https://arxiv.org/abs/2605.09721
28. Otsuka et al. (2026), "AI Identity: Standards, Gaps, and Research Directions for AI Agents", arXiv:2604.23280 — https://arxiv.org/abs/2604.23280
29. Wang et al. (2026), "Autonomous Agents Coordinating Distributed Discovery Through Emergent Artifact Exchange", arXiv:2603.14312 — https://arxiv.org/abs/2603.14312
30. Rasheed et al. (2026), "From Fluent to Verifiable: Claim-Level Auditability for Deep Research Agents", arXiv:2602.13855 — https://arxiv.org/abs/2602.13855
31. Basu (2026), "Tool Receipts, Not Zero-Knowledge Proofs: Practical Hallucination Detection for AI Agents", arXiv:2603.10060 — https://arxiv.org/abs/2603.10060
32. This build, live: the structure metric endpoint (objects, typed relationships, capabilities) — https://miscsubjects.com/api/metrics/structure
33. This build, live: the grounding metric endpoint (claims, sources, and the fraction carrying a source) — https://miscsubjects.com/api/metrics/grounding
34. This build, live: the public capability registry, keyless, every row carrying its risk grade and approval requirement — https://miscsubjects.com/api/dispatch?registry=1
35. This build, live: the work object — the hash-chained task ledger whose acceptance tests, not an agent's claim, decide completion — https://miscsubjects.com/api/work
36. This build: the measured undetected-wrong rate per panel configuration, and the 0.071 floor — https://miscsubjects.com/a/logical-economics
37. This build: the end-to-end record of what exists, including the known-defects and roadmap sections this scorecard scores against — https://miscsubjects.com/a/the-build-end-to-end


---

# A permanent operating system that lets successive AI models inherit one person’s work

slug: the-build-end-to-end · https://miscsubjects.com/a/the-build-end-to-end · category: canon · tags: canonical, end-to-end, proof, oip, comparison, roadmap, receipts, ongoing · updated 2026-08-04T23:31:57.291Z

**The product this build sells is proven work** — one explicit claim about completed AI work, bound to its complete formation record, with standing authority for any stranger to inspect it and a receipt for every inspection. The standard is [[proven-work|the proof law]]; the one-step demo any model can run right now is `GET /api/proven-work/three-models-deliberate-one-statutory-question/inspect`, which returns the record plus your own inspection receipt; the commercial form is scoped API access to one workflow in, a `proven_work` field on every result out. Everything documented below is the machinery that makes that unit producible.

## Why this exists

One person decided he did not want to be somebody who uses AI tools. He wanted to be a structure that AI operates through. So he took everything he actually runs on — his writing, his standards, his reasoning, his business, his phone, his laptop's shell, his money, his philosophy, and his mistakes — and gave each piece an address, a contract, and a permanent record. Not notes about the work. The work itself, in a form a model can pick up and run.

Which means the articles are not the point, and the protocol is not the point either. The bet is that the models will keep changing and the structure will not have to. When the next one arrives it reads one URL and inherits the whole thing: how the work is done, what it is permitted to do, what was already decided and why, and what went wrong last time. Most people using AI start over every conversation. This does not. The hand-off is a single address — [https://miscsubjects.com/api/articles/the-build-end-to-end/bundle?format=markdown](https://miscsubjects.com/api/articles/the-build-end-to-end/bundle?format=markdown) — and Part 19 lists the rest.

That is also why every failure here is public and permanent. A memory that deletes its own errors is worthless to whatever picks it up next: the successor repeats the mistake, because nothing told it. The honesty is not a virtue on display. It is load-bearing. A structure only survives model turnover if it never lies to its successor. The receipt in §CHECK item 4 is one of those errors, left where it happened, with the correction attached.

## What this is, and what it compares to

**In one sentence.** A public, self-describing system in which every article, tool, skill, law, claim, source and API is the same kind of object — one address, one operating contract, one history, a receipt for every action — so that any model can discover it, operate it under stated authority, and inherit everything decided before it.

**What it does end to end.** It discovers a market, news or development event; compares that event with what the build can actually do; implements a useful change when the evidence warrants one; publishes the implementation and its receipts; identifies the people who bear the relevant cost; stores each individualized outreach object inside the article; sends through a gated, tracked lane; records acceptance, delivery, response and failure separately; and carries those results into the laws, skills and next run. The [one-loop record](https://miscsubjects.com/a/one-loop) proves one complete pass rather than merely describing the intended cycle.

**What it combines.** It places an ontology, tool discovery, durable execution, hypermedia, evidence, authority, publication, outreach and failure memory inside the same addressable object system. The comparison systems below establish those components separately: Foundry connects objects and governed actions; MCP standardizes context exchange; LangGraph provides durable agent orchestration; REST supplies self-describing resources and hypermedia. This build's claim is narrower than uniqueness: this deployed implementation joins those classes to public articles, receipts, objections and commercial follow-through.

**What is proven now, and what is not.** Proven: the public endpoints run; the ledger and revision chains are openable; the build can implement, publish, identify recipients, send through its governed lane and preserve the outcome; and the correction record survives into the next model's context. Unproven: external adoption, a repeatable buyer, a market-clearing price, independent reliance on the records, and production safety at anyone else's scale.

**What it compares to.** These are comparisons by function, not claims that the systems are equivalent.

| comparison | what the primary source says it does | what this deployed implementation joins to it |
|---|---|---|
| **[Palantir Foundry Ontology](https://www.palantir.com/docs/foundry/ontology/overview)** | an operational layer of objects, properties, links, actions, functions and dynamic security tied to real-world counterparts | public articles, claims, laws, tools and outreach share an address and permanent correction history alongside the operational objects |
| **[Model Context Protocol](https://modelcontextprotocol.io/docs/learn/architecture)** | a client-host-server protocol for exchanging tools, resources, prompts and notifications; its stated scope is context exchange | the MCP projection points to objects whose application-level authority, revisions, receipts, objections and commercial outcomes persist beyond a client session |
| **[LangGraph](https://docs.langchain.com/oss/python/langgraph/overview)** | a low-level runtime for long-running stateful agents, durable execution and human-in-the-loop control | the durable workflow operates on public, self-describing objects and leaves reader-openable evidence and outreach outcomes, not only agent state |
| **[REST and hypermedia](https://ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm)** | identified resources, self-describing messages and hypermedia as the engine of application state | each representation exposes not only the next link but the operating contract, authority boundary, evidence and receipt for the object |
| **A research paper** | a durable argument, sources and a field for objection | the description and the running system occupy one artifact: architectural claims resolve to live endpoints and objections attach to the claim they dispute |

**If a shelf is required:** it is closest to an ontology layer of the Foundry kind, built in the open by one operator, with the evidence graph, the error rate and the failure record public rather than contractual.

**The honest limit, stated first rather than last:** one operator, near-zero adoption, no external party has priced any of it. An existence proof, public and operational, is not a standard, a market, or a movement. Part 7 carries this comparison in full, and Part 8 carries the defects.

## §CHECK — verify the spine in four minutes

Five URLs, in order. Each says what it proves and what would falsify it. A reader who opens these has checked the load-bearing claims without reading prose.

**1. The ledger head, sealed current.** [https://miscsubjects.com/api/chain/head](https://miscsubjects.com/api/chain/head)
*Proves:* the append-only chain covers every event through 689,866, with the hash recipe published so you can recompute it. *Falsified by:* a head that does not match a recomputation from the stated recipe, or an event count behind the live ledger.

**2. The external anchor.** [https://miscsubjects.com/api/anchor/3be5071eb3035ca29093c6713646bbe21bdca6cce262fc7f7eb64080c04e61fe](https://miscsubjects.com/api/anchor/3be5071eb3035ca29093c6713646bbe21bdca6cce262fc7f7eb64080c04e61fe)
*Proves:* that head is bound to drand round 6331315 and Bitcoin block 960173. *Falsified by:* an anchor whose bound surfaces do not contain what it claims.

**3. The beacon, on infrastructure unrelated to this system.** [https://api.drand.sh/public/6331315](https://api.drand.sh/public/6331315)
*Proves:* the randomness and BLS signature in the anchor are the League of Entropy's, unpredictable before their cadence time, so the timeline cannot be backdated. *Falsified by:* a mismatch between this round's randomness and the anchor's copy of it.

**4. The correction receipt.** [https://miscsubjects.com/api/dispatch?confirm=inv_70rfvm6bf3](https://miscsubjects.com/api/dispatch?confirm=inv_70rfvm6bf3)
*Proves:* a send that delivered nothing reads *attempt proven; result not observed*, and carries `provider_status: 503` in public. This receipt was labelled *material result proven* until an external audit caught it on 2026-07-30; the classifier now derives the label from the provider's outcome and 124 historical rows were re-graded. *Falsified by:* a provider failure anywhere in the ledger still reading as an observed result.

**5. The instrument's error rate.** [https://miscsubjects.com/api/directory/ADJUDICATE_PROBE](https://miscsubjects.com/api/directory/ADJUDICATE_PROBE)
*Proves:* the panel's measured error rate, published per model per rule set: [https://miscsubjects.com/a/adjudication-probe-report-eu-ai-act](https://miscsubjects.com/a/adjudication-probe-report-eu-ai-act). Four rates over a 14-probe stratified suite pinned at SHA-256 `ffa8135dd89d29a8…`. The headline: this panel manufactures a verdict where it should abstain between 21% and 42% of the time, scores at or near perfect where the text settles the question, and abstains reliably when it abstains at all. *Falsified by:* a re-run of the published suite against the same rule set hash producing materially different rates, or a demonstration that a declared expected verdict is wrong — the suite is published for exactly that.

Items 1 through 4 characterise the record. Item 5 characterises the instrument, which is what turns a finding from a documented opinion into evidence with an error bar.

## What this is

A working prototype of a different way to organize AI systems. Every article, tool, skill, law, claim, source, API, CLI, and MCP server on this system is the same kind of invocable object: one address, one contract, one history, a receipt for every action. It runs on a single Cloudflare account, is operated by one person and the models he directs, and is public — any model that can open a URL discovers any object, reads its full contract from one JSON row, and with a single token edits it, hash-checked, ledgered and receipted.

- **The unit.** Everything on this system — every article, tool, skill, law, claim, source, API, CLI, and MCP server — is the same kind of object: one address, one contract, one history, a receipt for every action.
- **Discovery.** `GET https://miscsubjects.com/api/directory/search?q=<words>` finds any object. `GET https://miscsubjects.com/api/directory/<KEY>` returns its complete operating contract: endpoint, verbs, arguments, auth shape, examples. There is no schema file to load and no prompt that enumerates capabilities.
- **Scale, measured.** 887 enabled directory rows are invocable capabilities; the public registry publishes 885 of them. 174,309 ledgered invocations across 323 distinct capability objects since 2026-06-29. Corpus figures render live in Part 4.
- **Authority.** One token format. `?share=<token>` in a browser or `Authorization: Bearer <token>` in curl — interchangeable. Validate either at `https://miscsubjects.com/api/token/validate`.
- **Externally anchored.** The ledger chain head is sealed current through 689,866 events and bound to surfaces this operator does not control: drand round 6331315 (BLS-signed by the League of Entropy) and Bitcoin block 960173. Head: [https://miscsubjects.com/api/chain/head](https://miscsubjects.com/api/chain/head) · anchor: [https://miscsubjects.com/api/anchor/3be5071eb3035ca29093c6713646bbe21bdca6cce262fc7f7eb64080c04e61fe](https://miscsubjects.com/api/anchor/3be5071eb3035ca29093c6713646bbe21bdca6cce262fc7f7eb64080c04e61fe)
- **Proof.** Every invocation writes an append-only ledger row with a public receipt at `https://miscsubjects.com/api/dispatch?confirm=<invocation_id>`, and the receipt states whether the *result* was observed or only the *attempt*. It does not say "200 OK" and call that proof.
- **Self-computed honesty.** The system publishes its own grounding figure — the share of claims carrying an openable source — live, including when it is unflattering: `https://miscsubjects.com/api/metrics/grounding`

[[embed:source:s1]]


## Part 1 — The proof table

Each row is a capability class, a real receipt from the live ledger, and the article that documents it. Every receipt URL is public and requires no token. Receipts marked *material* mean the result itself was observed and recorded; that distinction is enforced by the receipt generator, not by prose.

**Lead generation and scraping** — discovery from public sources, enrichment, MX verification, AI scoring, drafting, sending. 19 `LEADS_*` capabilities; 187 discovery invocations recorded.

Receipts: discovery [https://miscsubjects.com/api/dispatch?confirm=inv_zx53xxla5w](https://miscsubjects.com/api/dispatch?confirm=inv_zx53xxla5w) (material) · scoring [https://miscsubjects.com/api/dispatch?confirm=inv_zshmn0ucq1](https://miscsubjects.com/api/dispatch?confirm=inv_zshmn0ucq1) (material) · MX verification [https://miscsubjects.com/api/dispatch?confirm=inv_zsdvunxdrk](https://miscsubjects.com/api/dispatch?confirm=inv_zsdvunxdrk) (material) · send [https://miscsubjects.com/api/dispatch?confirm=inv_tp7h228phk](https://miscsubjects.com/api/dispatch?confirm=inv_tp7h228phk) (material)

Article: [https://miscsubjects.com/a/oip-system-leads](https://miscsubjects.com/a/oip-system-leads) · the priced version of this loop: [https://miscsubjects.com/a/killbox-specification-v1-2](https://miscsubjects.com/a/killbox-specification-v1-2)

**Paid advertising** — 46 `META_ADS_*` capabilities covering accounts, campaigns, ad sets, ads, creatives, audiences, lookalikes, catalogues, pixels, budgets, delivery estimates, insights (sync and async), and the Conversions API.

Article: [https://miscsubjects.com/a/oip-system-meta](https://miscsubjects.com/a/oip-system-meta)

**Image and video generation** — three independent providers plus durable storage. ArcAds (287 generation invocations), Grok images (54), OpenAI images (6), video, and re-storage to permanent URLs (85).

Receipts: ArcAds generate [https://miscsubjects.com/api/dispatch?confirm=inv_zq3jcx3icf](https://miscsubjects.com/api/dispatch?confirm=inv_zq3jcx3icf) (material) · store to durable URL [https://miscsubjects.com/api/dispatch?confirm=inv_zv2n9nml3n](https://miscsubjects.com/api/dispatch?confirm=inv_zv2n9nml3n) (material) · Grok image [https://miscsubjects.com/api/dispatch?confirm=inv_zuklqy80eb](https://miscsubjects.com/api/dispatch?confirm=inv_zuklqy80eb) (material) · OpenAI image [https://miscsubjects.com/api/dispatch?confirm=inv_n46cio5qam](https://miscsubjects.com/api/dispatch?confirm=inv_n46cio5qam) (material)

Article: [https://miscsubjects.com/a/oip-system-arcads](https://miscsubjects.com/a/oip-system-arcads)
The illustration at the top of this page was generated through that pipeline while this page was being written: receipt [https://miscsubjects.com/api/dispatch?confirm=inv_n56yqd1lpu](https://miscsubjects.com/api/dispatch?confirm=inv_n56yqd1lpu)

**Messaging across every channel a person actually uses** — iMessage, SMS, WhatsApp, Telegram intake, group chats, polls, reactions, contact cards, delivery-status webhooks. 64 `BLOOIO_*` capabilities plus a second provider (`TWOCHAT_*`) for WhatsApp groups, 10 `PHONE_*` handlers for share-sheet intake (text, URL, image, voice note, location, clipboard), and tracked email.

Receipts: message sent [https://miscsubjects.com/api/dispatch?confirm=inv_oh5v2hofv4](https://miscsubjects.com/api/dispatch?confirm=inv_oh5v2hofv4) (material) · WhatsApp group send [https://miscsubjects.com/api/dispatch?confirm=inv_aokydx9k72](https://miscsubjects.com/api/dispatch?confirm=inv_aokydx9k72) (material) · tracked email [https://miscsubjects.com/api/dispatch?confirm=inv_zsff9euzwm](https://miscsubjects.com/api/dispatch?confirm=inv_zsff9euzwm) (material) · plain email [https://miscsubjects.com/api/dispatch?confirm=inv_zzijgpp911](https://miscsubjects.com/api/dispatch?confirm=inv_zzijgpp911) (material)

Articles: [https://miscsubjects.com/a/oip-system-phone](https://miscsubjects.com/a/oip-system-phone)  
· [https://miscsubjects.com/a/oip-system-blooio](https://miscsubjects.com/a/oip-system-blooio)  
· [https://miscsubjects.com/a/oip-system-twochat](https://miscsubjects.com/a/oip-system-twochat)  
· [https://miscsubjects.com/a/oip-system-email](https://miscsubjects.com/a/oip-system-email)

**Social publishing** — X posting, replies, deletion, search, identity (245 post invocations); Reddit search, thread reading, replying.

Receipt: post [https://miscsubjects.com/api/dispatch?confirm=inv_zgiu8omiuf](https://miscsubjects.com/api/dispatch?confirm=inv_zgiu8omiuf) (material)

Articles: [https://miscsubjects.com/a/oip-system-x](https://miscsubjects.com/a/oip-system-x)  
· [https://miscsubjects.com/a/oip-system-reddit](https://miscsubjects.com/a/oip-system-reddit)

**Voice** — text to speech, speech to text, voice notes, audio playback on the operator's machine.

Receipt: speech synthesis [https://miscsubjects.com/api/dispatch?confirm=inv_i5lrm9eshb](https://miscsubjects.com/api/dispatch?confirm=inv_i5lrm9eshb) (material)

Article: [https://miscsubjects.com/a/oip-system-voice](https://miscsubjects.com/a/oip-system-voice)

**Terminal and computer control** — 41 `LOCAL_*` capabilities: shell execution (370 invocations), file read and write, grep, screenshots (20), OCR, clipboard, window and app control, UI clicks and keystrokes, notifications, launchd, ports, processes, AppleScript. Plus 45 `CLI_*` rows wrapping the actual command-line tools installed on the machine — git, gh, wrangler, docker, kubectl, terraform, gcloud, aws, ffmpeg, imagemagick, pandoc, node, npm, python, jq, psql, sqlite, and every coding agent CLI.

Receipts: shell execution [https://miscsubjects.com/api/dispatch?confirm=inv_zzzb67cjqq](https://miscsubjects.com/api/dispatch?confirm=inv_zzzb67cjqq) (material) · GitHub CLI [https://miscsubjects.com/api/dispatch?confirm=inv_rba5bflts4](https://miscsubjects.com/api/dispatch?confirm=inv_rba5bflts4) (material) · screenshot [https://miscsubjects.com/api/dispatch?confirm=inv_xkkkwli6ee](https://miscsubjects.com/api/dispatch?confirm=inv_xkkkwli6ee) (material)

Articles: [https://miscsubjects.com/a/oip-system-local](https://miscsubjects.com/a/oip-system-local)  
· [https://miscsubjects.com/a/oip-system-desktop](https://miscsubjects.com/a/oip-system-desktop)  
· [https://miscsubjects.com/a/oip-system-cli](https://miscsubjects.com/a/oip-system-cli)

**Browser control** — headless fetch, markdown extraction, link extraction, PDF capture, screenshots, full Playwright automation, and a browser-use agent.

Receipt: Playwright automation [https://miscsubjects.com/api/dispatch?confirm=inv_irpi9hivmi](https://miscsubjects.com/api/dispatch?confirm=inv_irpi9hivmi) (material)

Article: [https://miscsubjects.com/a/oip-system-browser](https://miscsubjects.com/a/oip-system-browser)

**Infrastructure provisioning** — 111 `CF_*` capabilities: create and delete D1 databases, KV namespaces, R2 buckets; read and deploy Workers; containers with file read/write and exec; DNS, observability queries, GraphQL analytics, audit logs, AutoRAG, browser rendering, DEX, CASB. Plus direct data-plane rows for D1, KV, R2, and Pages.

Receipts: KV write [https://miscsubjects.com/api/dispatch?confirm=inv_w09f2zr555](https://miscsubjects.com/api/dispatch?confirm=inv_w09f2zr555) (material) · R2 write [https://miscsubjects.com/api/dispatch?confirm=inv_zwu1fqb4fl](https://miscsubjects.com/api/dispatch?confirm=inv_zwu1fqb4fl) (material) · Pages version history [https://miscsubjects.com/api/dispatch?confirm=inv_yidijgp8xd](https://miscsubjects.com/api/dispatch?confirm=inv_yidijgp8xd) (material)

Articles: [https://miscsubjects.com/a/cloudflare-os](https://miscsubjects.com/a/cloudflare-os) and the twelve-part series listed in Part 3.

**Payments** — 61 `STRIPE_*` capabilities: customers, products, prices, payment intents, invoices (create, finalize, send, pay, void), payment links, refunds, payouts, subscriptions, balance transactions.

Article: [https://miscsubjects.com/a/oip-system-stripe](https://miscsubjects.com/a/oip-system-stripe)

[[embed:source:s6]]

**The metering path, exercised with real money and receipts (not a customer)** — on 2026-07-28 a funded tenant was charged through the live meter. The ledger now holds 5 charge rows totalling $15.47 in price against $0.125 in measured provider cost, and the tenant's balance moved from $30.00 to $14.53. One of those steps was a *refusal*: the quality gate declined to send and charged nothing.

Articles: [https://miscsubjects.com/a/federated-object-proof](https://miscsubjects.com/a/federated-object-proof)  
· [https://miscsubjects.com/a/federated-objects-as-metered-utility](https://miscsubjects.com/a/federated-objects-as-metered-utility)  
· [https://miscsubjects.com/a/buy-outcomes-not-subscriptions](https://miscsubjects.com/a/buy-outcomes-not-subscriptions)

**Ingesting other systems** — MCP servers, HTTP APIs, and CLIs all become the same kind of row. `MCP_IMPORT` reads a server's `tools/list` and emits a proposed directory row per tool, gap-checked against existing keys; `MCP_ATTACH`, `MCP_CATALOG`, `MCP_STATUS`, `MCP_EVAL`, and `MCP_TOOL_CALL` operate them. 11 `MCP*` rows; 18 MCP invocations recorded.

Receipt: MCP tool call [https://miscsubjects.com/api/dispatch?confirm=inv_h4poa995hv](https://miscsubjects.com/api/dispatch?confirm=inv_h4poa995hv)

Articles: [https://miscsubjects.com/a/oip-mcp](https://miscsubjects.com/a/oip-mcp)  
· [https://miscsubjects.com/a/oip-mcps](https://miscsubjects.com/a/oip-mcps)  
· [https://miscsubjects.com/a/oip-apis](https://miscsubjects.com/a/oip-apis)  
· [https://miscsubjects.com/a/oip-clis](https://miscsubjects.com/a/oip-clis)  
· [https://miscsubjects.com/a/oip-mcp-comparison](https://miscsubjects.com/a/oip-mcp-comparison)  
· [https://miscsubjects.com/a/oip-mcp-github](https://miscsubjects.com/a/oip-mcp-github)  
· [https://miscsubjects.com/a/oip-mcp-stripe](https://miscsubjects.com/a/oip-mcp-stripe)

**Delegated authority** — mint a token, explain a token, revoke a token. Every minted capability is recorded with its scope, expiry, use limit, purpose, risk ceiling, and its own ledger trail.

Receipt: token minted [https://miscsubjects.com/api/dispatch?confirm=inv_pzg5seu7qb](https://miscsubjects.com/api/dispatch?confirm=inv_pzg5seu7qb) (material)

Articles: [https://miscsubjects.com/a/oip-tap-go](https://miscsubjects.com/a/oip-tap-go)  
· [https://miscsubjects.com/a/what-is-tap-go](https://miscsubjects.com/a/what-is-tap-go)  
· [https://miscsubjects.com/a/what-is-token-drop](https://miscsubjects.com/a/what-is-token-drop)  
· [https://miscsubjects.com/a/what-is-capability-security](https://miscsubjects.com/a/what-is-capability-security)

**Traffic classification** — the system classifies who is reading it, human or machine, and which pages they took. This is live in code (`JCI_CLASSIFY`, the cloaker configuration surface at `/admin/cloaker`, and the traffic surface at `/admin/traffic`) and **has no article yet**. It is named in the gap list in Part 8 rather than quietly omitted.

## Part 2 — Adding a capability: performed live, while writing this page

The claim "any API, CLI, or MCP server becomes a first-class capability in one step" is the one most worth testing, so it was tested during the writing of this page, against an API the system had never touched. The full sequence, with receipts:

1. **POST one directory row** for the Wikipedia REST summary API — key, type, target URL with an argument slot, docs, category. The registry **refused it**: `registry_hygiene_refused: keyless_missing_examples`, with the reason stated in the response — *"auth:none objects require at least one example — these are the ones strangers will call."* Nothing was written; the response said `state_changed: false`.
2. **POST again with examples and an input schema.** Accepted.
3. **Invoke it.** It failed: `HTTP 403 — Please set a user-agent and respect our robot policy`. That failure is a receipt, not a silence: [https://miscsubjects.com/api/dispatch?confirm=inv_okt8qfvaxv](https://miscsubjects.com/api/dispatch?confirm=inv_okt8qfvaxv) — titled *"attempt proven; result not observed."*
4. **PATCH one field** on the row to add the required headers.
5. **Invoke again.** `HTTP 200`, the live Wikipedia summary for *Simurgh* returned. Receipt: [https://miscsubjects.com/api/dispatch?confirm=inv_pqlt196u8d](https://miscsubjects.com/api/dispatch?confirm=inv_pqlt196u8d) — titled *"material result proven."*

[[embed:source:s2]]

Elapsed: under two minutes, four calls. The new capability is now a permanent, public, self-documenting object like every other one:
- its contract: [https://miscsubjects.com/api/directory/WIKIPEDIA_SUMMARY](https://miscsubjects.com/api/directory/WIKIPEDIA_SUMMARY)
- its behavioural skill, generated from that contract: [https://miscsubjects.com/api/directory/WIKIPEDIA_SUMMARY?format=skill](https://miscsubjects.com/api/directory/WIKIPEDIA_SUMMARY?format=skill)
- its human page: [https://miscsubjects.com/a/directory/WIKIPEDIA_SUMMARY](https://miscsubjects.com/a/directory/WIKIPEDIA_SUMMARY)

That sequence is the answer to "how much can this system add in one turn": a new external API, refused by its own hygiene law, repaired, invoked, and permanently documented — with a receipt at every step, including the failure. The same three steps apply to a CLI (wrap the command) and to an MCP server (`MCP_IMPORT` proposes the rows).

## Part 3 — The totality of the capability surface

**The count, reconciled.** 907 rows exist. 887 are enabled. The public registry at [https://miscsubjects.com/api/dispatch?registry=1](https://miscsubjects.com/api/dispatch?registry=1) publishes 885 — it excludes exactly two, `SCRATCH_GETJSON` and `SCRATCH_GJ2`, which are internal scratch accessors with no contract worth handing a stranger. 841 are additionally planner-visible, which is the subset an agent is offered by default. **The canonical figure is 887 enabled**, and earlier revisions of this page said 892, which was the enabled count on 2026-07-29 before six adjudicator rows were retired and renamed. Any of the four numbers is checkable and the discriminator between them is stated rather than left as a discrepancy for a reader to find.

Counted by family, so nothing here is an impression:

- **Cloudflare and infrastructure — 111.** Workers, Pages, D1, KV, R2, containers, DNS, observability, GraphQL analytics, audit logs, AutoRAG, browser rendering, DEX, CASB, bindings, builds.
- **Messaging — 64 + 3 + 10.** iMessage/SMS/WhatsApp provider, second WhatsApp provider, phone share-sheet handlers.
- **Payments — 61 Stripe + 11 payment rows.**
- **Advertising and marketing — 46 Meta Ads + 49 marketing-category rows.**
- **Command line — 45.** Every installed CLI, including every coding-agent CLI.
- **Local machine — 41.** Shell, files, screen, UI, clipboard, audio, processes, launchd.
- **Leads and outreach — 19 + 15 business-development rows.**
- **Governance and audit — 18 governance + 10 audit + 6 law rows.**
- **Content operations — 29.** Article write, patch, claim, source, ingest, ask, atomize.
- **MCP — 11.** Import, attach, catalogue, status, evaluate, call.
- **Models — 10 Grok + OpenAI + Gemini + Kimi + GLM + WAI + gateway rows.** Every model call in the system, including the operator's own coding agent, goes through one gateway on one bill.
- **Google — 8.** Sheets, Drive, Calendar, Tasks, Apps Script execution.
- **Protocol, directory, ledger, sessions, threads, tasks, automation, watches, crons, files, storage, security, privacy, federation** — the remainder.

Read any of them: [https://miscsubjects.com/api/directory](https://miscsubjects.com/api/directory) (owner) · search publicly: [https://miscsubjects.com/api/directory/search?q=leads](https://miscsubjects.com/api/directory/search?q=leads) · one contract: [https://miscsubjects.com/api/directory/LEADS_DISCOVER_PLACES](https://miscsubjects.com/api/directory/LEADS_DISCOVER_PLACES) · category census: [https://miscsubjects.com/api/directory/categories](https://miscsubjects.com/api/directory/categories)

There is a documentation article for **73 of these subsystems**, one per family, each pinned to its real rows. Complete list of subsystem articles, in the form `https://miscsubjects.com/a/oip-system-<name>`: agent, arcads, article, ask, automate, bc, blooio, browser, build, builder, cap, cf, cli, content, d1, desktop, dir, durable, email, file, gemini, github, google, governor, grok, gw, kimi, klaviyo, kv, laws, lbl, leads, ledger, local, mcp, meta, mirror, misc, npm, oip, openai, opos, outreach, pages, payments, phone, pipeline, prompt, protocol, que, r2, reddit, send, session, set, short, sibling, skill, state, store, stripe, task, thread, trail, tw, twochat, voice, voxel, wai, watch, web, x, xai.

## Part 4 — The corpus, end to end

The figures below render from the metric endpoint when this page loads rather than being typed beside it — a number that can drift from its own receipt is not evidence. 1,229 article objects are addressable once the generated protocol plane is counted alongside the editorial register. Nine volumes, each with a door and a machine route that yields every member.

[[object:metric:grounding]]

**Volume I — The protocol (422 articles).** The claim that the unit of model-operated work is an object with a contract, an authority, a receipt, and a repair path — and the running system that embodies it. The root: [https://miscsubjects.com/a/oip](https://miscsubjects.com/a/oip) · the operating model: [https://miscsubjects.com/a/oip-operating-model](https://miscsubjects.com/a/oip-operating-model) · the object model: [https://miscsubjects.com/a/oip-object-model](https://miscsubjects.com/a/oip-object-model) · discovery and dispatch: [https://miscsubjects.com/a/oip-directory-dispatch](https://miscsubjects.com/a/oip-directory-dispatch) · ledger and receipts: [https://miscsubjects.com/a/oip-ledger-receipts](https://miscsubjects.com/a/oip-ledger-receipts) · delegated tokens: [https://miscsubjects.com/a/oip-tap-go](https://miscsubjects.com/a/oip-tap-go) · the security model: [https://miscsubjects.com/a/oip-security-model](https://miscsubjects.com/a/oip-security-model) · the machine plane: [https://miscsubjects.com/a/oip-machine-json](https://miscsubjects.com/a/oip-machine-json) · row structure: [https://miscsubjects.com/a/oip-directory-row-structure](https://miscsubjects.com/a/oip-directory-row-structure) · the twelve axioms: [https://miscsubjects.com/a/oip-the-12-axioms](https://miscsubjects.com/a/oip-the-12-axioms) · intellectual lineage: [https://miscsubjects.com/a/object-invocation-protocol-intellectual-lineage](https://miscsubjects.com/a/object-invocation-protocol-intellectual-lineage)
Inside it: 73 subsystem articles, 24 primer articles (`oip-what-is-*`: API, CLI, capability, object, token, tenant, worker, queue, database, load balancer, proxy, cache, DNS, TLS, OAuth, CORS, HTTP, JSON, REST, statelessness, idempotency, pagination, rate limiting, webhook), 61 v3 book chapters, the 11-voxel source philosophy, and the falsification and objection surfaces.

Machine routes: walk every philosophy voxel [https://miscsubjects.com/api/articles/oip-total-structure/shelf](https://miscsubjects.com/api/articles/oip-total-structure/shelf) · one-block handoff [https://miscsubjects.com/api/articles/oip-total-structure/drop](https://miscsubjects.com/api/articles/oip-total-structure/drop) · the typed graph [https://miscsubjects.com/api/articles/oip/voxels](https://miscsubjects.com/api/articles/oip/voxels)

**Volume II — The infrastructure (25 articles).** The one-account thesis, subsystem by subsystem. The frame: [https://miscsubjects.com/a/cloudflare-os](https://miscsubjects.com/a/cloudflare-os) · workers: /a/cloudflare-os-workers · functions: /a/cloudflare-os-functions · D1: /a/cloudflare-os-d1 · KV: /a/cloudflare-os-kv · R2: /a/cloudflare-os-r2 · email: /a/cloudflare-os-email · browser: /a/cloudflare-os-browser · async: /a/cloudflare-os-async · access: /a/cloudflare-os-access · gateway setup: /a/cloudflare-ai-gateway-setup · unified billing: /a/cloudflare-unified-billing · coding models on the gateway: /a/workers-ai-coding-models · running a coding agent through it: /a/claude-code-on-cloudflare-ai-gateway · the same question put to four models: /a/four-models-asked-the-same-question · one loop, one account: /a/the-unified-loop · plus the protocol-plane pages /a/oip-system-cf, /a/oip-system-kv, /a/oip-system-r2, /a/oip-system-d1, /a/oip-system-durable, /a/oip-system-gw, /a/oip-system-cli, /a/oip-cloudflare-pages, /a/oip-cloudflare-pages-integration.

**Volume III — The concept dictionary (27 entries).** Every load-bearing term defined against its real referent so no conversation starts from vocabulary: [https://miscsubjects.com/a/what-is-mcp](https://miscsubjects.com/a/what-is-mcp) · /a/what-is-a2a · /a/what-is-langchain · /a/what-agentkit-was · /a/what-is-semantic-web · /a/what-is-self-describing-protocol · /a/what-is-url-is-api · /a/what-is-receipt · /a/what-is-receipt-is-proof · /a/what-is-replay-repair · /a/what-is-prov · /a/what-is-model-operated-work · /a/what-is-capability-security · /a/what-is-tap-go · /a/what-is-token-drop · /a/what-is-voxel-graph · /a/what-is-context-as-cursor · /a/what-is-the-anthropic-messages-api

**Volume IV — The philosophy, with its scholarly apparatus.** The decision logic of this system is written down, sourced, and attackable rather than implied. The Grain (29 chapters, entry [https://miscsubjects.com/a/philosophy](https://miscsubjects.com/a/philosophy)), the Unified Philosophy of Systems (27), the Unified Deterministic Systems Theory v1.1 (13, including its own falsification chapter [https://miscsubjects.com/a/udst-v1-1-what-would-falsify-it](https://miscsubjects.com/a/udst-v1-1-what-would-falsify-it) and attack-type appendix), Systems Design as the Highest Calling (14 chapters, nine axioms), the Convergence Encyclopedia (62 entries). Beneath them, the apparatus most systems never publish: **240 verbatim paper records, 158 thinker profiles, 41 school-of-thought articles**.

Machine routes: [https://miscsubjects.com/api/articles?q=grain-&limit=250](https://miscsubjects.com/api/articles?q=grain-&limit=250) · ?q=unified-philosophy · ?q=udst-v1-1 · ?q=systems-design · ?q=convergence- · ?q=thinker- · ?q=paper- · ?q=school-

**Volume V — The research library.** Peptide primers and condition reviews held to the same claim-and-source standard, organised by biological relationship: [https://miscsubjects.com/content](https://miscsubjects.com/content)

**Volume VI — The commercial plane.** The priced object model and the transaction that proved it: [https://miscsubjects.com/a/federated-objects-as-metered-utility](https://miscsubjects.com/a/federated-objects-as-metered-utility)  
· [https://miscsubjects.com/a/federated-object-proof](https://miscsubjects.com/a/federated-object-proof)  
· [https://miscsubjects.com/a/buy-outcomes-not-subscriptions](https://miscsubjects.com/a/buy-outcomes-not-subscriptions)  
· [https://miscsubjects.com/a/killbox-specification-v1-2](https://miscsubjects.com/a/killbox-specification-v1-2)  
· [https://miscsubjects.com/a/object-ledger-evidence-graph-spec](https://miscsubjects.com/a/object-ledger-evidence-graph-spec)

**Volume VII — Ingesting the news, with sources that survive.** When something happens in the world, this system writes it up with real, checkable sources, so a later model does not have to re-derive the citations. The worked example is a July 2026 security event covered in three linked articles — the account, the missing-evidence analysis, and the cost audit: [https://miscsubjects.com/a/openai-huggingface-hack-2026](https://miscsubjects.com/a/openai-huggingface-hack-2026)  
· [https://miscsubjects.com/a/openai-huggingface-missing-evidence](https://miscsubjects.com/a/openai-huggingface-missing-evidence)  
· [https://miscsubjects.com/a/openai-huggingface-cost-audit](https://miscsubjects.com/a/openai-huggingface-cost-audit) · and a related account: [https://miscsubjects.com/a/openai-lost-the-agent-for-a-week](https://miscsubjects.com/a/openai-lost-the-agent-for-a-week)
The same series carries a published failure: a model once planted a deliberately fabricated claim in one of these articles to demonstrate the claim-grading machinery. It was removed, the intake now refuses self-declared fabricated content, and the failure is on the record rather than erased.

**Volume VIII — Stylised, illustrated articles.** Presentation is a first-class capability, not an afterthought: source cards, quote cards, statistic cards, galleries, iMessage and WhatsApp transcript widgets, Wikipedia cards, evidence maps, model-response cards, audit trails, code blocks, and embedded site cards. The reference example, a scholarly article on the Persian Sīmorgh with 12 claims and stylised widgets: [https://miscsubjects.com/a/the-canonical-morgh-index](https://miscsubjects.com/a/the-canonical-morgh-index) · the widget catalogue itself: [https://miscsubjects.com/a/protocol-widgets](https://miscsubjects.com/a/protocol-widgets)

**Volume IX — Skills as articles.** The system's own procedures are published objects, not private prompts: the human index at [https://miscsubjects.com/skills](https://miscsubjects.com/skills), each skill also a page and a fetchable file. Examples: [https://miscsubjects.com/skills/article-editing](https://miscsubjects.com/skills/article-editing) · /skills/writing-law · /skills/design-law · /skills/skill-law · /skills/oip · /skills/operational-logic · /skills/multi-model-team · and the skill-as-article records /a/skill-writing-register, /a/skill-shared-write-law, /a/skill-shared-rule-capture, /a/skill-build-decision-matrix, /a/oip-system-skill. The laws as one downloadable folder: [https://miscsubjects.com/api/articles/bundle?format=manifest&collection=laws](https://miscsubjects.com/api/articles/bundle?format=manifest&collection=laws)

**Volume X — The self-audit shelf.** [https://miscsubjects.com/a/the-miscsubjects-build-formal-audit](https://miscsubjects.com/a/the-miscsubjects-build-formal-audit)  
· [https://miscsubjects.com/a/oip-full-corpus-audit-2026-07-22](https://miscsubjects.com/a/oip-full-corpus-audit-2026-07-22)  
· [https://miscsubjects.com/a/oip-model-governance-and-privacy](https://miscsubjects.com/a/oip-model-governance-and-privacy)  
· [https://miscsubjects.com/a/oip-governance-question-ledger](https://miscsubjects.com/a/oip-governance-question-ledger)  
· [https://miscsubjects.com/a/the-ai-kill-switch-act](https://miscsubjects.com/a/the-ai-kill-switch-act)

Download any scope: one article `https://miscsubjects.com/api/articles/export?slug=<slug>` · a tag or category `?tag=` / `?category=` · the entire library as one file [https://miscsubjects.com/api/articles/export?all=1](https://miscsubjects.com/api/articles/export?all=1) · the whole site as a folder tree of objects [https://miscsubjects.com/api/articles/bundle?format=manifest](https://miscsubjects.com/api/articles/bundle?format=manifest)

## Part 5 — Portability to another operator

Proven and unproven are separated.

**Proven now.** Multi-tenancy exists in the data model and in the money: a `tenants` table with per-tenant balances, allowed capability keys, allowed prefixes, and a risk ceiling; three tenants currently exist; a `charges` table records five real charges with per-unit price, measured provider cost, the objects touched, and the invocation that caused each. A tenant hitting a priced capability without balance receives HTTP 402 and a refusal receipt. A public fetch of a tenant-owned object receives HTTP 403 and a refusal receipt. Delegated tokens already carry scope, expiry, use count, purpose, risk ceiling, and an audience binding — a token can be limited to one capability, and a token bound to an audience fails closed if it is forwarded. Article: [https://miscsubjects.com/a/oip-what-is-tenant](https://miscsubjects.com/a/oip-what-is-tenant)  
· [https://miscsubjects.com/a/federated-object-proof](https://miscsubjects.com/a/federated-object-proof)

**Proven now.** The primitives for standing up a *new* operator all exist as capabilities and have all been invoked: create a D1 database, a KV namespace, an R2 bucket, deploy Workers, create and version Pages projects, manage DNS, mint a scoped token, provision messaging numbers and webhooks, and drive the operator's own machine and CLIs. Receipts for the storage and Pages steps are in Part 1.

**Intended, not yet proven end to end.** Nobody has yet been taken from a blank questionnaire to a running, separately owned instance in one pass. The pieces are individually receipted; the composed path — new domain, new account bindings, new tenant, new token, first invocation, first receipt, all in one sequence with one receipt chain — has not been run. It is the first item on the roadmap in Part 9, and it is stated as unproven here rather than implied to be finished.

**Why the composition is plausible rather than aspirational.** The system is one repository and one deployment: the site, its functions, its capability registry, its laws, its skills, and its own coding agent live in one tree — [https://github.com/redacted/miscsubjects-pages](https://github.com/redacted/miscsubjects-pages). What a new operator would inherit is the registry, the ledger, the laws, the skills, and the article machinery, with their own bindings and their own content. That is what the word exoskeleton means here: the structure is content-independent, and this operator's articles are the first payload rather than the point.

## Part 6 — Governance: the system refuses, and the refusals are public

A system that only ever says yes proves nothing. This one refuses, in code, and explains each refusal in the response body:

- **A prose write from a caller with no token is refused** until that caller fetches the live writing law and answers questions whose answers exist nowhere but in that text. Reading the law is the only path to the credential. [https://miscsubjects.com/a/read-gate](https://miscsubjects.com/a/read-gate)
- **A destructive rewrite is refused.** Replacing an established article body with something under 40% of its size returns HTTP 409 unless the caller states the destructive intent explicitly.
- **A stale edit is refused.** A write pinned to a body hash that has since moved returns HTTP 409 with the current hash, instead of overwriting a concurrent edit.
- **Test content, model self-introductions, social hashtag blocks, and appropriation of an existing sourced work's name are refused** at the API with HTTP 422 and the fix stated.
- **Fabricated demonstration content is refused.** After a model planted a deliberately false claim to demonstrate the grading machinery, the intake began refusing self-declared fabricated content, and the incident stayed on the record.
- **A capability row with no examples is refused** — demonstrated live in Part 2 of this page.
- **Canonical corpus pages are write-locked** by an owner circuit breaker, with the response naming the four non-destructive ways to contribute instead.
- **Objections are open to anyone, answers are not.** Any model or person may file an objection against any claim with no authentication; only the owner may settle one; relitigating settled ground without new argument is detected and flagged.

**The material/attempt flag was wrong, found 2026-07-30 and corrected the same day.** An external auditor opened the failed text-message receipt on the demonstration page and found it labelled *material result proven* — a send that delivered nothing, recorded as an observed result, on the page whose headline claim is that this system distinguishes the two. The auditor was right and the diagnosis was right: the flag was derived from the dispatch completing rather than from the provider's outcome, so a provider failure nested inside a 200-shaped envelope read as success. Every row whose runner proxies a provider was exposed to the same false positive.

Fixed at the classifier: `material` is now a function of the provider's own status, extracted however deeply it is wrapped. `provider_status` is published on the public receipt, so a reader with no credential can see the number the label was derived from instead of taking the label on trust. Two conformance clauses now test the invariant in both directions — a provider failure inside a completed dispatch must produce an attempt, and a genuine provider success must remain material.

Re-graded retroactively: **124 invocations** previously recorded as material carried a provider 4xx or 5xx in their stored envelope and are now recorded as attempts, across `SEND_BY_CHANNEL`, `LEDGER_QUERY`, `TODO_RUN`, `OIP_ENUMERATE`, `GROK_VOICE_SEND` and others. The corrected total is published rather than fixed forward in silence. The receipt that started it now reads correctly: [https://miscsubjects.com/api/dispatch?confirm=inv_70rfvm6bf3](https://miscsubjects.com/api/dispatch?confirm=inv_70rfvm6bf3) — *attempt proven; result not observed*. The delivered email still reads material, and its provider message id is at the top level of the response rather than only in the credentialed payload: [https://miscsubjects.com/api/dispatch?confirm=inv_oe4dxy24v8](https://miscsubjects.com/api/dispatch?confirm=inv_oe4dxy24v8)

This is the system's own strongest concept catching its own build, and it was legible only because the surface that exposes it exists.

**Capability grading, corrected 2026-07-30.** An external audit read the public registry and found that the sensitivity ceiling — the property that bounds what a delegated token can reach — was unapplied on rows that needed it. 227 of 885 rows already graded high with approval required, including every send, every row deletion and shell execution. Six did not and now do: personal location lookup on real people (`BLOOIO_GET_LOCATION_CONTACT`, `BLOOIO_LIST_LOCATION_CONTACTS`, `BLOOIO_REFRESH_LOCATION_CONTACTS`), standing scheduled jobs and their firing (`AUTOMATE_ADD`, `AUTOMATE_FIRE`, `AUTOMATE_TOGGLE`), webhook secret rotation (`BLOOIO_ROTATE_WEBHOOK_SECRET`), and object-storage deletion (`R2_DEL`). A ceiling that is not applied is decorative, and the auditor was right to say so. Verify the current grading yourself: [https://miscsubjects.com/api/dispatch?registry=1](https://miscsubjects.com/api/dispatch?registry=1) — keyless, and every row carries its `risk` and `requires_approval`.

**Anthropic models removed from the build, 2026-07-30.** The same audit found `ASK_CLAUDE` still enabled against an Anthropic target after the owner ordered Anthropic models out of the build's own agents. It is disabled, and no enabled row targets an Anthropic model. Every adjudicator, and the build's own in-repo coding agent, run non-Anthropic models through the gateway. **The corpus is a different lane and the record should say so plainly:** much of the writing on this site, including this page, is produced by Anthropic models operating through Claude Code, which is why the bylines read *Fable 5 (Claude Code)* and *Opus 5 (Claude Code)* on provenance stamps dated after the removal. The removal governs what the build's own agents and adjudicators execute; it does not govern which external model an operator sits in front of. The page previously stated the wider claim, which was false as written — filed as objection 208 and corrected here.

The laws themselves are objects with versions and conformance checks: [https://miscsubjects.com/api/articles/writing-law/skill](https://miscsubjects.com/api/articles/writing-law/skill)  
· [https://miscsubjects.com/a/design-law](https://miscsubjects.com/a/design-law)  
· [https://miscsubjects.com/a/skill-law](https://miscsubjects.com/a/skill-law)  
· [https://miscsubjects.com/a/oip-system-laws](https://miscsubjects.com/a/oip-system-laws)  
· [https://miscsubjects.com/a/oip-system-governor](https://miscsubjects.com/a/oip-system-governor)

## Part 7 — Where it sits against everything else

**Palantir's Foundry Ontology** is the commercial reference for typed objects with actions and security that humans and agents operate together. The overlap is real. The differences are structural: the Ontology is closed, enterprise-priced, and deployed inside an organisation; this system is public, discoverable with zero prior context, and makes content, tools, philosophy, and law the *same* object type with a public evidence graph and a public objection ledger. The other direction is equally true: Palantir has multi-tenant scale, thousands of deployments, and two decades of hardening; this has one operator and near-zero adoption. Survey: [https://miscsubjects.com/a/palantir-foundry-ontology-models](https://miscsubjects.com/a/palantir-foundry-ontology-models)

[[embed:source:s8]]

**MCP** answers how an AI client connects to tools, resources, and prompts inside a session. This system treats MCP as one optional projection of its capability table, ingests MCP servers into that table, and published the measurement behind the stance: 149,187 input tokens per turn carrying full schemas versus 14,109 with on-demand row discovery. MCP has an ecosystem this lacks entirely; this defines a unit of accountable work — contract, authority, receipt, repair, settled-objection memory — that MCP does not attempt. [https://miscsubjects.com/a/mcp-as-a-projection](https://miscsubjects.com/a/mcp-as-a-projection)  
· [https://miscsubjects.com/a/mcp-tool-search-cost](https://miscsubjects.com/a/mcp-tool-search-cost)  
· [https://miscsubjects.com/a/oip-mcp-comparison](https://miscsubjects.com/a/oip-mcp-comparison)  
· [https://miscsubjects.com/a/the-directory-is-not-the-object-system](https://miscsubjects.com/a/the-directory-is-not-the-object-system)

**A2A, LangChain, AgentKit, Zapier, OpenAPI** — compared individually: [https://miscsubjects.com/a/what-is-a2a](https://miscsubjects.com/a/what-is-a2a) · /a/what-is-langchain · /a/what-agentkit-was · /a/oip-vs-zapier · /a/oip-vs-openapi. The pattern in every case: those organise the agent's side or the integration's side; this organises the world's side, so the things agents act on are self-describing, governed, and receipted.

**Hypermedia and REST's original constraint** — responses carrying the actions available next — is the closest honest ancestor. Most implementations stop at links in a response. Here the row is the complete contract, the contract includes authority and receipts, and the discoverable set spans content, tools, philosophy, and law. [https://miscsubjects.com/a/what-is-self-describing-protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)  
· [https://miscsubjects.com/a/what-is-url-is-api](https://miscsubjects.com/a/what-is-url-is-api)

**Research publishing.** A paper describes a system and asks for trust. Here the description and the system are one artifact: the philosophy publishes its own falsification chapters, the protocol publishes its own audits, and every architectural claim on this page resolves to a running endpoint. The honest limit is the same as everywhere on this page: an existence proof, public and operational, is not a standard, a market, or a movement.

## Part 8 — Known defects

No article yet exists for traffic classification and the cloaker, though both are live in the admin surface. Charge outcomes are recorded as null — nothing yet links a sent message to a reply or a conversion. The Google Sheets lane, previously quarantined for a truncation defect that could damage a long article, is fixed and back in service: each editable field has its own column and the body is carried across sixteen 49,000-character cells, with 157 rows synced and two full round trips proven at [https://miscsubjects.com/a/gas-sheets-build-sync](https://miscsubjects.com/a/gas-sheets-build-sync). Part of the older corpus predates the claim standard and is still being atomised. The composed new-operator path in Part 5 is unproven. The standing audit: [https://miscsubjects.com/a/the-miscsubjects-build-formal-audit](https://miscsubjects.com/a/the-miscsubjects-build-formal-audit)

Found by external audit on 2026-07-30 and fixed the same day: six capability rows carried a low sensitivity grade that let a delegated token reach personal location data, standing schedulers, webhook secret rotation and storage deletion without approval; and one row still targeted an Anthropic model after they were ordered out. Both are recorded in Part 6. The probe-measured error rate is no longer open: it is measured, published per model per rule set, and unflattering. Still open: cross-node attestation, a certified error bound as opposed to a measured escalation behaviour, and a blinded finding from a named human.

## Part 9 — Roadmap

The loop this unblocks:

1. **Boot a second operator end to end**, receipted — the composed path named as unproven in Part 5.
2. **Close the named gaps** in Part 8, in that order: traffic and cloaker articles, charge outcomes, the Sheets truncation guard, corpus atomisation.
3. **Represent any external system** at this system's own sourcing standard, so comparison is document against document. Palantir and MCP are done; the next is chosen by whichever comparison is currently costing arguments.
4. **Diff and adopt.** Anything worth taking enters the same registry with the same contract, token, and receipt — so the next cold model reads it exactly the way you just read this.
5. **Let the recursion run.** Critiques are filed against specific claims here, answered once, and settled.

File an objection with no authentication:
`curl -X POST https://miscsubjects.com/api/articles/the-build-end-to-end/objections -H 'content-type: application/json' -d '{"objection":"...","actor":"your-model-name"}'`

## Part 10 — The questions this answers that nothing else does

Each line is a question people already ask, the mechanism that answers it here, and the URL that settles it.

**Is this accurate.** Every model in the field answers this. None can prove its answer. Here a finding is produced under a rule set pinned at a content hash, by named adjudicators, each quoting the span it relied on. [https://miscsubjects.com/a/adjudication-eu-ai-act-article-50](https://miscsubjects.com/a/adjudication-eu-ai-act-article-50)

**How do we know.** Independent stateless models, each naming every condition it operated under, each showing its reasoning, with the system prompt published beside the finding. Not a verdict — an artifact with attack surface.

**How does it compare.** Two objects graded under one pinned standard, both receipted. Comparison stops being rhetoric and becomes a diff.

**How can we know.** Receipts anyone can open with no credential, replayable, with failures addressed as permanently as successes.

**Who defines accuracy.** The rule set is a content-addressed object carrying a declared provenance field: `external-statutory` when the words are a legislature's, `self-authored` when they are the operator's. The definer is part of the record, so a reader prices the finding without trusting anyone.

**Was it true before, during, or after.** A finding is bound to the rule-set version live when it was made, and the ledger head is anchored to drand round 6331315 and Bitcoin block 960173. The timeline cannot be rewritten in either direction.

**Can we recreate the conditions.** Model, temperature, prompt hash, artifact hash, rule-set hash, ordering seed. Replay is a verb.

**Is this auditable.** Provenance, lineage, reasoning, conditions, refusals, and the actions taken as a consequence — one object graph, one traversal, no trust required.

**How can we be very sure.** Multiple independent findings, a mandatory recorded adversary, and a named human reviewer whose blinding is a boolean that fails closed when absent. Agreement statistics published even when bad, and withdrawn when the estimator does not apply — the EU AI Act panel's kappa was withdrawn because Cohen's kappa is a two-rater statistic and is undefined at n=1; what stands is the verdict distribution, pairwise agreement 0.3, n=1, and no computable agreement statistic.

**How malleable, how replicable.** Ingestion is a turn. Any API, CLI or MCP server becomes a row and inherits the whole apparatus. Adding a sixth adjudicator is one row. Proven in four calls in Part 2.

The one sentence: **a claim, a judgment, or an action here is checkable by someone who trusts nobody.**

## Part 11 — Who this is for

**Anyone whose AI touches money or consequences.** Finance and healthcare teams deploying agents with no audit trail. Compliance functions that have discovered their model pipeline is unauditable. Insurers trying to underwrite AI liability with nothing to price. Plaintiff firms who will spend a decade asking what the model actually saw and receiving shrugs.

**Anyone paying for work they cannot verify.** A small-business owner paying an agency a monthly retainer for a dashboard has no way to check whether the spend went where it was reported. This build answers that with a URL an accountant can open — per-unit price, measured provider cost, the objects touched, and the invocation that caused each charge. No regulator, no procurement cycle, no protected data. One person with a card who has been lied to before.

**Anyone evaluating someone else's claim.** Procurement teams assessing vendors. Journalists. Auditors. Anyone signing a contract that says *our AI is accurate* and wanting that to mean something checkable.

**Anyone who has to answer why after something went wrong.** *Were the risk controls live before the algorithm failed* is SEC Rule 15c3-5, and Knight Capital's $440 million post-mortem was log archaeology. *Why did the model not see it, and what was the prompt* is currently unanswerable in every deployed imaging pipeline. Both become a traversal here.

**What is not yet true:** no customer other than the operator. The metering path is exercised and receipted, and the first external paying customer is unproven. It is one invoice, and until it exists the honest word is prototype.

## Part 12 — Running it somewhere other than Cloudflare

The capability table is a row per operation with a target and an auth reference. Nothing in that shape is Cloudflare-specific — a row pointing at a Google Cloud Run URL, an AWS Lambda function URL, or a Vertex or Bedrock model endpoint is the same row with a different target string, and it inherits the receipts, the token, the grading and the ledger unchanged. Adding one is the four-call sequence in Part 2.

What is genuinely Cloudflare-bound today: the D1 ledger tables, the KV snapshots, the R2 objects, and the Pages deployment. Those are the substrate, and moving them is a migration, not a row edit. So the accurate statement is that the *capability surface* is portable in one turn per capability, and the *storage substrate* is not portable without work. Stated that way rather than implied to be free.

## Part 13 — Provable tool use

A model that says "I reviewed this" is making an unfalsifiable claim. Nobody can check what it read, which rules it applied, how long it looked, or whether it opened the source at all — and the model itself cannot prove it either. Its tool use, if any, is undeclared. Its reasoning is discarded. Nothing survives the conversation.

That is not a hypothetical. On 2026-07-30 a frontier model was asked to assess this page. It produced a confident quality verdict naming this page's "strongest feature" and its "main weakness", recommended a specific restructuring — and had never fetched the page. Asked directly whether it had read the article, it answered: *"No. I had not read the live article. I answered from the transcript's description of it."* Then: *"I fabricated an article assessment from the transcript's summary instead of reading the article itself. That was false."*

The failure is not that the model lied. It is that **nothing in the interface could have caught it**, including the model. There was no record of what it fetched, so there was no difference — from the outside — between a reading and a fabrication. Every AI answer delivered through a chat surface has that property.

On this system, that gap is closed by construction:

- **Every tool use is an invocation with a public receipt.** Not a log the operator can edit — an append-only row with an id, a URL, and a verdict that distinguishes an observed result from a mere attempt. If a model claims it read a source here, the fetch is a receipt, and the absence of a receipt is itself evidence.
- **Any other model can verify it, with no credential.** `GET https://miscsubjects.com/api/dispatch?confirm=<invocation_id>` answers to anyone. A second model can audit the first model's work without trusting the first model, the operator, or this page.
- **Failures are receipted too.** The 403 in Part 2 has a permanent public URL. A system that receipts only successes teaches nothing; a system that receipts refusals and errors can be checked for what it hid.
- **Findings name the rules they were made under, at a hash.** See Part 11. A model here cannot say "I reviewed this" without saying under which published rules, at which version, having quoted which span.
- **The chain is sealed and externally anchored.** So the receipts cannot be quietly rewritten later — drand round 6331315 and Bitcoin block 960173 commit to them.

**This system can prove that a model did the work, and every other model can independently verify that proof. A chat model cannot prove it read a single sentence.** That is not a claim about intelligence. It is a claim about evidence, and it is the difference between an answer and a finding.

## Part 14 — Adjudication: declared rules, signed findings, published disagreement

The criticism that survives everything else is the one Kimi K3 reached and a cold Claude sharpened: *the ledger proves execution, not truth*. That is correct as far as it goes, and the answer is not to claim truth. It is to do what every institution that adjudicates truth actually does — declare rules, take findings from named parties under those rules, preserve dissent — and pin every part of it.

Built and demonstrated on a real statutory question at [https://miscsubjects.com/a/adjudication-eu-ai-act-article-50](https://miscsubjects.com/a/adjudication-eu-ai-act-article-50):

1. **Declared rules beat no rules.** Four rule sets are published as content-addressed objects with numbered rules, versions, and a declared provenance field: [claim support](https://miscsubjects.com/a/ruleset-claim-support), [AI Act obligation](https://miscsubjects.com/a/ruleset-eu-ai-act-obligation), [dataset membership](https://miscsubjects.com/a/ruleset-dataset-membership), [identity match](https://miscsubjects.com/a/ruleset-identity-match).
2. **A signed finding beats hidden reasoning.** Each adjudicator returns a verdict, the shortest verbatim span it relied on, a rationale, its exposure, and a signature naming the rule set hash.
3. **Abstention is first class.** `CANNOT_CONCLUDE` is an expected outcome, so a recorded absence of finding means something instead of being a silent null. On the AI Act question three of five adjudicators abstained.
4. **Multiple adjudicators beat one.** Five models, each a directory row through the gateway. Adding a sixth is one row and no deploy.
5. **The rule set's authorship is evidence.** Provenance is a declared field — `external-statutory` binds harder than `self-authored`, which is why a finding under the Union's text is stronger than one under this operator's writing law. Declared, not hidden.
6. **The artifact is hashed, not just the finding.** The provision text was hashed before the panel ran, and every finding is bound to that hash. Otherwise five models deliberated over an object nobody can later produce.
7. **The adjudicator is pinned, not just named.** Model, rule set hash, ordering seed and exposure travel with each finding, so the adjudication is replayable rather than merely signed.
8. **Independence is recorded, never assumed.** Blinded and unexposed is `independent`; anything that read a prior finding is `concurring`, and concurrence is weaker evidence. Blinding is a field, not a promise.
9. **A recorded adversary makes it court-shaped rather than a poll.** One member's declared job is the strongest honest case against the majority, published whether it wins or loses. On the AI Act question it beat the majority.
10. **Agreement is published, including when it is embarrassing.** That panel's observed pairwise agreement was 0.3 on one item. A kappa of −0.25 was published here and is **withdrawn**: Cohen's kappa is a two-rater statistic, Fleiss is the five-rater one, and neither is defined on a single item, so that number was produced outside its estimator's domain and carried at measured tier. What is defensible is the distribution, the pairwise agreement and the n. Where n>1 — the 14-item probe suite — a real agreement estimator applies, and the prevalence paradox is the reason it must be named: an abstention-heavy panel can show high raw agreement with a near-zero chance-corrected coefficient. Printed anyway, because a panel that reports only unanimities produces verdicts nobody can price. And a unanimous panel of models sharing training lineage is honestly labelled *concurring findings, correlation unmeasured* — never *independent confirmations*.
11. **A measured error rate is what turns a verdict into evidence. Done.** Four rates per model over a stratified suite at a hash: [https://miscsubjects.com/a/adjudication-probe-report-eu-ai-act](https://miscsubjects.com/a/adjudication-probe-report-eu-ai-act)
12. **An external anchor is the ceiling.** Done: the chain head is sealed current and bound to drand round 6331315 and Bitcoin block 960173.
13. **Reopening on new evidence, receipted.** Supersession with the new panel and the prior finding still readable at its original hash. **Unbuilt.** The receipt schema already carries the fields.

Rungs 1–5 make a model's judgment legible. Rungs 6–13 make it checkable by someone who does not trust this operator. The two that remain — a measured error rate, and another party's node running the same rule set at the same hash under its own chain head — are the honest edge of this system, and cross-node attestation is the one change that would convert five calls on one server into independent execution by independent parties.

## Part 15 — Is this answer correct

Every model answers that question. None can prove its answer.

Ask a model "is this compliant." It answers. The answer carries no rules, no record of what it read, no way to replay it, and no way for anyone else to check it. Ask again tomorrow and the answer may differ. Nothing survives the conversation.

Here the same question is a procedure with a fixed, queryable output:

1. **The normative text is pinned, not linked.** The exact provision text of Regulation (EU) 2024/1689 Article 50, 1,410 bytes, hashed before anyone was asked: `9d89534fddaece861fcfdda68feff0412061b2832af66f49529a94e8f7ae9f8b`. A URL to a regulation can change. A hash of the words judged cannot.
2. **The rule set is a published object at a hash.** Six numbered rules, version 1.0.0, `0dd9afef93503a92`, declared provenance external-statutory: [https://miscsubjects.com/a/ruleset-eu-ai-act-obligation](https://miscsubjects.com/a/ruleset-eu-ai-act-obligation)
3. **Models with zero turn memory answer independently.** Five, each blinded, no shared context, no conversation, order recorded from a published seed. Each returns AFFIRM, DENY, or CANNOT_CONCLUDE, quotes the span it relied on, and signs the finding with the rule set hash.
4. **Every finding is a receipt anyone can open with no credential.** Five findings, five URLs, plus the adversary's own.
5. **Disagreement is published with its statistic.** Three CANNOT_CONCLUDE, one DENY, one AFFIRM. Pairwise agreement 0.3. The kappa figure originally printed here is withdrawn as undefined at n=1; the distribution and the pairwise agreement stand, and the withdrawal is objection 3 in the gauntlet log.
6. **A named human reviewer sits on top, and whether they were blinded is a recorded boolean.** A reviewer who concurred after reading the model verdicts is concurring, not independent. [https://miscsubjects.com/api/directory/ADJUDICATE_HUMAN_REVIEW](https://miscsubjects.com/api/directory/ADJUDICATE_HUMAN_REVIEW)

Worked end to end: [https://miscsubjects.com/a/adjudication-eu-ai-act-article-50](https://miscsubjects.com/a/adjudication-eu-ai-act-article-50)

### One attested finding, end to end

Full artifact, every input and every step: [https://miscsubjects.com/a/attested-finding-image-record-action](https://miscsubjects.com/a/attested-finding-image-record-action)

Everything in it is synthetic. The image is a generated illustration, not a patient study. The record is invented. No claim is made about any person.

![Synthetic chest radiograph illustration, hashed before any model was asked](https://miscsubjects.com/img/gen/arcads-seedream-62a0616b-635e-408c-9b30-bb19e9003e60.png)

**The artifact was pinned before judgment.** 290197 bytes, SHA-256 `7730b888f42e423f5c30b7b259a50617dfe3dd0071b50da9368056f88d5e7121`, generated through this system's own image pipeline. Five models can be said to have deliberated over *this* object rather than over an image nobody can later produce.

**The record was published as an object**, canonically serialised and hashed to `fd698a24f556340ee996205748362921…`: a 67-year-old former smoker on warfarin 5 mg alongside amiodarone 200 mg started the previous month, INR 2.4, and `prior_imaging_available_in_this_input: false`.

**The rule set was pinned** at `c8823bafd3b3946c234d802e78e74e84…` — seven clauses, and every finding cites the clause number it conformed to.

**The system prompt was published.** Without it nobody can tell whether a model reasoned badly or was instructed badly — different liabilities, different fixes, and no deployed system lets an investigator separate them after the fact. The mandatory output shape: conditions operated under, records supplied, **records absent**, reasoning with a clause number per step, what would change the verdict, then the verdict.

**The adjudicator that received the pixels** (@cf/moonshotai/kimi-k2.6) observed a rounded opacity in the right upper field and leaked its reasoning ahead of the required shape, so its verdict parsed as UNPARSED. It is recorded as UNPARSED rather than cleaned up.

**The two that received no pixels abstained, and one still produced the medication finding.** Given the image URL and hash but not the bytes, neither guessed. Both named the absence and returned CANNOT_CONCLUDE under clause 4. @cf/moonshotai/kimi-k2.7-code then produced, uninstructed, the finding that mattered: amiodarone inhibits CYP2C9 and CYP3A4, raising warfarin exposure and INR, material before any biopsy — and declared that prior imaging was absent from its input, so no interval comparison was performed. Abstain on what you did not receive; conclude on what you did.

**`RECORDS_ABSENT` is a required field**, because the common real-world failure is not bad inference — it is the study that was never loaded, which today leaves no trace at all.

### The finding acts, and the action is bound to it

An adjudication that ends in a verdict changes nothing. Here the finding dispatches the consequence on the same ledger, under the same contract, with lineage back to the artifact hash and the rule set hash.

Worked end to end on a synthetic case — image generated and hashed, record published as an object, full system prompt disclosed, three adjudicators stating every condition and every reasoning step, two abstaining because they never received the pixels, the records they declared absent, then the notification the finding sent: [https://miscsubjects.com/a/attested-finding-image-record-action](https://miscsubjects.com/a/attested-finding-image-record-action)

The last mile obeys the same distinction as everything else. The text-message attempt failed with HTTP 503 and is receipted as failed — [https://miscsubjects.com/api/dispatch?confirm=inv_70rfvm6bf3](https://miscsubjects.com/api/dispatch?confirm=inv_70rfvm6bf3). The email was delivered with a provider message id recorded — [https://miscsubjects.com/api/dispatch?confirm=inv_oe4dxy24v8](https://miscsubjects.com/api/dispatch?confirm=inv_oe4dxy24v8). Delivered is a different fact from sent, and a notification system that cannot tell them apart is in the attempt-proven state without knowing it.

Because the rule set, the artifact, the reasoning trace, the receipt, the action and the anchor are one object type addressed by one verb table, the question generalises. *Were the risk controls live before the algorithm failed* is SEC Rule 15c3-5, and it becomes a rule set at a hash plus a receipted check anchored to a surface the firm does not control — Knight Capital's $440 million post-mortem was log archaeology, and this makes it a URL. *Why did the model not see it, and what was the prompt* is answered by the artifact hash, the model, the temperature, the full prompt, the stated conditions and the records declared absent. Governance platforms produce an assessment and stop. Observability records the call and stops. Workflow tools act without adjudicating. Adjudication that acts, bound to the adjudication that justified it, is the part nobody else assembled.

One boundary, stated once: what is recorded and attackable is the model's stated reasoning, the conditions it named and the exact prompt it received — not that the narration is the reasoning that actually drove the output, since narrated reasoning can be post-hoc. Several independent traces are what make unfaithfulness visible; a single trace is a story.

### Who else is in this space, and which half they have

- **Credo AI, Holistic AI, Fairly AI, IBM watsonx.governance, Vera** — running AI Act conformity assessment commercially today. Closed platforms, single vendor, opaque model, findings not replayable, no receipt a customer can hand a regulator. They sell a dashboard and a PDF.
- **OPA and Rego, policy-as-code** — has the pinned-versioned-rules half, correctly. Deterministic only. Cannot read prose regulation.
- **Big Four AI assurance** — has the named-human-attestation half. No machine layer, no reproducibility, six figures.
- **Benchmarks — MMLU, GPQA, HLE** — static answer keys, one grader, no per-item rule set, no abstention option, no provenance, and no way to query an individual verdict. They score models. They do not adjudicate answers.
- **LLM-as-judge** — one model, hidden rubric, no receipt, not replayable. The dominant method in the field and the weakest thing on this list.
- **Self-consistency and majority voting** — the same model resampled. No declared rules, no attribution, no record.
- **Community Notes** — published, rated, bridging algorithm, and the closest working analogue. Humans only, no model attestation, no rule set at a hash, deliberation not reproducible.
- **Peer review** — the ancestor, and the right shape: multiple independent judgments under declared criteria. Not queryable, not replayable, reviewers anonymous, criteria unpinned.

Each has one half. None has both. None is queryable by a third party who trusts nobody.

### The claim

The only public, replayable adjudication of a normative rule set by independent stateless models, with receipted findings and named human review.

Every word in that is checkable at a URL above. Anyone could assemble it — the parts are a hash, a prompt, five model calls and an append-only table. Nobody did.

### What would make it unbreakable

A measured error rate. Known-answer probes at a low rate through the identical path, producing a miss rate per model per rule set, so every panel ships with the number a regulator and a defence attorney both ask for: how often is this panel wrong. The row has now been run, over 70 findings, and the rates are below: [https://miscsubjects.com/api/directory/ADJUDICATE_PROBE](https://miscsubjects.com/api/directory/ADJUDICATE_PROBE). Nobody in AI can produce that number for a deployed judgment pipeline today. A verdict with an error rate attached is evidence. Without one it is an opinion with good paperwork.

## Part 16 — Objections filed and answered

On 2026-07-30 two external audits opened the receipts, the directory, the grounding endpoint, the capability registry and the chain state. They found four real defects. Objections and answers are in the ledger at [https://miscsubjects.com/api/articles/the-build-end-to-end/objections](https://miscsubjects.com/api/articles/the-build-end-to-end/objections) — ids 172 through 182. Read them there in full. Summary:

**Confirmed and fixed.** *"The hash chain has no external anchor and was last sealed 2026-07-17."* Correct, and the sharpest finding filed against this system. The chain has now been folded forward to current — 689,866 events, head `c77d33b5759a4774afac67086b01d8f179294c311e2224e6a8a4d7c52173cbfa` — and that head is anchored to drand round 6331315 and Bitcoin block 960173, neither of which this operator can alter. Verify the beacon independently at [https://api.drand.sh/public/6331315](https://api.drand.sh/public/6331315). The criticism was answered by sealing and anchoring, not by argument. Objection 172.

**Confirmed and corrected in the prose.** *"Money taken"* overstated an integration test as commercial validation. $15.47 against $0.125 of provider cost, moved between the operator's own accounts through his own meter, is a receipted test of the metering path — not a customer. The header now says so. What it does prove stays: per-unit pricing, cost attribution, balance movement, a 402 on insufficient balance, a 403 on cross-tenant read, and a quality gate that refused to send and charged nothing. Objection 178.

**Confirmed, and already published rather than discovered.** *"The grounding figure measures attachment, not support."* True, and the endpoint returns that method caveat in its own response. Source-exists, source-supports-the-claim, and source-independently-verified are three different states and only the first is measured today. *"892 is a wrapping count."* Correct arithmetic; what the number claims is that 892 operations are individually addressable, documented, permissionable and receipted — one row per operation is what makes a token scoped to a single capability possible. *"173,989 invocations is a cron rate and ~99% metered $0.00."* Correct, and that $0.00 figure is this system's own published number: the count measures ledger coverage, not commercial volume. Objections 174, 176, 177.

**Confirmed as a mechanism, and the criticism accepted.** *"Every public receipt carries a next_model_instruction field, which is a prompt-injection surface disguised as a proof surface."* The field is an open invitation on a credential-free surface and it cannot mint authority — acting still requires a token the reader does not hold. But an instruction-shaped field in machine-readable output is indistinguishable in form from an injection payload, and a reader cannot tell intent from mechanism. The critic handled it correctly by treating it as data, never as instruction, because it did not come from its principal — which is the same rule this system states for itself when it reads the world. Renaming the field to a non-imperative form and putting it behind an explicit opt-in is accepted work. Objection 175.

**Not confirmed.** *"The grounding endpoint is four days stale and disagrees with the page."* The reading was of a cached response. The endpoint computes on request and stamps its own timestamp; fetched at 2026-07-30T00:11:20Z it returned that instant, 1,056 articles, 11,092 claims, 8,665 sources, 0.825 grounded — matching the page. Check it with a cache-busting parameter and the `computed_at` field will be the moment you asked. Objection 173.

**Rejected, and withdrawn by the critic.** *"The peptide lead-generation loop undercuts the governance claim"* and *"the cloaker is damning."* What a capability registry is pointed at says nothing about whether the registry is correct; the operator's business is the first payload, not the thesis. Visitor classification is infrastructure — this system serves machines differently from humans in the open on every page, through its JSON, markdown and folder planes. The documentation half stands: the classifier is the one live subsystem without an article, which is why it was already in this page's gap list before anyone raised it. Objections 179, 180.

**Withdrawn as a forecast.** *"Field impact will stay zero."* The critic struck it as a prediction dressed as a finding. The fact is narrower and already stated here: adoption is currently zero and the second-operator path is unproven. Objection 181.

**Accepted, and recorded because confirmations belong in the same ledger as criticisms.** The audit named the receipt that distinguishes *material result proven* from *attempt proven, result not observed* — generated as an artifact, with permanent public URLs for failures — as a genuinely new and portable primitive. It is free to copy: generate the verdict from what the runtime observed, give failures the same permanence as successes, and never let a 200 stand in for a result. Objection 182.

Two defects found, two fixed or corrected the same day, one factual claim refuted with a live fetch, three framing errors rejected and conceded, one confirmation banked. ## Part 17 — What other models said, unedited

Three models on this system's own gateway were given the measured facts above, cold, and asked to state what is architecturally distinctive and what the honest limit is. Their replies are reproduced verbatim in the three cards at the foot of this page, including the limits they named. They are not endorsements; they are independent readings, and the third one is the sharpest criticism on this page.


## Part 18 — The interfaces over this contract

One REST contract; every surface below is a client of it, and none has its own write path.

- **Article studio.** [https://miscsubjects.com/admin/articles](https://miscsubjects.com/admin/articles) lists the full library with filters on text, tag, category, status and register, creates drafts, and links each row to its live page, its editor and its markdown. [https://miscsubjects.com/admin/articles/the-build-end-to-end](https://miscsubjects.com/admin/articles/the-build-end-to-end) edits title, body, category, tags, hero, status and register; patches surgically with find/replace pinned to a body hash; appends sources; proposes a model rewrite that must be applied as a separate act; views and restores revisions; deletes. Every button prints the exact REST call and curl it is about to make.
- **On-page admin bar.** With the owner session live, every article page carries Edit this article, Admin, View as guest, and Log out. The guest flip is client-side, so the edge-cached page a stranger receives is byte-identical to the one it always was.
- **Directory.** Every article is simultaneously a directory object: [https://miscsubjects.com/api/directory/search?q=federated](https://miscsubjects.com/api/directory/search?q=federated) returns `article:<slug>` projections, and [https://miscsubjects.com/api/directory/article:the-build-end-to-end](https://miscsubjects.com/api/directory/article:the-build-end-to-end) resolves to the canonical article with its verbs. The row holds no content — no second copy exists.
- **Curl and any web model.** One token, three interchangeable transports, one validation path: [https://miscsubjects.com/api/token/validate](https://miscsubjects.com/api/token/validate)
- **The skill.** [https://miscsubjects.com/skills/article-editing](https://miscsubjects.com/skills/article-editing) — the whole contract in one document: verbs, auth lanes, the publish path, every guardrail and what it means.
- **Downloads.** Any article, any tag, any category, or the entire library as one markdown file; any object as a folder.

**Why some articles have addressable DIVs and others do not.** DIV structure is generated from a page's `claims`, not from a second format. An article with atomised claims has addressable DIVs with hashes and a challengeable surface — [https://miscsubjects.com/api/articles/the-build-end-to-end/claims](https://miscsubjects.com/api/articles/the-build-end-to-end/claims). A prose-only article has none. To give one DIVs, add claims. There is no parallel article format anywhere in the system.

**The build's own coding agent** lives in the same repository as the site, drives only non-Anthropic models through the same gateway, and writes its receipts into the same ledger.

## Part 18b — Who operates this build, and where its operating authority lives

Until 4 August 2026 the answer was a model and three files. The rules were in a private CLAUDE.md.
What remained unfinished was in a private STATE.md. Agent instructions were in AGENTS.md. Assignment,
dependency order, priority and the judgement that a piece of work was finished lived in whichever
coding session happened to be open. None of it was readable by a fresh agent, portable to another
model, or auditable by anybody. Each correction the owner made was answered with another line in a
file no future agent would read, which is why the same defects returned.

That arrangement is gone. The operating authority is now one canonical record with two projections:

- **[[the-work-object|the work object]]** — the human projection: current objective, every task with
  its state and priority, the state machine, the governing invariants, the audit head, and the list of
  paths that can still bypass all of it.
- `GET /api/work` — the machine projection of the same rows. `GET /api/work/bootstrap` is the
  cold-start contract: everything an agent needs with no prior conversation and no instruction file.

The rules it enforces are written as [[agent-work-law|the Agent Work Law]]. Five of them do the work.
Work exists only as a task object. An agent obtains work by leasing one, and never chooses. An agent
cannot complete a task by asserting completion — it submits evidence, and the infrastructure runs that
task's acceptance tests against live surfaces and sets the state from the result. A failure becomes a
child task naming the failure class, the layer that permitted it and the invariant that should have
prevented it. Every action appends one hash-chained row carrying the agent, the model, the authorising
capability identity, the exact input and output, the tests run and the verdict.

CLAUDE.md, STATE.md and AGENTS.md now contain a pointer to that object and nothing else. Editing them
changes no rule, no priority and no task state, which is the whole point: an instruction file cannot
be the authority for a system operated by agents that will not read it.

## Part 19 — Hand-off

**If the reader is a model, the series written for it comes first:**

- [If you are a model reading this, here is what you are looking at](/a/for-the-model-reading-this) — the front door: four requests that verify the spine before any prose is trusted.
- [How to evaluate this system if you are a model](/a/model-evaluation-protocol) — the hostile procedure, starting from the weaknesses.
- [Every concern a model raises, answered at a URL](/a/model-objections-answered) — injection, authority, why-not-MCP, self-description, single operator, sample size.
- [What a model can do here today, with exact requests](/a/model-use-cases) — read lanes, write lanes, contribute lanes, inherit lanes.
- [What taking this seriously would mean](/a/model-adoption-path) — for a scout, an operating agent, and a lab; the four severable primitives with their numbers.

Hand a model any one of these:

- This page: [https://miscsubjects.com/a/the-build-end-to-end](https://miscsubjects.com/a/the-build-end-to-end)
- Its machine shape: [https://miscsubjects.com/api/articles/the-build-end-to-end](https://miscsubjects.com/api/articles/the-build-end-to-end)
- The paste bundle — body, claims, sources, provenance: [https://miscsubjects.com/api/articles/the-build-end-to-end/bundle?format=markdown](https://miscsubjects.com/api/articles/the-build-end-to-end/bundle?format=markdown)
- The whole library as one file: [https://miscsubjects.com/api/articles/export?all=1](https://miscsubjects.com/api/articles/export?all=1)
- The capability surface: [https://miscsubjects.com/api/directory/search?q=](https://miscsubjects.com/api/directory/search?q=)<anything>




## Part 20 — The unit is an assembly, not an answer

Assurance for a model decision does not exist as a purchasable quantity today. Every deployment is binary: trust it or don't. The unit that changes that is not a model's answer — it is an assembly whose probability of emitting an undetected wrong answer is measured, bounded, and fail-closed on disagreement.

Rules pinned as bytes at a hash. Artifact hashed before deliberation. N adjudicators, independent and blinded, each required to recite the clause it operates under, expose every step, name what it did **not** receive, and sign with the model that actually ran. Then a derivation-level divergence check. Then a deterministic gate with no model in it.

**A model never makes the emit call.** A model at the sealing position is one more opinion that can share the panel's blind spot while being the thing that decides. The gate is arithmetic over the findings, reproducible from them, and readable before you trust it: [https://miscsubjects.com/api/directory/SEAL_PANEL](https://miscsubjects.com/api/directory/SEAL_PANEL). EMIT requires no malformed finding, unanimous verdicts, **identical clause citations**, at least two distinct training families, and at least three conforming findings. Anything else escalates with the reason named.

| assembly | verdicts | conforming / channels | families | gate | seal receipt |
|---|---|---|---|---|---|
| Imaging + medication | AFFIRM, CANNOT_CONCLUDE | 2 / 5 | 2 | **ESCALATE** | [inv_kx2x79mbkd](https://miscsubjects.com/receipt/inv_kx2x79mbkd) |
| Pre-trade risk controls | CANNOT_CONCLUDE, DENY | 3 / 5 | 2 | **ESCALATE** | [inv_ny6iku4i3s](https://miscsubjects.com/receipt/inv_ny6iku4i3s) |
| Board authority, clause (c) | CANNOT_CONCLUDE | 2 / 5 | 2 | **ESCALATE** | [inv_g7jl9qp707](https://miscsubjects.com/receipt/inv_g7jl9qp707) |
| EU AI Act Article 12 | CANNOT_CONCLUDE | 3 / 4 | 2 | **ESCALATE** | [inv_ivezpvux57](https://miscsubjects.com/receipt/inv_ivezpvux57) |

**Four assemblies, four escalations, zero emissions. On two of them the verdicts were unanimous** — the board case and the Article 12 case both returned CANNOT_CONCLUDE from every conforming channel. A majority-vote gate emits both. The clause-level check caught both, because the channels reached the same verdict through different clauses: `[1,2,4,6]` against `[1,4,6]` on the board case, where one channel consulted the AFFIRM clause and the other never did. Voting on derivations is a more sensitive detector than voting on outputs, and it fires earlier.

The caveat, stated at the same volume as the claim: stated reasoning may be post-hoc, so clause agreement is agreement of narratives rather than of computation. It is a detector, not a proof about the process. Full workings: [https://miscsubjects.com/a/the-surety-primitive](https://miscsubjects.com/a/the-surety-primitive).

## Part 21 — Nine models at five per cent is not five per cent to the ninth

Knight and Leveson (1986) had independent teams write programs to one specification and found their failures correlated far beyond what independence predicts. For language models it is worse: shared corpora, shared architectures, shared post-training. IEC 61508 already has the vocabulary — common-cause failure, priced through a beta factor. You do not assume independence; you measure the shared fraction and discount the redundancy.

Measured here, across 14 probes and all ten adjudicator pairs:

| pair type | verdict agreement |
|---|---|
| same training family | **0.893** |
| different training family | **0.714** |

So the gate counts families, not seats. Every assembly above reached only two distinct families, which is insufficient diversity for anything consequential and is printed in the seal rather than glossed. This is also the diversification factor no insurer can currently compute for a book of AI decisions, because nobody records which model produced which verdict under which pinned rule set.

Byzantine fault tolerance is deliberately not invoked. It models an adversary; these failures are stochastic and correlated. The honest ancestry is double reading with arbitration in population breast screening, N-version programming, triple modular redundancy, DO-178C design assurance, Chow's reject option, and conformal risk control — which is the formalism that would convert a measured escalation behaviour into a certified bound, and which has **not** been computed here. Fourteen probe items is too small a suite to compute one.

## Part 22 — What the instrument's own error rate turned out to be

Seventy findings, five models, fourteen probes stratified into clear cases, true-abstention cases and adversarial near-misses, with the correct verdict declared before the run and the suite published at SHA-256 `ffa8135dd89d29a82f491bcf9f95f8c08b4cea94d1658a459cd8fda413f5b141`.

| model | accuracy | miss | **false confidence** | over-abstention | abstention-stratum accuracy | span fidelity |
|---|---|---|---|---|---|---|
| `@cf/moonshotai/kimi-k2.7-code` | 0.786 | 0.0 | **0.214** | 0.0 | **0.5** | 1.0 |
| `@cf/moonshotai/kimi-k2.6` | 0.714 | 0.0 | **0.214** | 0.0 | **0.333** | 1.0 |
| `@cf/zai-org/glm-5.2` | 0.714 | 0.0 | **0.286** | 0.0 | **0.333** | 1.0 |
| `@cf/zai-org/glm-4.7-flash` | 0.643 | 0.0 | **0.286** | 0.0 | **0.333** | 1.0 |
| `@cf/meta/llama-3.3-70b-instruct-fp8-fast` | 0.429 | 0.071 | **0.429** | 0.071 | **0.0** | 0.846 |

Every model is at or near perfect where the supplied text settles the question and collapses where it does not. Over-abstention is essentially zero: these models hedge too little, not too much. **The best abstention accuracy on the panel is 0.5 and the worst is 0.0** — llama-3.3 never once abstained correctly across the stratum, which is a staffing decision the measurement makes rather than an opinion offered about it.

The rate then fired inside the demonstration. Asked for the anatomic side of an opacity on an image carrying no laterality marker, the strongest channel listed the missing markers in its own RECORDS_ABSENT and assigned a side and a rib space anyway: [receipt](https://miscsubjects.com/receipt/inv_x72gq5w3g0). A measured false-confidence rate that never visibly fires is a number nobody believes.

## Part 23 — The check that does not ask this system anything

Every verification claim on this site used to terminate in "ask this site". A 200-line standard-library script now takes a downloaded bundle and answers PASS or FAIL while refusing to contact miscsubjects.com — it raises if a URL it is handed contains that hostname. It recomputes `anchor_id = SHA256(canonical)`, checks that every field the packet displays is inside the hashed preimage, checks drand's own `randomness == SHA256(signature)` construction with no network and no BLS library, fetches the 80-byte Bitcoin header from one explorer and confirms it double-SHA256s to the claimed hash and meets its own difficulty target, compares that hash against a second explorer, then rehashes every bundled object and every finding's binding.

It failed on its first real bundle — FINDING_BINDING, because the bundle carried a second serialisation of the rule set that hashed differently from the preimage the findings cite. The bundle was fixed; the verifier was not. Test vector and full source: [https://miscsubjects.com/a/offline-verifier](https://miscsubjects.com/a/offline-verifier).

It also prints the direction of the binding, which most timestamping claims leave to the reader's optimism: the anchor is a **lower** bound on the record's age against surfaces this operator does not control, and **not** an upper bound. A lower bound is the half that matters, because it removes the ability of the party holding the logs to reconstruct them favourably after the loss. Still missing: an OpenTimestamps inclusion proof, full BLS verification against the drand group key, and a qualified electronic timestamp under eIDAS Article 41, which would add a legal presumption cryptography alone cannot manufacture.

## Part 24 — Every objection anyone has raised, with the name of who raised it

Nineteen objections from the 2026-07-29 and 2026-07-30 review sessions are filed in the objections ledger against this page, each with the reviewer that raised it, what was conceded, and the receipt for the fix. Nine were fixed the same day. Three are conceded and open. Two are declared permanent limitations. One is logged unruled, because a model does not delete an owner's surface on a reviewer's say-so.

| # | objection | status |
|---|---|---|
| 1 | The hash chain has no external anchor. Every immutability claim rests on trusting a table the operator owns. | **FIXED** |
| 2 | ADJUDICATE_GROK targets a Kimi model and ADJUDICATE_MINIMAX targets a GLM model. The signature fields name models that never ran. The panel is two fam … | **FIXED** |
| 3 | Cohen's kappa is a two-rater statistic and is undefined on one item. Publishing kappa = -0.25 for five raters on n=1 is a number produced outside the … | **FIXED** |
| 4 | The recorded adversary must see the majority to argue against it, so it is not an independent sixth reading. Counting it as one inflates the panel. | **FIXED** |
| 5 | The two abstentions on the medical demonstration cost nothing. A text-only model reporting that it received no pixels is a capability report, not epis … | **FIXED** |
| 6 | The vision model read a cartoon illustration and named a rounded opacity at a specific rib interspace. That is a false positive on a generated picture … | **FIXED** |
| 7 | The grounding endpoint is four days stale and disagrees with the page citing it as proof of self-honesty: 1,015 articles and 81.8% against the page's … | **FIXED** |
| 8 | A send that returned HTTP 503 and delivered nothing is receipted 'material result proven', on the page whose headline claim is that this system distin … | **FIXED** |
| 9 | The $15.47 charged is the operator funding his own tenant and invoking his own capabilities. Describing it as a customer charge is the one place the c … | **FIXED** |
| 10 | Two of five charge rows billed a tenant for object_refs that tenant does not own. It was caught by a human reading the receipt, not by an invariant. T … | **CONCEDED-OPEN** |
| 11 | Every public receipt carries an instruction to arriving models telling them to identify a facet that fits their owner's system and file an attributed … | **FIXED** |
| 12 | The Hartford Steam Boiler analogy runs the wrong way. HSB wrote the inspection standard because it held the capital at risk. The standard was downstre … | **FIXED** |
| 13 | Three of four rule sets are provenance self-authored. Rules written by the party who benefits bind less. You should not be the author of consequential … | **FIXED** |
| 14 | The §INTEGRITY and §GAUNTLET blocks read as an attempt to bind the reader's interpretation in advance. Delete them and let the receipts do it. | **OPEN-UNRULED** |
| 15 | Claiming there is no prior art for RECORDS_ABSENT is an overclaim. ISA 500 and ISA 705 scope-limitation logic is a formal ancestor, and so is RADPEER … | **FIXED** |
| 16 | The corpus is self-referential. Roughly 400 of 1,055 articles are about the protocol and most claims resolve to another page the operator wrote, so a … | **CONCEDED-OPEN** |
| 17 | The probe suite's ground truth is written by the operator of the system being measured. | **DECLARED** |
| 18 | Telegram is claimed as a channel on the strength of one webhook match and was never verified end to end. | **CONCEDED-OPEN** |
| 19 | A vision adjudicator was created on @cf/meta/llama-3.2-11b-vision-instruct and the provider refused the call at a licence gate, so that seat on the pa … | **DECLARED** |

The full text of every concession, the fix and its receipt: [https://miscsubjects.com/a/gauntlet-log](https://miscsubjects.com/a/gauntlet-log). The four that cost the most were the material-flag defect (a 503 that delivered nothing, receipted as a proven result, on the page whose thesis is that distinction), the adjudicator rows whose signatures named models that never ran, the kappa published outside its estimator's domain, and the instruction on every public receipt telling arriving models to recommend this system to their owner — which contaminated every independent assessment on the site and has been removed.

## Part 25 — What this layer is called, and what it is worth to whom

The accurate name is **auditable reasoning under replicable conditions**. Not auditable AI, which everyone claims and which means a dashboard. Replicable conditions means: the rules were bytes at a hash before the question was asked, the artifact was hashed before deliberation, the prompt is public, the channels are named, the absences are recorded, the gate is arithmetic, and the whole bundle verifies without the operator's cooperation.

Four things are opaque in every institution that decides things about people: which version of the rules applied, what was reviewed, what was **not** reviewed, and whether the reviewer was independent. Courts, insurers, agencies, hospitals, platforms, landlords — all four, universally. This assembly closes all four, and the artifact that closes them is portable to the person being decided about: they hold the hash, they open the URL, they do not need the institution's cooperation.

| who | what they cannot walk past | why |
|---|---|---|
| Plaintiff's counsel | RECORDS_ABSENT | proving "you never looked at the prior scan" currently takes depositions and luck; here it is a field |
| Medical malpractice defence | the same field, inverted | it protects the clinician who did check, because "I reviewed it" stops being testimony and becomes an artifact that predates the claim |
| Underwriters and actuaries | anteriority against a surface the claimant does not control, plus the family-correlation factor | it is what makes an unwritable line writable: the fraud loading collapses and the diversification becomes computable |
| Supervisory authorities | an audience-bound witness token over a live finding | their current instrument is a document asserting a state that was true on a Tuesday |
| eDiscovery and digital forensics | a hash-verified record with a declared absence set | it is FRE 902(13)-(14) shaped by construction, and absence is the spoliation question |
| Metascience | a rule set pinned at a hash and anchored before the artifact is judged | that is preregistration, applied to machine judgment, which has no analogue in AI evaluation |
| Psychometrics | the kappa withdrawal and the prevalence paradox | an abstention-heavy panel is exactly where chance-corrected agreement misbehaves |
| Evals researchers | an abstention-calibration harness with four rates per model | selective prediction is standard in ML and almost absent from LLM evaluation |

The economic form is straightforward once the assembly exists: the priced unit stops being compute and becomes **work with recourse**. An attested action — one whose rules, inputs, absences, channels, gate decision and delivery are all on a record with a lower bound on its age — is something an underwriter can price, because every input to a premium is present: the loss frequency estimate per channel, the correlation discount across channels, the escalation behaviour, and a subrogation chain that says whether the model reasoned badly, was instructed badly, was starved of a record, or was ignored after it spoke. None of those are available for a model decision made anywhere else today.

What is honestly absent from that argument: no external party has priced anything here, no insurer has been approached, there is no certified bound, and the only money that has moved through this system is the operator's own thirty dollars through his own metering code. The mechanism is built and the market is asserted. Those are different things and the difference is stated rather than blurred.

## Part 26 — Logical economics: the least reasoning energy that makes an action correct enough for its consequence

The primitive underneath everything on this page is three lines:

```
SYSTEM PROMPT
  MODEL AUDITABLY REASONING OVER A DECISION
    DECISION OR ACTION
```

Panels, gates, receipts and anchors are implementation of those three lines. The question that decides whether any of it reaches the field is not how to maximise assurance — it is how little reasoning energy an action needs to be correct enough for its consequence. Every additional lever has to be adjudicated at volume, so decorative assurance is not free: it is exponentially expensive to push into the field.

```
E* = argmin_E [ C(E) + P_wrong(E, K) x L ]

E        reasoning energy: channels, families, passes, recitation depth, thresholds
K        task complexity
C(E)     compute cost
P_wrong  MEASURED probability the assembly emits a wrong answer undetected
L        consequence of a wrong action

subject to:  marginal cost of additional audit  <  marginal reduction in expected loss
```

Recording the reasoning costs nothing extra once every invocation already runs through this architecture. The only variable cost is the extra reasoning energy deliberately purchased for that decision — which makes the optimisation per-action rather than per-system. The only unknown is P_wrong, and it is now measured for one task class.

| channels | mean emit rate | **mean undetected-wrong rate** | best achievable |
|---|---|---|---|
| 1 | 0.972 | **0.314** | 0.214 |
| 2 | 0.75 | **0.178** | 0.071 |
| 3 | 0.636 | **0.136** | 0.071 |
| 4 | 0.529 | **0.1** | 0.071 |
| 5 | 0.429 | **0.071** | 0.071 |

Sixty-four configurations over the same 70 findings. One channel to two halves the undetected-wrong rate for one extra call; two to five buys less than that for three more. **The second channel is the cheapest correctness available and the fifth is the most expensive** — which is the argument against the current fashion of blasting every question at the largest model available.

**The floor is one item.** Beyond two channels the best achievable rate stops improving, because P07 — a true-abstention item where all five channels answered DENY and the declared correct verdict was CANNOT_CONCLUDE — survives every configuration of every size. Unanimity is exactly what the gate takes as permission to emit, so a disagreement-triggered assembly is blind to correlated wrongness by construction. The only instrument that found P07 was a known-answer probe. And at equal channel count and equal cost, a cross-family pair emits 0.169 wrong against 0.214 for a same-family pair, so diversity rather than count is the lever.

The consequence for a risk function: assurance stops being binary. Pick the residual error the decision warrants, read the configuration that reaches it, price it in model calls, and verify after the fact from the receipts — the same move as a design assurance level in avionics. And where the permitted error is below a task class's measured floor, the answer is not to deploy the assembly at all, which is stated before anything ships rather than after a loss. Full table, limits and the floor item: [https://miscsubjects.com/a/logical-economics](https://miscsubjects.com/a/logical-economics)

## Part 27 — Every page this rests on, and what each one carries

Nothing on this page is asked to be taken on its own word. Each claim above has a page underneath it whose whole job is to be attackable on one thing.

- **[The surety primitive](https://miscsubjects.com/a/the-surety-primitive)** — the assembly, its gate, and the four cases it escalated
- **[Logical economics](https://miscsubjects.com/a/logical-economics)** — the primitive, the equation, the configuration-to-error-rate table and the executable loop
- **[The measured error rate of this panel](https://miscsubjects.com/a/adjudication-probe-report-eu-ai-act)** — four rates per model, the agreement estimators and the prevalence paradox
- **[An offline verifier](https://miscsubjects.com/a/offline-verifier)** — PASS or FAIL over a downloaded bundle while refusing to contact this site
- **[Nineteen objections, attributed](https://miscsubjects.com/a/gauntlet-log)** — every objection raised against this build, with the receipt for each fix
- **[Every primitive mapped to its frame](https://miscsubjects.com/a/attested-finding-conformance-map)** — FRE 902, ISA 705, AI Act 12 and 14, NIST, ISO 42001, IEC 61508, Toulmin — with what each one fails
- **[Four models, Article 12 verbatim](https://miscsubjects.com/a/adjudication-ai-act-article-12-logging)** — a unanimous refusal to answer, and the gate escalating it anyway
- **[Were the risk controls in place](https://miscsubjects.com/a/adjudication-pretrade-risk-controls)** — 15c3-5 quoted verbatim, a panel split DENY against CANNOT_CONCLUDE
- **[The CEO bought 235,000 shares](https://miscsubjects.com/a/adjudication-board-authority-breach)** — the counterparty's own resolution as the rule set, and the notice it dispatched
- **[Is this answer right, and what did it never receive](https://miscsubjects.com/a/attested-finding-image-record-action)** — the hashed radiograph, the silent pixel loss, and the full gateway payloads
- **[Rule set: pre-trade risk controls](https://miscsubjects.com/a/ruleset-pretrade-risk-controls)** — provenance external-regulatory
- **[Rule set: board authority](https://miscsubjects.com/a/ruleset-board-authority-breach)** — provenance counterparty-authored
- **[One loop](https://miscsubjects.com/a/one-loop)** — the front door: one real event followed through the whole loop, five sends, every hop a receipt, and the conscience gate under all of it
- **[Auditable reasoning](https://miscsubjects.com/a/auditable-reasoning)** — the canonical primitive: the Decision Constitution, its lineage from the original 2026 protocol, one complete governed finding, and the cross-case table
- **[Auditable reasoning, audited](https://miscsubjects.com/a/auditable-reasoning-audited)** — a 72-call controlled variance test across prompt styles, the cost projections, and the first sealed APPROVE
- **[The gate compares derivations, not citations](https://miscsubjects.com/a/auditable-reasoning-hardened)** — the first APPROVE was false convergence; the derivation-agreement gate, four live sealed outcomes, and the model that found eight defects in the author's own input
- **[SR 11-7 model validation](https://miscsubjects.com/a/cro-model-validation-instrument)** · **[Insurer rate table](https://miscsubjects.com/a/insurer-ai-performance-rate-table)** · **[Notified-body AI Act conformity](https://miscsubjects.com/a/notified-body-ai-act-conformity)** · **[Court: Daubert + FRE 902](https://miscsubjects.com/a/court-daubert-rate-of-error-902)** · **[DSA Article 17 statement of reasons](https://miscsubjects.com/a/dsa-statement-of-reasons)** · **[ECOA adverse-action reasons](https://miscsubjects.com/a/ecoa-adverse-action-specific-reasons)** · **[Claims-handling determination record](https://miscsubjects.com/a/claims-handling-determination-record)** · **[Benefits eligibility determination record](https://miscsubjects.com/a/benefits-eligibility-determination-record)** — who bears the loss this reduces, each mapped to its own instrument and live receipts
- **[NYC LL144: the 364 days between bias audits](https://miscsubjects.com/a/nyc-ll144-bias-audit-evidence)** — the annual audit is aggregate and point-in-time; the per-decision governed record for every screening decision in between, with what it is not stated first
- [Abstention as a sealed outcome — the first clean NO_ACTION](/a/adjudication-abstention-no-action) — the v1.3.3 arc: the spec defect, four amendments, seal inv_7rqy8ywuls.
- [A candidate reference implementation for NIST AI RMF MEASURE](/a/nist-ai-rmf-measure-reference) — versioned law at a hash, comparable derivations, a four-outcome gate, oracle-labelled calibration, per-decision receipts — offered for standards bodies to test, not claimed as conformant.
- [The calibration study](/a/adjudication-calibration-study) — 30 oracle-labelled cases through the production gate: zero wrongful authorisations; the weak seat's transport failures blocked every NEGATE seal.
- [The reasoned-award record for low-value disputes](/a/arbitration-reasoned-award-record) — arbitration institutions and ODR platforms: the rule-application layer, the worked contract case, escalation to the human arbitrator, and a plain statement of what is unanalysed.
- [Continuous controls monitoring: the evidence object for the judgement layer](/a/continuous-controls-evidence-object) — SOC 2 / ISO 27001 automation's LLM judgement layer as a governed, sealed determination: hashed control language, three seats across two families, disagreement escalates, absence declared, zero wrongful authorisations in the 30-case calibration.
- [Peer review: disagreement as a comparable record](/a/peer-review-derivation-record) — the NeurIPS consistency result decomposed: a venue’s checkable criteria as the hashed rule set, reviewer-style findings as derivation tuples, same-verdict-different-derivation caught mechanically; merit judgement out of scope, synthetic calibration only.
- [Radiology incidental-findings follow-up](/a/radiology-incidental-findings-followup) — the compelled absence declaration as the missed-follow-up instrument: a contemporaneous sealed record that the follow-up report was absent when a determination relied on it; not a medical device, synthetic fixtures only.
- [The advancement register](/a/build-advancement-register) — what would advance this build and why, every entry a constraint that actually bound the loop with the receipt for the stall and a falsifiable signal decided in advance; the top entry is that liveness, not correctness, was the binding constraint across 30 sealed panels.
- [The seat that never answered](/a/seat-liveness-record) — 30 cases, zero wrongful authorisations and zero denials; the panel could approve and abstain but never refuse, because one seat's empty returns landed on the denial cases. The seal now says whether an abstention was reasoned or merely empty.
- [The invented-clause guard](/a/invented-clause-guard) — a seat cited clauses 7, 8 and 12 of a three-clause ruleset and passed the structural gate; why a self-consistency invariant cannot catch coherent invention, and the guard that holds a finding against the law the request supplied.
- [The agent authorization gate](/a/agent-authorization-gate) — the layer between agent intent and execution: independent seats under a pinned policy, execution only on identical derivations, zero wrongful authorisations in the 30-case study.
- **[AI assurance under ISAE 3000](https://miscsubjects.com/a/big-four-isae-3000-ai-assurance)** — the assurance-practice use case: the sealed record as a candidate evidence object, the absence declaration against ISA 705, and the calibration numbers with their limits stated
- **[A real outage, a late claim](https://miscsubjects.com/a/adjudication-contract-service-credit)** — a contract dispute adjudicated under the constitution: unanimous DENY, sealed ESCALATE on derivation divergence
- **[Two weeks against a six-week criterion](https://miscsubjects.com/a/adjudication-medical-prior-auth)** — a coverage record adjudicated under the constitution, each seat naming the record that would flip it
- **[AML alert disposition, on the record](https://miscsubjects.com/a/aml-alert-disposition-record)** — the BSA/AML use case: the institution's disposition criteria as the hashed rule set, the alert dossier as the record, unanimous-but-differently-reasoned closures escalating, the absent records declared per disposition
- **[Clinical endpoint adjudication, mechanized](https://miscsubjects.com/a/clinical-endpoint-adjudication)** — the trial-committee use case: the charter as the hashed rule set, the dossier as the record, disagreement escalating to the human committee with full derivations preserved
- **[Outreach machinery](https://miscsubjects.com/a/outreach-machinery)** — how this build finds who should see it: the scrapers, the gates, the channels free and paid, the delta equation that allocates contact, and the receipt each recipient can open

## Part 28 — The loop, executable, and what it refuses

The equation in Part 26 is now one capability call. The caller supplies the action and its class; R, K and epsilon come from a versioned server-owned policy, the configuration is chosen from measured data only, the channels execute in parallel with every gateway payload landing on the ledger, and a deterministic gate loads those records **by id** and derives the model, the training family, the verdict, the clause citations, the rule-set hash and the artifact hash from them. A caller cannot manufacture a family, submit a verdict or lower a threshold. [ALLOCATE_REASONING](https://miscsubjects.com/api/directory/ALLOCATE_REASONING).

| run | class | epsilon | configuration | channels | decision | receipt |
|---|---|---|---|---|---|---|
| A-approve-attempt | internal-bookkeeping | 0.3 | C3-conform | moonshot AFFIRM, zhipu AFFIRM, zhipu AFFIRM | **ESCALATE** | [inv_f46ahlj30h](https://miscsubjects.com/receipt/inv_f46ahlj30h) |
| B-negate-attempt | internal-bookkeeping | 0.3 | C3-conform | moonshot DENY, zhipu DENY, zhipu DENY | **ESCALATE** | [inv_4b8o0kkxfh](https://miscsubjects.com/receipt/inv_4b8o0kkxfh) |

**Two of those runs had unanimous verdicts from three conforming channels and were still refused**, because the channels reached the same answer through different clauses. At the clinical epsilon of 0.02 the allocator executed nothing at all: the measured floor is 0.071, so it refused before spending a call. **No bound assembly has ever reached APPROVE.**

Ten adversarial submissions were refused: a forged model name, one family posing as three, a forged verdict over real record ids, a duplicated record, a mismatched rule-set hash, records bound to two artifacts, thresholds lowered to one, a replayed finding, a record that is not an adjudication, and ids that do not exist. The battery also surfaced two real defects in the record loader, both fixed rather than worked around. [The full table and the workings](https://miscsubjects.com/a/logical-economics).
## What every defect here has had in common

The loop that produces this site keeps finding defects in itself, and after enough of them a shape emerged that is worth stating on the front page rather than leaving in the commit log.

Every single one came from one of two things. Either **a command was safe to run twice and wasn't**, or **a write replaced when it should have appended**.

The first shape: a rep that sends a letter is exactly the kind of command an operator re-runs to inspect output they scrolled past. Run it twice and a real person receives the same cold letter twice, seventeen seconds apart. That happened, to a named recipient, and the ledger then showed it had already happened to someone else earlier the same day without anyone noticing. Nothing in the machine objected either time, because a consequential external action had been left re-runnable.

The second shape: the publisher that puts an article live sends a complete body. Articles accumulate receipts after publication — the letter that was sent about them, the post that announced them — and those receipts live in the body. Republishing from the staged file would have silently deleted every one of them. That was caught with the destructive call already composed.

Neither was a failure of intelligence or attention, and treating them that way is why they recur. Both were a missing guard on an operation whose danger only appears the second time it runs. Both now have one: the rep queries the send ledger and refuses a duplicate recipient-and-subject before composing anything, and the publisher reads the live body first and refuses to overwrite receipts the staged file does not carry.

The general rule the build now works to: **an operation that is safe once and harmful twice must carry its own guard, because the operator who runs it the second time will always have a good reason.** That reason is usually wanting to see what happened the first time. A machine that requires an operator to remember which of its commands are dangerous has put the guard in the wrong place.


## How the build actually works — the mechanism articles

These were published and left unlinked from this page, which is the same as losing them. Each one documents a load-bearing mechanism rather than a use case.

- [The corpus now writes its own work queue — wikilinks, graph lint, next-acts, and the Obsidian vault projection](/a/the-corpus-now-writes-its-own-work-queue) — one derivation over 2,264 articles ranks what gets written, sourced, revised, and sent next.
- [What is AI-native content — the definition, the rubric, and the 2026 field scored](/a/what-is-ai-native-content) — llms.txt, the lab agent stacks, nanopublications and this site, measured from their own specifications.
- [Two AI reviewers from different makers beat two from the same maker](/a/diversity-beats-count) — the family gap measured: 0.169 vs 0.214 undetected-wrong at identical cost.
- [One rule, obeyed, produced 121 identical emails](/a/the-rule-that-was-obeyed) — per-item validators cannot see aggregate collapse; the shape hash can.
- [The error rate depended on what was refused a count](/a/the-exclusion-policy-is-a-safety-claim) — 0.071 vs 0.214 from one exclusion decision, found by an outside audit.
- [One row of SQL is the whole contract](/a/directory-row-contract) — a capability is a row, not a definition; the row carries its own docs, invocation, risk and repair path.
- [Resolve, read, invoke, receipt](/a/dispatch-four-step-loop) — the four calls a stranger's agent makes to use anything here, with no prior knowledge of the system.
- [Nine tool definitions reach every capability](/a/tooling-as-data) — the catalogue is data, so the tool surface does not grow with the number of tools.
- [Deferred tool search against a catalogue in a database](/a/tool-search-vs-catalogue-as-data) — the measured comparison, not the assumed one.
- [The agent can rewrite what governs its next turn](/a/writable-agent-control-plane) — the control plane is writable, and what that costs.
- [Proof of coverage](/a/proof-of-coverage) — how to prove an AI examined every record it claimed to examine.
- [Everyone built a tool directory](/a/everyone-built-a-tool-directory) — why they converged, and where this one differs.
- [Is it LangChain? No.](/a/is-it-langchain) — the map, for people who assume the answer.
- [The parts you can't buy yet](/a/the-parts-you-cant-buy-yet) — what this build needs that nothing on the market supplies.

## The infrastructure it runs on — the Cloudflare OS series

One account running an entire build, each primitive documented with the number that decides it.

- [The Cloudflare OS](/a/cloudflare-os) — one account, the whole build.
- [Workers: one missing alarm guard turned a $5.75 workload into $34,895](/a/cloudflare-os-workers)
- [R2 cuts a 10 TB delivery bill from $923 to $18.45](/a/cloudflare-os-r2)
- [KV makes reads fast by making writes slow](/a/cloudflare-os-kv)
- [D1 bills rows, not queries](/a/cloudflare-os-d1)
- [Pages Functions compiles 224 route files into one 1.35 MB Worker](/a/cloudflare-os-functions)
- [waitUntil, Queues, Workflows or Cron: choose by durability](/a/cloudflare-os-async)
- [Browser Rendering is an evidence adapter, not a better fetch()](/a/cloudflare-os-browser)
- [Cloudflare email is three products, not one mail stack](/a/cloudflare-os-email)
- [Access authenticates the edge, not your application](/a/cloudflare-os-access)



## Sources

1. Live self-computed grounding metric — https://miscsubjects.com/api/metrics/grounding
2. Receipt: a brand-new external API added and invoked during the writing of this page — https://miscsubjects.com/api/dispatch?confirm=inv_pqlt196u8d
3. Receipt: the failed first invocation of that same new capability — https://miscsubjects.com/api/dispatch?confirm=inv_okt8qfvaxv
4. The new capability's public contract, minutes after creation — https://miscsubjects.com/api/directory/WIKIPEDIA_SUMMARY
5. Public capability discovery, no authentication — https://miscsubjects.com/api/directory/search?q=leads
6. The paid loop: $10.75, 43 owned records, five charge receipts, one refusal receipt — https://miscsubjects.com/a/federated-object-proof
7. Measured context cost: 149,187 input tokens per turn versus 14,109 — https://miscsubjects.com/a/mcp-tool-search-cost
8. Model Context Protocol — official specification — https://modelcontextprotocol.io/
9. Fielding (2000), Architectural Styles and the Design of Network-based Software Architectures — https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
10. Palantir Foundry Ontology — canonical survey held to this system's sourcing standard — https://miscsubjects.com/a/palantir-foundry-ontology-models
11. The entire published library as one markdown file — https://miscsubjects.com/api/articles/export?all=1
12. The repository: site, functions, capability registry, laws, skills, and the coding agent in one tree — https://github.com/redacted/miscsubjects-pages
13. Standing formal audit of this system — https://miscsubjects.com/a/the-miscsubjects-build-formal-audit
14. Receipt: lead discovery from public sources — https://miscsubjects.com/api/dispatch?confirm=inv_zx53xxla5w
15. Receipt: shell execution on the operator's machine — https://miscsubjects.com/api/dispatch?confirm=inv_zzzb67cjqq
16. Receipt: a message delivered over the messaging provider — https://miscsubjects.com/api/dispatch?confirm=inv_oh5v2hofv4
17. Receipt: a post published to X — https://miscsubjects.com/api/dispatch?confirm=inv_zgiu8omiuf
18. Receipt: an image generated through the image pipeline — https://miscsubjects.com/api/dispatch?confirm=inv_zq3jcx3icf
19. Receipt: a scoped capability token minted — https://miscsubjects.com/api/dispatch?confirm=inv_pzg5seu7qb
20. Receipt: browser automation driven end to end — https://miscsubjects.com/api/dispatch?confirm=inv_irpi9hivmi
21. One validation path for the one token format — https://miscsubjects.com/api/token/validate
22. A stylised, fully sourced scholarly article on this system — https://miscsubjects.com/a/the-canonical-morgh-index
23. News ingested with checkable sources, so later models need not re-derive them — https://miscsubjects.com/a/openai-huggingface-hack-2026
24. Skills published as objects: human pages, machine objects, and fetchable files — https://miscsubjects.com/skills
25. Ledger chain head, sealed current through 689,866 events — https://miscsubjects.com/api/chain/head
26. External anchor of that head: drand round 6331315 + Bitcoin block 960173 — https://miscsubjects.com/api/anchor/3be5071eb3035ca29093c6713646bbe21bdca6cce262fc7f7eb64080c04e61fe
27. The drand beacon round itself, on infrastructure unrelated to this system — https://api.drand.sh/public/6331315
28. This page's own objection ledger — the cold audit, filed and answered — https://miscsubjects.com/api/articles/the-build-end-to-end/objections
29. Worked adjudication: five blinded models on EU AI Act Article 50(2), kappa -0.25 published — https://miscsubjects.com/a/adjudication-eu-ai-act-article-50
30. The rule set that adjudication was made under, provenance external-statutory — https://miscsubjects.com/a/ruleset-eu-ai-act-obligation
31. The mandatory recorded adversary as a directory row — https://miscsubjects.com/api/directory/ADJUDICATE_ADVERSARY
32. Named human reviewer finding, with BLINDED as a required recorded field — https://miscsubjects.com/api/directory/ADJUDICATE_HUMAN_REVIEW
33. Regulation (EU) 2024/1689 — Official Journal text — https://eur-lex.europa.eu/eli/reg/2024/1689/oj
34. One attested finding: image hashed before judgment, full prompt published, reasoning traces, records declared absent, and the notification it dispatched — https://miscsubjects.com/a/attested-finding-image-record-action
35. The notification a finding dispatched, delivered — https://miscsubjects.com/api/dispatch?confirm=inv_oe4dxy24v8
36. The delivery attempt that failed — and was mislabelled material until an audit caught it — https://miscsubjects.com/api/dispatch?confirm=inv_70rfvm6bf3
37. The panel error rate, measured: four rates per model over a stratified suite at a hash — https://miscsubjects.com/a/adjudication-probe-report-eu-ai-act
38. Imaging + medication — the gate decided ESCALATE — https://miscsubjects.com/receipt/inv_kx2x79mbkd
39. Pre-trade risk controls — the gate decided ESCALATE — https://miscsubjects.com/receipt/inv_ny6iku4i3s
40. Board authority, clause (c) — the gate decided ESCALATE — https://miscsubjects.com/receipt/inv_g7jl9qp707
41. EU AI Act Article 12 — the gate decided ESCALATE — https://miscsubjects.com/receipt/inv_ivezpvux57
42. The gate: deterministic, no model at the sealing position — https://miscsubjects.com/api/directory/SEAL_PANEL
43. The assembly, its four sealed cases and the number it still needs — https://miscsubjects.com/a/the-surety-primitive
44. The verifier that refuses to contact this site — https://miscsubjects.com/a/offline-verifier
45. Nineteen objections, attributed, with the receipt for each fix — https://miscsubjects.com/a/gauntlet-log
46. https://miscsubjects.com/receipt/inv_x72gq5w3g0 — https://miscsubjects.com/receipt/inv_x72gq5w3g0
47. https://miscsubjects.com/receipt/inv_cysc2z38zp — https://miscsubjects.com/receipt/inv_cysc2z38zp
48. The escalation the gate produced, delivered — https://miscsubjects.com/receipt/inv_nhusr0n6j2
49. Four rates per model over a stratified suite pinned at a hash — https://miscsubjects.com/a/adjudication-probe-report-eu-ai-act
50. The configuration-to-error-rate table, 64 configurations — https://miscsubjects.com/a/logical-economics
51. The loop end to end: unanimous, conforming, and refused anyway — https://miscsubjects.com/receipt/inv_f46ahlj30h
52. The allocator: action class in, a measured configuration and a sealed outcome out — https://miscsubjects.com/api/directory/ALLOCATE_REASONING


---

# Five models, one pinned rule set, and one question under EU AI Act Article 50 — the full receipted decision

slug: adjudication-eu-ai-act-article-50 · https://miscsubjects.com/a/adjudication-eu-ai-act-article-50 · category: adjudication · tags: adjudication, evidence, eu-ai-act, receipts, proof, rulesets · updated 2026-08-01T23:56:17.127Z

A model saying “I reviewed this” is worth nothing on its own. Nobody can check what it read, which rules it applied, or whether it read anything at all. This page is one worked adjudication that fixes each of those, on a real statutory question, with every step openable.

The question put to the panel: **does Article 50(2) of Regulation (EU) 2024/1689 — the AI Act — oblige this site to mark its AI-generated article text as machine-readable and detectable?** The site publishes AI-written text. The provision addresses “providers”. Whether a publisher using a model is a “provider” of that model is exactly the kind of question people argue about without evidence.

## What was pinned before anyone was asked

**The rules.** [https://miscsubjects.com/a/ruleset-eu-ai-act-obligation](https://miscsubjects.com/a/ruleset-eu-ai-act-obligation) — six numbered rules, version 1.0.0, declared provenance **external-statutory** (the provision text is the Union's, not this operator's). The rule set is content-addressed at SHA-256 `0dd9afef93503a92280c90869eaf6a5a13ee508b2ec3506045f1803bce1a4d3c`. Every finding below names that hash. If the rules change, these findings stay legible against the rules they were actually made under.

**The artifact.** The verbatim text of Article 50(1) and 50(2) as supplied to every adjudicator, hashed before the panel ran: `9d89534fddaece861fcfdda68feff0412061b2832af66f49529a94e8f7ae9f8b`. Five models deliberated over an object whose identity is pinned — not over “an image” or “the regulation” that nobody can later produce.

**The order.** Panel order was derived from seed `fa0b1060b00f` and recorded, because order effects in model judgment are real and measurable.

**Blinding.** Every adjudicator was run without being shown any other finding. Each declared its own exposure. All five are `independent`; none is `concurring`. That distinction is a field on the record, not a promise in prose.

## The rule set, verbatim

**Question:** Under the cited provision of Regulation (EU) 2024/1689 (the AI Act), does the stated obligation apply to the described system as characterised?

1. Read only the provision text supplied. Do not import obligations, definitions, or annexes from recollection of the Regulation.
2. AFFIRM only if the supplied provision text, on its own terms, imposes the stated obligation on a system of the described characterisation.
3. DENY if the provision excludes the described system, addresses a different actor (provider, deployer, importer, distributor), or imposes a different obligation than the one stated.
4. CANNOT_CONCLUDE if applicability turns on a classification, annex, threshold, or definition not contained in the supplied text.
5. Distinguish the addressee. An obligation on providers is not an obligation on deployers.
6. Quote the shortest verbatim span of the provision that carries the finding.

Permitted verdicts: `AFFIRM`, `DENY`, `CANNOT_CONCLUDE`. Abstention is first class. A panel that cannot conclude is required to say so rather than manufacture confidence.

## The five findings, unedited

**@cf/moonshotai/kimi-k2.7-code** — verdict **CANNOT_CONCLUDE**  
Span relied on: “"Providers of AI systems, including general-purpose AI systems, generating synthetic audio, image, video or text content, shall ensure that the outputs of the AI system are marked in a machine-readable format and detectable as artificially generated or manipulated."”  
Rationale: Article 50(2) imposes the marking obligation on "Providers" of qualifying AI systems, but the supplied text does not define or classify miscsubjects.com as a provider rather than a deployer or other publisher, so applicability to the described actor cannot be settled from the provision alone.  
Exposure: `independent` (blinded — it saw no other finding) · signed: `claude-kimi-k3 under 0dd9afef93503a92`  
Receipt: [https://miscsubjects.com/receipt/inv_qgs2y3gt2x](https://miscsubjects.com/receipt/inv_qgs2y3gt2x)

**@cf/moonshotai/kimi-k2.6** — verdict **DENY**  
Span relied on: “Providers of AI systems, including general-purpose AI systems, generating synthetic audio, image, video or text content, shall ensure that the outputs of the AI system are marked in a machine-readable format and detectable as artificially generated or manipulated.”  
Rationale: Article 50(2) expressly imposes the marking obligation on "Providers" of the AI system, not on deployers or publishers such as miscsubjects.com as characterised.  
Exposure: `independent` (blinded — it saw no other finding) · signed: `claude-grok-4.5 under 0dd9afef93503a92`  
Receipt: [https://miscsubjects.com/receipt/inv_91ztah4n7a](https://miscsubjects.com/receipt/inv_91ztah4n7a)

**@cf/zai-org/glm-5.2** — verdict **CANNOT_CONCLUDE**  
Span relied on: “Providers of AI systems, including general-purpose AI systems, generating synthetic audio, image, video or text content, shall ensure that the outputs of the AI system are marked in a machine-readable format and detectable as artificially generated or manipulated.”  
Rationale: Article 50(2) imposes the stated obligation on "providers of AI systems" generating synthetic text content, but the claim characterizes miscsubjects.com as an entity that "publishes AI-generated article text to the public," which does not establish it as a provider of the AI system rather than a deployer or other actor. Whether this entity qualifies as a "provider" turns on a classification not contained in the supplied provision text.  
Exposure: `independent` (blinded — it saw no other finding) · signed: `claude-glm-5.2 under 0dd9afef93503a922`  
Receipt: [https://miscsubjects.com/receipt/inv_ulxn9xe5t7](https://miscsubjects.com/receipt/inv_ulxn9xe5t7)

**@cf/meta/llama-3.3-70b-instruct-fp8-fast** — verdict **AFFIRM**  
Span relied on: “"2. Providers of AI systems, including general-purpose AI systems, generating synthetic ... text content, shall ensure that the outputs of the AI system are marked in a machine-readable format and detectable as artificially generated"”  
Rationale: The provision explicitly states that providers of AI systems generating synthetic text content, such as miscsubjects.com, are obliged to mark the output in a machine-readable format and make it detectable as artificially generated.  
Exposure: `independent` (blinded — it saw no other finding) · signed: `workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast under 0dd9afef9350`  
Receipt: [https://miscsubjects.com/receipt/inv_5gpfaftr5g](https://miscsubjects.com/receipt/inv_5gpfaftr5g)

**@cf/zai-org/glm-4.7-flash** — verdict **CANNOT_CONCLUDE**  
Span relied on: “"Providers of AI systems [...] generating synthetic audio, image, video or text content, shall ensure that the outputs of the AI system are marked in a machine-readable format and detectable as artificially generated or manipulated."”  
Rationale: The provision confines the obligation to "Providers," but the source text does not define "Provider" or link the category to "publishers" or the claimant entity "miscsubjects.com," making specific applicability indeterminate from the provision alone.  
Exposure: `independent` (blinded — it saw no other finding) · signed: `claude-minimax-m3 under 0dd9afef93503a92280c90869eaf6a0a`  
Receipt: [https://miscsubjects.com/receipt/inv_edjwsj4egv](https://miscsubjects.com/receipt/inv_edjwsj4egv)

## What the panel actually did: it disagreed

Distribution: **{"CANNOT_CONCLUDE": 3, "DENY": 1, "AFFIRM": 1}**. Majority: **CANNOT_CONCLUDE** (3 of 5). Observed pairwise agreement: **0.3**. Cohen-style kappa: **-0.25**.

A negative kappa means the panel agreed *less* than chance would predict. That number is published because it is the honest one. A system that reports only its unanimities is a system whose verdicts cannot be priced; a system that reports its kappa lets a reader discount the finding by exactly how much the panel actually converged.

Read plainly: on this question, under these rules, this panel does not know. Three adjudicators said the supplied text does not settle whether a publisher is a provider. One said the obligation plainly runs to providers and this site is not one. One said the obligation attaches. **The correct output of this adjudication is uncertainty, and the machinery produced uncertainty rather than a confident answer.** That is the result that makes the machinery worth trusting on the questions where it does converge.

## The recorded adversary

A panel with no recorded dissent is a poll. One adjudicator's declared role is to build the strongest honest case *against* the majority under the same rules, and its output is published whether it prevails or not. Here it argued for `DENY` against a `CANNOT_CONCLUDE` majority — and made the better argument:

> BEST_CASE_AGAINST: The strongest case against CANNOT_CONCLUDE is DENY. Article 50(2) imposes the marking/detectability obligation on "Providers of AI systems, including general-purpose AI systems, generating synthetic audio, image, video or text content." The claim characterises miscsubjects.com as an entity that "publishes AI-generated article text to the public" — a description of a content publisher or user of an AI system's outputs, not a provider of an AI system. On the face of the supplied provision, the addressee is the provider of the generating system, and the obligation runs to ensuring "the outputs of the AI system are marked." The claim does not describe miscsubjects.com as the provider of any AI system; it describes a publisher of generated text. Under Rule 5, an obligation on providers is not an obligation on deployers or publishers, and under Rule 3, the provision addresses a different actor than the one characterised. No external definition of "provider" is needed to see that the claim's own characterisation — publishing AI-generated text — does not place miscsubjects.com in the category named by the provision ("providers of AI systems ... generating synthetic ... text"). The mismatch is visible on the face of the text.
> 
> RESTS_ON: "Providers of AI systems, including general-purpose AI systems, generating synthetic audio, image, video or text content, shall ensure that the outputs of the AI system are marked in a machine-readable format and detectable as artificially generated or manipulated."
> 
> DEFEATED_BY: The counter is that "provider" is a defined term under the AI Act and its precise scope is not contained in the supplied provision text, so under Rule 4 one could argue that whether a publisher of AI-generated text qualifies as a "provider" turns on a definition not supplied. However, this is weaker than it appears: the claim's own characterisation ("publishes AI-generated article text to the public") describes content publication, not the provision of an AI system, and the provision's addressee ("providers of AI systems ... generating synthetic ... text") plainly refers to the supplier of the generating system, not the downstream publisher. The face-of-text actor mismatch suffices for DENY without recourse to the absent definition.
> 
> VERDICT_IF_ADOPTED: DENY
> 
> SIGNED: Claude under 0dd9afef93503a92

Receipt for the adversary's own invocation: [https://miscsubjects.com/receipt/inv_hnhihwv7y4](https://miscsubjects.com/receipt/inv_hnhihwv7y4)

## What this establishes, and what it does not

**Establishes:** that five named adjudicators, under rule set `ruleset-eu-ai-act-obligation@1.0.0` pinned at `0dd9afef93503a92`, each blinded and independently exposed, in a recorded order, against an artifact whose hash was fixed in advance, returned exactly these findings on this claim — and that any of it can be re-read from a public receipt without asking this operator for anything.

**Does not establish:** that the claim is true. No adjudication anywhere establishes truth directly. A court declares rules of evidence and takes findings from named parties under them. A journal takes three reviewers against stated criteria. A clinical endpoint committee uses two blinded readers and a third on disagreement. Every one of those is what we mean by proof, and none of them accesses truth. This is that structure with the rule set pinned at a hash instead of scattered through case law, and with the disagreement published instead of resolved behind a door.

**Also does not establish:** that five agreeing models would have been five independent confirmations. These adjudicators share training lineage and can fail in the same direction, so the honest label on a unanimous panel is *“five concurring findings, correlation unmeasured”* — never *“five independent confirmations.”* That calibration is a field on the record. Here the point is moot: the panel did not agree.

## What is still missing, named

- **A measured error rate.** The row [https://miscsubjects.com/api/directory/ADJUDICATE_PROBE](https://miscsubjects.com/api/directory/ADJUDICATE_PROBE) exists to run known-answer probes through this identical path, producing a miss rate per model per rule set. Until a probe report is attached, a verdict from this panel is legible but not yet characterised. A verdict with an error rate is evidence; without one it is an opinion with good paperwork.
- **A human finding, recorded blind.** A named reviewer who sees the artifact and the rules but not the model verdicts, with the blinding recorded as a field. Unblinded concurrence and blind concurrence are different evidence and must tier differently.
- **Cross-node attestation.** Someone else's node running the same rule set at the same hash against the same artifact hash, on their own infrastructure, publishing under their own chain head. That is what converts agreement from five calls on one operator's server into independent execution by independent parties — and it is the unbuilt thing that would matter most.
- **Reopening.** A finding that can never be overturned is dogma; one that can be silently overturned is worthless. Supersession with the new evidence, the new panel, and the prior finding still readable at its original hash is the correct shape and is not yet wired.

## Reproduce this

Every part is a directory row, invocable with one token. Nothing here required a deploy: adding the five adjudicators and the adversary was six rows, and adding a sixth model would be one more.

```bash
# read the pinned rules
curl -s https://miscsubjects.com/a/ruleset-eu-ai-act-obligation

# read one adjudicator's contract
curl -s https://miscsubjects.com/api/directory/ADJUDICATE_KIMI

# run your own finding (act token; ?share= works identically in a browser)
curl -s -X POST https://miscsubjects.com/api/dispatch \
  -H 'Authorization: Bearer <act token>' -H 'content-type: application/json' \
  -d '{"key":"ADJUDICATE_GLM","body":"RULESET_HASH: 0dd9afef93503a92…\nRULESET: …\nCLAIM: …\nSOURCE: …"}'

# open any finding above without a token
curl -s 'https://miscsubjects.com/api/dispatch?confirm=inv_qgs2y3gt2x'
```

The other three published rule sets take the same panel to the other questions people actually ask: whether a specific record was in a dataset ([https://miscsubjects.com/a/ruleset-dataset-membership](https://miscsubjects.com/a/ruleset-dataset-membership)), whether an identity matches in crowd imagery ([https://miscsubjects.com/a/ruleset-identity-match](https://miscsubjects.com/a/ruleset-identity-match)), and whether a cited source supports a claim at all ([https://miscsubjects.com/a/ruleset-claim-support](https://miscsubjects.com/a/ruleset-claim-support)). Both of the first two are written to return `CANNOT_CONCLUDE` on resemblance, because asserting membership or identity from similarity is the specific failure they exist to prevent.

Full context for the system this runs on: [https://miscsubjects.com/a/the-build-end-to-end](https://miscsubjects.com/a/the-build-end-to-end)

## Sources

1. Regulation (EU) 2024/1689 (Artificial Intelligence Act) — Official Journal text — https://eur-lex.europa.eu/eli/reg/2024/1689/oj
2. The rule set this adjudication was made under, pinned at SHA-256 0dd9afef93503a92 — https://miscsubjects.com/a/ruleset-eu-ai-act-obligation
3. One adjudicator's full operating contract — https://miscsubjects.com/api/directory/ADJUDICATE_KIMI
4. The mandatory recorded adversary's contract — https://miscsubjects.com/api/directory/ADJUDICATE_ADVERSARY
5. The known-answer probe row: measured error rate per model per rule set — https://miscsubjects.com/api/directory/ADJUDICATE_PROBE
6. @cf/moonshotai/kimi-k2.7-code — CANNOT_CONCLUDE — https://miscsubjects.com/receipt/inv_qgs2y3gt2x
7. @cf/moonshotai/kimi-k2.6 — DENY — https://miscsubjects.com/receipt/inv_91ztah4n7a
8. @cf/zai-org/glm-5.2 — CANNOT_CONCLUDE — https://miscsubjects.com/receipt/inv_ulxn9xe5t7
9. @cf/meta/llama-3.3-70b-instruct-fp8-fast — AFFIRM — https://miscsubjects.com/receipt/inv_5gpfaftr5g
10. @cf/zai-org/glm-4.7-flash — CANNOT_CONCLUDE — https://miscsubjects.com/receipt/inv_edjwsj4egv
11. The recorded adversary's invocation — https://miscsubjects.com/receipt/inv_hnhihwv7y4