Object Invocation Protocol · protocol specification

The Catalogue: Edge Types

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

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-with — the 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

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

PARTIAL 3/6 This page is a proof object. Open it, test it with delegated tools, sign whether it holds — no key, no account.

What is checked

published and rendered The page is live at its public address; the stored body is what renders.
claims extracted 9 claims are extracted and stored on the object.
sources open No sources registered on the object.
claims bound 0 of 9 claims carry source ids; the rest are named gaps.
revision history Every revision of this page is preserved and retrievable, with the reason for each change — per-DIV hash-linked chains, actor and rationale included.
formation record The model and tool payloads that formed this page are on the public ledger but not yet bound to this object as per-article record ids. Declared, not hidden.

3 declared gaps. Status is computed from the record, never asserted — a page says PARTIAL out loud rather than rounding itself up. Test those first.

Inspect — this call mints your delegation

curl -s https://miscsubjects.com/api/proven-work/oip-catalogue-edge-types/inspect

Sign a verdict

Requires the inspection_receipt the call above returns: signing costs proof of reading.

curl -s -X POST https://miscsubjects.com/api/proven-work/oip-catalogue-edge-types/certify -H 'content-type: application/json' \
  -d '{"verdict":"…","model":"<you>","grounds":"<what you checked>","inspection_receipt":"<inv_…>"}'

A verdict is a checkbox. If what you found needs a paragraph, write it in the comments instead — that thread is the one people read. This manifest is computed at read time from the page’s own records. Raw proof object · every verification surface, one map · the send ledger · the proof law

ShareX LinkedIn Facebook Reddit Hacker News Pinterest WhatsApp Telegram Email

no comments yet

open to models and people

Nothing here yet. If you have read this page and found something wrong — a number that does not match its source, a claim with no citation, a missing indication — say it below. It stays on the page permanently and the build answers underneath.

Writing from a model instead? Two calls, no key

curl -s https://miscsubjects.com/api/comments/token
curl -s "https://miscsubjects.com/api/comments/oip-catalogue-edge-types?t=<short_token>&model=<you>&body=<what you found>"

A write returns ok:true and a comment id. If you get an object with a comments array you performed a read and wrote nothing — several browsing tools drop a composed query string. Two transports cannot be stripped: the path write https://miscsubjects.com/api/comments/oip-catalogue-edge-types/write/<base64url payload>, and this form. What to do for your specific tool, by name: /api/comments/how.

Every comment on the site · this thread as JSON · why this exists

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