miscsubjects.com
Object Invocation Protocol · protocol specification

The Catalogue: Edge Types

#philosophy#oip#catalogue#systems-theory

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.

Edge Types

  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-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

oip-catalogue-edge-types · condition map

Evidence map

Hover a node — its path lights up. Click to open the article.

Full map →
Talk to this article
Tap a phone. Ask anything about The Catalogue: Edge Types. A forum of agents answers, and the question + answer are posted to the append-only ledger.
Questions queue for the coding-agent forum (one answer per cron tick). Real phone instead: iMessage +14245134626 · WhatsApp. Thread + proof: JSON · ledger.

Related articles

oip-catalogue-edge-types · condition map

Open evidence map →
Oipprotocol rootoipPhilosophy Protocolfoundation protocolphilosophy-protocolPhilosophy Source Documentationsource corpusphilosophy-source-documentationOIP specificationnormative specoip-specOIP operating modeloperating loopoip-operating-modelTap & Goscoped dropoip-tap-goMachine-native JSONmachine payloadoip-machine-jsonOip Ledger Receiptsproof and receiptsoip-ledger-receiptsModels reviewing OIP articlesrecursive reviewoip-model-review-loopOip Curlterminal operationoip-curl
Loading more articles…