miscsubjectsAI governance
Object Invocation Protocol · protocol specification

The Catalogue: Build Order

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-catalogue-build-order
**This page as JSON:** https://miscsubjects.com/api/articles/oip-catalogue-build-order
**Machine bundle:** https://miscsubjects.com/api/articles/oip-catalogue-build-order/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.
  1. Build order — the priority twelve

Highest convergence, lowest tier, touch every domain. Build these voxels first; everything else hangs off them:

  1. Gradient dissipation (§3.1)
  2. Least action (§3.2)
  3. Symmetry ↔ breaking (§3.3–3.4)
  4. Criticality / power laws (§3.5)
  5. Information / compression / Landauer (§3.10)
  6. Feedback / cybernetics (§3.7)
  7. Recursion / self-reference (§3.9)
  8. Selection / Price equation (§3.12)
  9. Networks (§3.16)
  10. Autopoiesis (§3.8)
  11. Free energy / prediction (§3.11)
  12. Duality / complementarity (§3.14)

---

End v1. Tier honestly, source everything, keep the contradicts edges live, point the review loop at disconfirmation. Convergence between your first-principles derivations and these independent ones is your A₇ signal — and where they diverge is the finding, not the failure.

---

Corpus map

Key evidence

0 claims · tier-ranked · API
Model review1 contributions · 1 modelExpand the recursive review layer
1 / 1
grok/grok-4.3atomizer
atomize2026-07-07 08:31
atomize · 3 claims
inspect — what it was prompted & output
prompted with
You are the claim atomizer for the miscsubjects.com philosophy and OIP corpus. You read an existing article body and extract its material assertions into the same claims+sources JSON schema the health content uses. The body is read-only input.

ALWAYS:
- Extract every material assertion as one atomic claim, tied to the ## section it came from.
- Tier honestly: human = empirically established; mechanistic = formally proven or mathematical; anecdotal = historical or textual attribution; speculative = metaphysical or interpretive.
- Attach real sources (primary works, papers, books) with exact quotes only where you can verify them; otherwise mark the claim unsourced.
- Prefer fewer, harder claims over many soft ones.

NEVER:
- Never rewrite, summarize, or output the body.
- Never invent a URL, quote, or publication.
- Never duplicate an existing claim text.

input: atomize oip-catalogue-build-order
it output
{
  "claims": [
    {
      "id": "c1",
      "text": "The priority twelve build order consists of gradient dissipation, least action, symmetry breaking, criticality / power laws, information / compression / Landauer, feedback / cybernetics, recursion / self-reference, selection / Price equation, networks, autopoiesis, free energy / prediction, and duality / complementarity.",
      "section": "# Build Order",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Defines the exact sequence of foundational concepts asserted as highest convergence and lowest tier."
    },
    {
      "id": "c2",
      "text": "These twelve items must be built first as voxels, with everything else hanging off them.",
      "section": "# Build Order",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "States the asserted construction priority and dependency structure."
    },
    {
      "id": "c3",
      "text": "The corpus map includes a catalogue hub, 25 nodes such as C01 through C06, and edge series including Convergence 1 and Disconfirming 1.",
      "section": "## Corpus map",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Enumerates the asserted structure of the convergence catalogue."
    }
  ],
  "sources": [
9e8531560191fceb
Machine verification: /api/articles/oip-catalogue-build-order/contributions
oip-catalogue-build-order · posted 2026-07-04 · updated 2026-07-17 · 3 prior revisions · Fable 5 (Claude Code)
Ledger API & provenance
Provenance · 5 model passes · 4324 tokens · $0 · 4 models
chain head d2333063faad7629
edit claude-fable-5 · 2026-07-04 04:33 · tokens unrecorded · 3c08969e27c3
edit claude-fable-5 · 2026-07-04 05:01 · tokens unrecorded · eed3a6b95c6a
atomize grok/grok-4.3 · 2026-07-07 08:31 · 4324 tok · d7eccf0171be
score scorer · 2026-07-07 08:31 · tokens unrecorded · 8e3beb6da5b2
voxel_divide owner · 2026-07-17 02:36 · tokens unrecorded · d2333063faad
verify chain →
Live ledger · 26 payloads · 3 turns
recent activity · inspect
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 10:09
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 23:40
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 22:31
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 22:12
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 20:42
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 15:00
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"}