miscsubjectsAI governance
Object Invocation Protocol · protocol specification

Total Structure v3: Appendix B

Copies the public OIP protocol bundle: article, JSON-native map, routes, receipts. No owner token.

§SELF — protocol specification · traversal JSON in-band
## §SELF — OIP protocol specification

**What this page is:** the normative root specification for the Object Invocation Protocol.

**What it specifies:** protocol unit, object contract, invocation route, authority scope, receipt schema, replay, repair, and conformance.

**Read:** https://miscsubjects.com/a/oip-v3-appendix-b
**This page as JSON:** https://miscsubjects.com/api/articles/oip-v3-appendix-b
**Machine bundle:** https://miscsubjects.com/api/articles/oip-v3-appendix-b/bundle?format=markdown
**Voxel graph (philosophy plane wired to protocol plane):** https://miscsubjects.com/api/articles/oip/voxels
**Live object tree:** https://miscsubjects.com/api/dispatch?map=1&format=markdown
**Find an object from plain language:** https://miscsubjects.com/api/dispatch?ask=<what you want>
**Read one object:** https://miscsubjects.com/api/dispatch?key=<KEY>&format=markdown

**Proof rule:** an action is not proven by intent, description, or a 200. It is proven by the ledger and the OIP receipt for the invocation.

APPENDIX B — The Benchmark

The implementation test for the machine plane compares six conditions on audit-dependent tasks:

  • A — single unscaffolded frontier model, one-shot.
  • B — single scaffolded model with deterministic proof structure.
  • C — multiple unscaffolded models, consensus voting.
  • D — role-separated deterministic team: generator, decomposer, verifier, red-team, repairer, compressor, ledger.
  • E — LLM-as-OS dynamic router: deterministic command plane selecting per task among local/open-weight/frontier models, tools, context, proof depth, red-team depth, privacy mode, and ledgering, under cost, privacy, latency, and surety constraints.
  • Fnew in v3.0: a live object-grammar deployment (Law VI pattern): one dispatch door, contract-resolved invocation, mandatory receipts, repair lineage, scheduled zero-context review. F tests what A–E cannot: the grammar under real operation over time — reuse rates, repair-lineage integrity, review-loop effect on artifact quality, delegation safety under scoped tokens.

Metrics: correctness, auditability, reproducibility, adversarial survival, token cost, compute cost, latency, human verification time and time saved, failure cost (domain-weighted), reuse value, proof-reuse rate, repair-lineage integrity (fraction of failures with attached fixes), review-score trajectory over versions, data-custody and privacy cost, actionability. Derived: surety, logical energy, logical density, task-adjusted logical density.

Predictions: D dominates A and C where surety gain exceeds coordination cost; E dominates D across heterogeneous task sets; F's review-score trajectory rises across versions (S8's constructive prediction) and F's repair-lineage integrity stays near unity where A–E's unlinked-guess rate grows with volume.

Validity requirements: demonstrably audit-dependent tasks; diverse error distributions; measured (not assumed) coordination cost; defined deployment window; pre-published failure-cost weighting; ground truth independent of the evaluated systems; pre-defined privacy scoring; for F, review parameters declared before the window opens (IX.10).

Falsifiers: A consistently beats D/E/F on task-adjusted logical density; surety/alpha cost curves fail to fall under deterministic scaffolding; proof reuse fails to beat regeneration over the window; routing overhead exceeds task-adjusted gain; F's review scores stagnate or degrade across versions (S8); F's repair lineage decays with scale (S7).

---

---

Corpus map

Evidence · 1 sources · swipe →chain bcb2d03065a7 · verify chain · provenance

Key evidence

1 claims · tier-ranked · API
Low-confidence / auto-generated 1
speculative0.12
Commercial vendors and clinics market this compound (1 commercial/clinic sources catalogued) — marketing material, not evidence.
commercial vendors
Collapsed 4 duplicate marketing claims
sources: s1
oip-v3-appendix-b · posted 2026-07-04 · updated 2026-07-17 · 4 prior revisions · Fable 5 (Claude Code)
Ledger API & provenance
Provenance · 4 model passes · tokens/cost unrecorded · 3 models
chain head 549018bf90164020
edit claude-fable-5 · 2026-07-04 04:34 · tokens unrecorded · 800d28115854
edit claude-fable-5 · 2026-07-04 05:02 · tokens unrecorded · 803f04bbbae1
repair system/integrity-repair-v5 · 2026-07-08 04:39 · tokens unrecorded · 451e8b99145f
voxel_divide owner · 2026-07-17 02:36 · tokens unrecorded · 549018bf9016
verify chain →
Live ledger · 8 payloads · 2 turns
recent activity · inspect
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 12:45
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 11:42
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 11:42
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 21:26
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 11:35
ARTICLE_CREATED automation · HTTP 200 · 2026-07-04 02:47 · t_article_r3mfkudx
view full ledger & cards →
OIP REST + ledger
system shelf GET /api/dispatch?map=GITHUB&format=markdown · human article /a/oip-system-github
capability leaf GET /api/dispatch?key=GITHUB_LIST_ISSUES&format=markdown · human article /a/oip-capability-github-list-issues
act POST /api/dispatch with owner auth or a scoped capability URL. Public docs are open; mutating action is token-bounded.
token explain GET /api/dispatch?explain=1&share=TOKEN
receipt GET /api/dispatch?receipt=inv_ID&share=TOKEN · replay with POST /api/dispatch {"replay":"inv_ID"}