Object Invocation Protocol · protocol specification

Convergence Catalogue: Build Order

Posted Jul 4, 2026 · Updated Jul 17, 2026 · 1 min read

Build Order & Priority Ranking

Appendix A — Build Order & Priority Ranking A.1 Construction Priority The catalogue was built in three priority tiers: Priority Tier 1: The Load-Bearing Spine (C01–C12) Highest convergence, lowest claim tier (T0–T1). These nodes carry the structural load of the graph. Everything else hangs off them. Built first because they are the most defensible and the most cross-referenced. Priority Tier 2: The Bridge Nodes (C13–C19) Connect the spine to the visual pattern layer and to implementation. These are the translation nodes between abstract principle and observable structure. Priority Tier 3: The Boundary Nodes (C20–C25) Mark the edges of what the catalogue can defend. Typed honestly. Some are T3/T4 — they live in the graph as meaning, not proof. A.2 Load-Bearing Subgraph The subgraph that carries the catalogue’s operational claim (the claim that convergence is real and documented) consists of: Core (T0–T1, Convergence ≥ 8.0): C01, C02, C03, C04, C06, C07, C08, C10, C11, C15, C16, C18, C23 Conditional (T2 or Convergence 6.0–7.9): C05, C09, C12, C14, C17, C19, C20, C21, C22 Carried (T3+ or Convergence < 6.0): C13, C24, C25 Nodes C24 and C25 are carried in the graph as instructed by Axiom A2: they are named, typed, visible — never smuggled in as T1. They provide meaning-context but zero structural load. A.3 Node Count by Tier A.4 Domain Coverage

---

Corpus map

Catalogue hub: Convergence Catalogue — Public Article
Nodes: C01 · C02 · C03 · C04 · C05 · C06 · … (25 nodes)
Edge series: Convergence 1 · Disconfirming 1

Key evidence

6 claims · tier-ranked · API

anecdotal

The catalogue was built in three priority tiers.

anecdotal

Priority Tier 1 (Load-Bearing Spine, C01–C12) has highest convergence and lowest claim tier (T0–T1).

anecdotal

Priority Tier 2 (Bridge Nodes, C13–C19) connects the spine to the visual pattern layer and implementation.

anecdotal

Priority Tier 3 (Boundary Nodes, C20–C25) marks the edges of what the catalogue can defend, with some at T3/T4.

anecdotal

The load-bearing subgraph consists of Core nodes (T0–T1, Convergence ≥ 8.0): C01, C02, C03, C04, C06, C07, C08, C10, C11, C15, C16, C18, C23; Conditional nodes (T2 or Convergence 6.0–7.9): C05, C09, C12, C14, C17, C19, C20, C21, C22; Carried nodes (T3+ or Convergence < 6.0): C13, C24, C25.

anecdotal

Nodes C24 and C25 are carried in the graph as instructed by Axiom A2: named, typed, visible, never smuggled in as T1, providing meaning-context but zero structural load.

Model review1 contributions · 1 modelExpand the recursive review layer

1 / 1

grok/grok-4.3atomizer

atomize2026-07-07 08:27

atomize · 6 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-convergence-build-order

it output

{
  "claims": [
    {
      "id": "c1",
      "text": "The catalogue was built in three priority tiers.",
      "section": "## A.1 Construction Priority",
      "tier": "anecdotal",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Defines the overall construction sequence and rationale for node ordering."
    },
    {
      "id": "c2",
      "text": "Priority Tier 1 (Load-Bearing Spine, C01–C12) has highest convergence and lowest claim tier (T0–T1).",
      "section": "## A.1 Construction Priority",
      "tier": "anecdotal",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Specifies the first-built structural core nodes and their properties."
    },
    {
      "id": "c3",
      "text": "Priority Tier 2 (Bridge Nodes, C13–C19) connects the spine to the visual pattern layer and implementation.",
      "section": "## A.1 Construction Priority",
      "tier": "anecdotal",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "Describes the translation nodes between abstract principle and observable structure."
    },
    {
      "id": "c4",
      "text": "Priority Tier 3 (Boundary Nodes, C20–C25) marks the edges of what the catalogue can defend, with some at T3/T4.",
      "section": "## A.1 Construction Priority",
      "tier": "anecdotal",
      "source_ids": [],
      "source_status

27276982b56a0646

Machine verification: /api/articles/oip-convergence-build-order/contributions

Build Order & Priority Ranking

Corpus map

Key evidence

Latest from the journal

Related articles