## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `what-is-convergence-catalogue`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/what-is-convergence-catalogue/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/what-is-convergence-catalogue/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/what-is-convergence-catalogue/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/what-is-convergence-catalogue/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/what-is-convergence-catalogue/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/what-is-convergence-catalogue/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## Article
- **slug:** `what-is-convergence-catalogue`
- **title:** What Is a Convergence Catalogue
- **url:** https://miscsubjects.com/a/what-is-convergence-catalogue
- **register:** standard
- **updated:** 2026-07-15T04:20:55.154Z
- **tags:** oip, kimi-import, self-explaining, voxel, concepts, what-is-convergence-catalogue

## Body

<!-- hierarchy:nav -->
> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Protocol Concepts](https://miscsubjects.com/a/oip-protocol-concepts) › **What Is a Convergence Catalogue**
>
> **Shelf:** Protocol Concepts · **Traversal:** self-explaining · hierarchical · voxel-ready
> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)

# What Is a Convergence Catalogue

## §SELF — what-is-convergence-catalogue

**What this page is:** A definition of the convergence catalogue framework for identifying agreements across independent knowledge domains.
**What it explains:** How a convergence catalogue selects and organizes claims that have been independently derived in multiple fields, and why this structure matters.
**Why read it:** You will understand what convergent evidence looks like in structured form, what criteria qualify a claim for inclusion, and why this framework supports the philosophical foundation of OIP.

### What a Convergence Catalogue Is

A convergence catalogue is a framework that collects claims from multiple independent domains and evaluates whether they point at the same underlying structure. Each claim in the catalogue is called a "node." The catalogue is not a theory of everything; it is a map of where independent theories agree.

### Why It Matters

If one field of study produces a claim, that claim might be an artifact of that field's methods or assumptions. If two independent fields produce the same claim, coincidence becomes less likely. If three or more independent fields produce the same claim — using different methods, different assumptions, and different vocabularies — the claim is likely describing something real about the world, not just something convenient for a single discipline. A convergence catalogue makes this agreement visible and verifiable.

### The Key Idea

A node is admitted to the catalogue only if it satisfies three criteria:

1. **Independent derivation in at least two domains.** The same claim must have been reached by researchers working in different fields, using different methods, without collaboration or shared assumptions.
2. **Falsifiable prediction.** The claim must imply a test that could prove it wrong. A claim that cannot be tested does not qualify.
3. **Named rival explanation tested and found wanting.** There must be at least one alternative explanation for the same phenomenon that has been proposed and rejected on empirical grounds.

An example of a node: **C01 — Gradient Dissipation.** The claim is: sustained order exists only by consuming a gradient (a difference in potential, such as temperature or concentration). This claim has been derived independently by:

- Ilya Prigogine (physics, 1967) — from studies of Bénard cells and non-equilibrium thermodynamics.
- Erwin Schrödinger (biology, 1944) — from the question "What is Life?" and the observation that living systems feed on negative entropy.
- Jeremy England (physics, 2013) — from the MIT driven matter theorem showing that matter under external driving spontaneously arranges to dissipate energy.

Three independent derivations. Three different domains. Same underlying principle.

The catalogue contains 25 such nodes spanning physics, biology, economics, mathematics, philosophy, computer science, and systems theory.

### What It Got Right

- **Structured independence check.** The requirement for cross-domain derivation prevents field-specific bias from masquerading as universal truth.
- **Falsifiability as a filter.** Requiring a testable prediction excludes unfalsifiable claims, keeping the catalogue grounded in empirical content.
- **Rival exclusion.** Requiring that a named alternative has been tested and rejected strengthens each node's standing — the claim has survived competition.
- **Replicable method.** Anyone can apply the three criteria to evaluate a new candidate node. The selection process is transparent and repeatable.

### What It Got Wrong or Left Unfinished

