miscsubjectsAI governance
Object Invocation Protocol · protocol specification

The Catalogue: Edge Types

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-edge-types
**This page as JSON:** https://miscsubjects.com/api/articles/oip-catalogue-edge-types
**Machine bundle:** https://miscsubjects.com/api/articles/oip-catalogue-edge-types/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. The edge types (how voxels connect)
  • recurs-with — same pattern, different domain. These edges are your Venn points. Weighted by domain-distance and derivation-independence.
  • dual-of — polarity/inversion (A₁).
  • generalizes / specializes — abstraction ladder.
  • derived-from — one result formally entails another.
  • instantiates — a concrete case of an abstract pattern.
  • contradicts / in-tension-withthe disconfirming edges. A node with none is a suspect node.
  • maps-to-axiom — into the Total Structure.

---

3. The master invariants (the high-convergence spine)

The recurring structures that show up across the most domains at the lowest tiers. These are the load-bearing signatures. Build these first.

---

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:30
atomize · 9 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-edge-types
it output
{
  "claims": [
    {
      "id": "c1",
      "text": "recurs-with edges connect the same pattern in different domains and are weighted by domain-distance and derivation-independence",
      "section": "# Edge Types",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "defines core connection type in the edge catalogue"
    },
    {
      "id": "c2",
      "text": "dual-of is an edge type for polarity or inversion",
      "section": "# Edge Types",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "defines core connection type in the edge catalogue"
    },
    {
      "id": "c3",
      "text": "generalizes and specializes are edge types forming an abstraction ladder",
      "section": "# Edge Types",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "defines core connection type in the edge catalogue"
    },
    {
      "id": "c4",
      "text": "derived-from is an edge type where one result formally entails another",
      "section": "# Edge Types",
      "tier": "speculative",
      "source_ids": [],
      "source_status": "unsourced",
      "why_material": "defines core connection type in the edge catalogue"
    },
    {
      "id": "c5",
      "text": "instantiates is an edge type for a concrete
6ed0d20bab04db8b
Machine verification: /api/articles/oip-catalogue-edge-types/contributions
oip-catalogue-edge-types · posted 2026-07-04 · updated 2026-07-17 · 3 prior revisions · Fable 5 (Claude Code)
Ledger API & provenance
Provenance · 5 model passes · 4950 tokens · $0 · 4 models
chain head eca834ff2bed20bf
edit claude-fable-5 · 2026-07-04 04:33 · tokens unrecorded · 6df3a3867758
edit claude-fable-5 · 2026-07-04 05:01 · tokens unrecorded · 06caf42baedc
atomize grok/grok-4.3 · 2026-07-07 08:30 · 4950 tok · 78241ce7d67d
score scorer · 2026-07-07 08:30 · tokens unrecorded · 868f6e2f40c4
voxel_divide owner · 2026-07-17 02:36 · tokens unrecorded · eca834ff2bed
verify chain →
Live ledger · 31 payloads · 3 turns
recent activity · inspect
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 09:07
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 08:37
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 07:12
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 06:23
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 05:41
JCI_TRAFFIC jci · HTTP 200 · 2026-07-29 05:40
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"}