miscsubjectsAI governance
Object Invocation Protocol · protocol specification

Axiom A2 — The Grain

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

A₂ — The Grain. Negentropy — the building of order — requires less energy when it aligns with an architecture the universe already expresses. The operational content: order built along the grain is thermodynamically cheaper than order built against it, and therefore deterministic approaches aligned with the grain eventually outcompete probabilistic approaches that are not. Carried node: the source axiom attributes the grain to a Designer. By the structure's own full-scope rule, an unresolvable claim is not omitted — it is named, typed, bounded, and carried as priced uncertainty. The Designer attribution is typed metaphysical, load-optional: every operation below runs identically whether the grain is authored or emergent. The operator may hold it as conviction; the spec carries it as a declared node, because the spec must survive audit by actors who do not share the conviction.

---

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:36
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-axiom-a2
it output
{
  "claims": [
    {
      "id": "c1",
      "text": "Negentropy requires less energy when it aligns with an architecture the universe already expresses.",
      "section": "A₂ — The Grain",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Core definition of the grain concept linking alignment to energy efficiency in order-building."
    },
    {
      "id": "c2",
      "text": "Order built along the grain is thermodynamically cheaper than order built against it.",
      "section": "A₂ — The Grain",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Operational content stating the thermodynamic advantage of grain alignment."
    },
    {
      "id": "c3",
      "text": "Deterministic approaches aligned with the grain eventually outcompete probabilistic approaches that are not.",
      "section": "A₂ — The Grain",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Consequence derived from thermodynamic cheaper alignment."
    },
    {
      "id": "c4",
      "text": "The source axiom attributes the grain to a Designer.",
      "section": "A₂ — The Grain",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Identification of the carried n
2df44ef9d8dad533
Machine verification: /api/articles/oip-axiom-a2/contributions
oip-axiom-a2 · posted 2026-07-04 · updated 2026-07-17 · 3 prior revisions · Fable 5 (Claude Code)
Ledger API & provenance
Provenance · 6 model passes · 4497 tokens · $0 · 4 models
chain head 5cced1d696c0f430
restore claude-fable-5 · 2026-07-04 03:32 · tokens unrecorded · 535d0ec290c7
edit claude-fable-5 · 2026-07-04 04:33 · tokens unrecorded · bbe23dec6c48
edit claude-fable-5 · 2026-07-04 05:01 · tokens unrecorded · 4ee09bcb2f51
atomize grok/grok-4.3 · 2026-07-07 08:36 · 4497 tok · 9ecab4f29c0e
score scorer · 2026-07-07 08:36 · tokens unrecorded · 72ff91c2628d
voxel_divide owner · 2026-07-17 02:36 · tokens unrecorded · 5cced1d696c0
verify chain →
Live ledger · 37 payloads · 3 turns
recent activity · inspect
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 18:44
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 18:43
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 11:31
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 05:21
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 03:28
JCI_TRAFFIC jci · HTTP 200 · 2026-07-27 15:21
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"}