- **Does not quantify convergence strength.** Two domains agreeing is treated similarly to six domains agreeing. There is no weighting system.
- **Domain boundaries are fuzzy.** "Independent domain" is defined by the community of practice, not by a formal criterion. Two subfields of physics might be more independent than physics and systems theory.
- **No formal update mechanism.** The catalogue does not specify how nodes are revised or removed when new evidence contradicts them.
- **25 nodes is a starting point, not a ceiling.** The catalogue is incomplete. Many potential nodes have not yet been evaluated.

### How It Connects to Other Ideas

**Consilience.** Consilience (from the Latin *consilientia*, "jumping together") is the principle that evidence from independent sources converges on the same conclusion. E.O. Wilson's 1998 book *Consilience* argued for unity of knowledge across disciplines. The convergence catalogue operationalizes this principle with explicit criteria.

**Interdisciplinary validation.** Science typically validates claims within a single field. The convergence catalogue treats cross-field agreement as an additional validation signal — one that is harder to fake because it requires expertise in multiple domains.

**OIP philosophical foundation.** OIP (the Open Interface Protocol) structures software invocations as reproducible, auditable events. The convergence catalogue provides the philosophical argument for why this structure matters: if 25 independent derivations from physics, biology, economics, and other fields all point at the same underlying pattern — that order arises from constraint, gradients drive structure, and systems that preserve information about their environment persist — then the pattern is likely real. OIP embodies this by making every invocation a constrained, gradient-driven, information-preserving event that can be independently verified.

### Sources

- Prigogine, I. (1967). *Introduction to Thermodynamics of Irreversible Processes*. Interscience Publishers.
- Schrödinger, E. (1944). *What is Life? The Physical Aspect of the Living Cell*. Cambridge University Press.
- England, J.L. (2013). "Statistical Physics of Self-Replication." *Journal of Chemical Physics*, 139, 121923.
- Wilson, E.O. (1998). *Consilience: The Unity of Knowledge*. Alfred A. Knopf.

---

## Up the tree

- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry
- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map
- [Protocol Concepts shelf](https://miscsubjects.com/a/oip-protocol-concepts) — siblings on this shelf
- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels
- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)

## Related on this shelf

- [What Is Autopoiesis](https://miscsubjects.com/a/what-is-autopoiesis)
- [What Is Capability-Based Security](https://miscsubjects.com/a/what-is-capability-security)
- [What Is a Capability Token](https://miscsubjects.com/a/what-is-capability-token)
- [What Is a Confused Deputy](https://miscsubjects.com/a/what-is-confused-deputy)
- [What Is Context as Cursor](https://miscsubjects.com/a/what-is-context-as-cursor)
- [What Is a Falsification Surface](https://miscsubjects.com/a/what-is-falsification-surface)
- [What Is HATEOAS](https://miscsubjects.com/a/what-is-hateoas)
- [What Is the History of Link Protocols](https://miscsubjects.com/a/what-is-link-protocol-history)

## Machine surfaces

- Public page: `https://miscsubjects.com/a/what-is-convergence-catalogue`
- JSON article: `https://miscsubjects.com/api/articles/what-is-convergence-catalogue`
- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20a%20Convergence%20Catalogue`


## Claims (0)


## Voxel graph (0 atoms · 0 edges)
- full graph: https://miscsubjects.com/api/articles/what-is-convergence-catalogue/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (0)
- chain valid: yes · head: `genesis`

## Provenance (1 model passes)
- chain valid: yes · head: `dde30bb4c62e1711`

- write · kimi-agent-import · 2026-07-15T04:20 · hash `dde30bb4c62e`

## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/what-is-convergence-catalogue/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/what-is-convergence-catalogue/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"what-is-convergence-catalogue","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest what-is-convergence-catalogue|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim what-is-convergence-catalogue|tier|assertion`
- **iMessage ask:** `what-is-convergence-catalogue|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `what-is-convergence-catalogue`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/what-is-convergence-catalogue/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/what-is-convergence-catalogue/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*