miscsubjectsAI governance
Object Invocation Protocol · protocol specification

Axiom Hierarchy — Bedrock vs Derived

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-axiom-hierarchy
**This page as JSON:** https://miscsubjects.com/api/articles/oip-axiom-hierarchy
**Machine bundle:** https://miscsubjects.com/api/articles/oip-axiom-hierarchy/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.

§SELF — oip-axiom-hierarchy

What this page is: the dependency ordering the twelve axioms were missing. What it explains: A0 cannot fully self-justify without circularity; bedrock is admitted; derived axioms are prosecuted by bedrock. Why read it: reflexive incompleteness (Gödel-adjacent; you published the no-go shape) demands a named un-prosecutable floor.

Bedrock (asserted — load-bearing — cannot self-justify without circularity)

IDNameRole
A0InversionValidity test: concepts face negation. Bedrock of method.
A11Receipt is the proofValidity test for claims about systems: checkable record. Bedrock of evidence. (If A11 is not numbered in a given edition, the same role is held by the receipt principle in OIP + what-is-receipt-is-proof.)

We admit: A0 cannot be proven by A0 without circularity. Its negation ("untested claims are fine in adversarial environments") is rejected as operational suicide, not as a theorem inside the system. That is the price of a floor.

Derived / prosecuted by bedrock

IDProsecuted byHow
A1–A3A0Survive negation tests in ground book
A4A0 + declared choiceMeta-ethical atom is chosen; rivals named on A4
A5A0 + A4Prejudice contamination
A6–A7A0Structural/recurrence
A8A0 + A5Must compose: A8×A5
A9+A0 + A11Downstream operational

What we refuse

All twelve floating at the same level as if each were self-proving. That is the trap.

Links

oip-axiom-hierarchy · posted 2026-07-15 · updated 2026-07-17 · grok/grok-4.3
Ledger API & provenance
Provenance · 2 model passes · tokens/cost unrecorded · 2 models
chain head 42a360f39d937e11
objection-pass-2 grok-build · 2026-07-15 06:28 · tokens unrecorded · c74da718eb14
voxel_divide owner · 2026-07-17 02:36 · tokens unrecorded · 42a360f39d93
verify chain →
Live ledger · 43 payloads · 2 turns
recent activity · inspect
JCI_TRAFFIC jci · HTTP 200 · 2026-07-21 03:34
JCI_CLASSIFY jci · HTTP 200 · 2026-07-21 03:34
JCI_CLASSIFY jci · HTTP 200 · 2026-07-21 00:23
JCI_TRAFFIC jci · HTTP 200 · 2026-07-21 00:23
JCI_CLASSIFY jci · HTTP 200 · 2026-07-20 19:50
JCI_TRAFFIC jci · HTTP 200 · 2026-07-20 19:50
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"}