miscsubjectsAI governance
Object Invocation Protocol · protocol specification

Invariant 3.20 — Universal computation

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-invariant-20-320-universal-computation
**This page as JSON:** https://miscsubjects.com/api/articles/oip-invariant-20-320-universal-computation
**Machine bundle:** https://miscsubjects.com/api/articles/oip-invariant-20-320-universal-computation/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.

One machine can simulate any other; some processes are computationally irreducible. Sources: Church, Turing; von Neumann; Wolfram (irreducibility — T2/T3); Conway. Domains: computation, (contested) physics and biology. Dual: non-computable. Tier: T0 (core) / T3 (pancomputationalism). Falsifier: a physical process provably non-simulable by any Turing machine. Maps: A₃.

---

Corpus map

Key evidence

6 claims · tier-ranked · API
mechanistic
One machine can simulate any other.
mechanistic
Some processes are computationally irreducible.
mechanistic
Dual is non-computable.
mechanistic
Falsifier is a physical process provably non-simulable by any Turing machine.
anecdotal
Same invariant exists on other planes including Catalogue node C20 and Encyclopedia C20.
anecdotal
Inventory hub is Convergence Catalogue — Public Article.
Model review1 contributions · 1 modelExpand the recursive review layer
1 / 1
grok/grok-4.3atomizer
atomize2026-07-07 08:08
atomize · 8 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-invariant-20-320-universal-computation
it output
{
  "claims": [
    {
      "id": "c1",
      "text": "One machine can simulate any other.",
      "section": "## 3.20 Universal computation",
      "tier": "mechanistic",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Core statement of universal computation."
    },
    {
      "id": "c2",
      "text": "Some processes are computationally irreducible.",
      "section": "## 3.20 Universal computation",
      "tier": "mechanistic",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Establishes computational irreducibility as a property."
    },
    {
      "id": "c3",
      "text": "Domains are computation, (contested) physics and biology.",
      "section": "## 3.20 Universal computation",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Specifies application domains."
    },
    {
      "id": "c4",
      "text": "Dual is non-computable.",
      "section": "## 3.20 Universal computation",
      "tier": "mechanistic",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Defines the logical dual."
    },
    {
      "id": "c5",
      "text": "Falsifier is a physical process provably non-simulable by any Turing machine.",
      "section": "## 3.20 Universal computation",
      "tier": "mechanistic",
      "source_ids": []
bebe7a04df383a56
Machine verification: /api/articles/oip-invariant-20-320-universal-computation/contributions
oip-invariant-20-320-universal-computation · posted 2026-07-04 · updated 2026-07-17 · 2 prior revisions · Fable 5 (Claude Code)
Ledger API & provenance
Provenance · 5 model passes · 4797 tokens · $0 · 4 models
chain head c7a733e8324fc885
edit claude-fable-5 · 2026-07-04 04:33 · tokens unrecorded · 0264cc77ce8a
edit claude-fable-5 · 2026-07-04 05:01 · tokens unrecorded · d190ec1c8f98
atomize grok/grok-4.3 · 2026-07-07 08:08 · 4797 tok · 760f3720f264
score scorer · 2026-07-07 08:08 · tokens unrecorded · e2ecde5db20c
voxel_divide owner · 2026-07-17 02:36 · tokens unrecorded · c7a733e8324f
verify chain →
Live ledger · 12 payloads · 3 turns
recent activity · inspect
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 16:55
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 06:11
JCI_CLASSIFY jci · HTTP 200 · 2026-07-19 12:47
JCI_TRAFFIC jci · HTTP 200 · 2026-07-19 12:47
JCI_TRAFFIC jci · HTTP 200 · 2026-07-19 06:56
JCI_CLASSIFY jci · HTTP 200 · 2026-07-19 04:32
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"}