{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"what-is-convergence-catalogue","title":"What Is a Convergence Catalogue","body":"<!-- hierarchy:nav -->\n> **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**\n>\n> **Shelf:** Protocol Concepts · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# What Is a Convergence Catalogue\n\n## §SELF — what-is-convergence-catalogue\n\n**What this page is:** A definition of the convergence catalogue framework for identifying agreements across independent knowledge domains.\n**What it explains:** How a convergence catalogue selects and organizes claims that have been independently derived in multiple fields, and why this structure matters.\n**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.\n\n### What a Convergence Catalogue Is\n\nA 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.\n\n### Why It Matters\n\nIf 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.\n\n### The Key Idea\n\nA node is admitted to the catalogue only if it satisfies three criteria:\n\n1. **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.\n2. **Falsifiable prediction.** The claim must imply a test that could prove it wrong. A claim that cannot be tested does not qualify.\n3. **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.\n\nAn 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:\n\n- Ilya Prigogine (physics, 1967) — from studies of Bénard cells and non-equilibrium thermodynamics.\n- Erwin Schrödinger (biology, 1944) — from the question \"What is Life?\" and the observation that living systems feed on negative entropy.\n- Jeremy England (physics, 2013) — from the MIT driven matter theorem showing that matter under external driving spontaneously arranges to dissipate energy.\n\nThree independent derivations. Three different domains. Same underlying principle.\n\nThe catalogue contains 25 such nodes spanning physics, biology, economics, mathematics, philosophy, computer science, and systems theory.\n\n### What It Got Right\n\n- **Structured independence check.** The requirement for cross-domain derivation prevents field-specific bias from masquerading as universal truth.\n- **Falsifiability as a filter.** Requiring a testable prediction excludes unfalsifiable claims, keeping the catalogue grounded in empirical content.\n- **Rival exclusion.** Requiring that a named alternative has been tested and rejected strengthens each node's standing — the claim has survived competition.\n- **Replicable method.** Anyone can apply the three criteria to evaluate a new candidate node. The selection process is transparent and repeatable.\n\n### What It Got Wrong or Left Unfinished\n\n- **Does not quantify convergence strength.** Two domains agreeing is treated similarly to six domains agreeing. There is no weighting system.\n- **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.\n- **No formal update mechanism.** The catalogue does not specify how nodes are revised or removed when new evidence contradicts them.\n- **25 nodes is a starting point, not a ceiling.** The catalogue is incomplete. Many potential nodes have not yet been evaluated.\n\n### How It Connects to Other Ideas\n\n**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.\n\n**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.\n\n**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.\n\n### Sources\n\n- Prigogine, I. (1967). *Introduction to Thermodynamics of Irreversible Processes*. Interscience Publishers.\n- Schrödinger, E. (1944). *What is Life? The Physical Aspect of the Living Cell*. Cambridge University Press.\n- England, J.L. (2013). \"Statistical Physics of Self-Replication.\" *Journal of Chemical Physics*, 139, 121923.\n- Wilson, E.O. (1998). *Consilience: The Unity of Knowledge*. Alfred A. Knopf.\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [Protocol Concepts shelf](https://miscsubjects.com/a/oip-protocol-concepts) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [What Is Autopoiesis](https://miscsubjects.com/a/what-is-autopoiesis)\n- [What Is Capability-Based Security](https://miscsubjects.com/a/what-is-capability-security)\n- [What Is a Capability Token](https://miscsubjects.com/a/what-is-capability-token)\n- [What Is a Confused Deputy](https://miscsubjects.com/a/what-is-confused-deputy)\n- [What Is Context as Cursor](https://miscsubjects.com/a/what-is-context-as-cursor)\n- [What Is a Falsification Surface](https://miscsubjects.com/a/what-is-falsification-surface)\n- [What Is HATEOAS](https://miscsubjects.com/a/what-is-hateoas)\n- [What Is the History of Link Protocols](https://miscsubjects.com/a/what-is-link-protocol-history)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/what-is-convergence-catalogue`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-convergence-catalogue`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20a%20Convergence%20Catalogue`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-convergence-catalogue"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-convergence-catalogue/ledger","live":true},"embeds":[],"widgets":[{"type":"note","title":"Zero-context","text":"This page is self-explaining: §SELF states what it is, what it explains, and why to read it."},{"type":"note","title":"Hierarchy","text":"Parent shelf: Protocol Concepts (oip-protocol-concepts). Hub: oip-thinker-reference. Root: /a/oip."},{"type":"note","title":"Voxel","text":"Each article is a node. Links Up the tree + Related form the traversable graph."},{"type":"stat","value":20,"label":"Protocol Concepts on shelf"}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:55.154Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"dde30bb4c62e1711ce1c63434ef09303975f658f401c9f4eb8ad9a1568de8ec5"},{"ts":"2026-07-17T02:43:37.460Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-convergence-catalogue","response":"33 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"dde30bb4c62e1711ce1c63434ef09303975f658f401c9f4eb8ad9a1568de8ec5","hash":"611893477fb6cb5c5fe30d5e502ca308983c3261af7840bd6806d93ef8a5523e"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"611893477fb6cb5c5fe30d5e502ca308983c3261af7840bd6806d93ef8a5523e"},"posted_at":"2026-07-15T04:20:55.154Z","created_at":"2026-07-15T04:20:55.154Z","updated_at":"2026-07-17T02:43:37.460Z","machine":{"shape":"article.machine/v1","slug":"what-is-convergence-catalogue","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-convergence-catalogue","json":"https://miscsubjects.com/api/articles/what-is-convergence-catalogue","bundle":"https://miscsubjects.com/api/articles/what-is-convergence-catalogue/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/what-is-convergence-catalogue/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-convergence-catalogue","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"what-is-convergence-catalogue\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"what-is-convergence-catalogue\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/what-is-convergence-catalogue/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"what-is-convergence-catalogue\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-convergence-catalogue | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-convergence-catalogue","json":"/api/articles/what-is-convergence-catalogue","markdown":"/api/articles/what-is-convergence-catalogue/bundle?format=markdown","skill":"/api/articles/what-is-convergence-catalogue/skill","topology":"/api/articles/what-is-convergence-catalogue/topology","versions":"/api/articles/what-is-convergence-catalogue/revisions","invocations":"/api/articles/what-is-convergence-catalogue/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-convergence-catalogue","ok":false,"issues":[{"code":"heading_filing_label","message":"section heading “Why It Matters” is a filing label that gives a cold reader no claim","replacement":"Replace “Why It Matters” with the concrete claim, event, or object introduced in that section."},{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"189ab7a77ae8efd09aab6765560bdfadce32ec00197a9b6357fd615a18c69d9f","object":{"object_type":"article-object","identity":{"id":"article:what-is-convergence-catalogue","slug":"what-is-convergence-catalogue","title":"What Is a Convergence Catalogue"},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/what-is-convergence-catalogue","role":"explain","audience":"human"},"skill":{"route":"/api/articles/what-is-convergence-catalogue/skill","role":"direct behavior","audience":"model","content":"---\nname: what-is-convergence-catalogue\ndescription: Apply the What Is a Convergence Catalogue article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# What Is a Convergence Catalogue\n\nThis Skill is the behavioral expression of [the canonical article](/a/what-is-convergence-catalogue). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/what-is-convergence-catalogue.\n- Read claims and relationships at /api/articles/what-is-convergence-catalogue/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\n<!-- 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\n\n## Representations\n\n- Human: /a/what-is-convergence-catalogue\n- JSON: /api/articles/what-is-convergence-catalogue\n- Relationships: /api/articles/what-is-convergence-catalogue/topology\n- History: /api/articles/what-is-convergence-catalogue/revisions\n"},"json":{"route":"/api/articles/what-is-convergence-catalogue","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/what-is-convergence-catalogue/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"OIP_TREE","type":"http","method":"GET","category":"oip","enabled":true,"contract":"# WHAT: Return the recursive Object Invocation Protocol tree: root documents, API/CLI/MCP/device/model/core shelves, generated system articles, generated capability articles, ledgers, receipts, replay, repair, and token explanation surfaces.\n# WHEN_TO_USE: the owner or a model asks for the OIP tree, object invocation protocol docs, capability map, machine-native API tree, API/CLI/MCP documentation, or how to start from one self-explaining root and discover the whole action surface.\n# ARGS: none\n# EX: [OIP_TREE][/OIP_TREE]","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_TREE","json":"/api/directory/OIP_TREE","skill":"/api/directory/OIP_TREE?format=skill","oip_contract":"/api/dispatch?key=OIP_TREE"}},{"key":"ARXIV_GROW","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Regenerate the arXiv paper from live state. Reads paper/template.tex + paper/rings.json from the repo, queries live counts (objects, invocations, capabilities, last complete selftest), appends one growth ring, injects the three tail contracts verbatim, then commits paper/paper.tex + paper/rings.json + README.md + oip.json — each commit message carries this trace id. CI compiles the PDF on the paper.tex push. This fn is the only writer of the generated files.\n# WHEN_TO_USE: the owner says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.the owner.oip.arxiv-grow on the Mac.\n# ARGS: none.\n# EX: [ARXIV_GROW][/ARXIV_GROW]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_GROW","json":"/api/directory/ARXIV_GROW","skill":"/api/directory/ARXIV_GROW?format=skill","oip_contract":"/api/dispatch?key=ARXIV_GROW"}},{"key":"ARXIV_PAPER","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The arXiv paper as a live object. The paper \"The Document Is the Receipt\" lives at github.com/[OWNER_HANDLE]/oip (private) and is written only by ARXIV_GROW. Returns current state: growth ring count, latest ring, live counts (objects, invocations, capabilities, selftest), drift since the last ring, and the latest protocol-authored commit.\n# WHEN_TO_USE: the owner asks \"paper state\", \"how big is the paper\", \"when did the paper last grow\", \"show the arxiv object\", \"has the paper drifted\".\n# ARGS: none.\n# EX: [ARXIV_PAPER][/ARXIV_PAPER]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_PAPER","json":"/api/directory/ARXIV_PAPER","skill":"/api/directory/ARXIV_PAPER?format=skill","oip_contract":"/api/dispatch?key=ARXIV_PAPER"}},{"key":"CAP_MINT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Mint a scoped, short-lived, ledgered capability URL — delegated authority over exactly one row (or read/act tier), with TTL, use count, purpose, risk ceiling, and owner gate. Returns invoke_url + explain_url + fingerprint; the URL explains itself.\n# WHEN_TO_USE: the owner says \"mint a token/capability/link for <KEY>\", \"give a model a 10 minute key to X\", \"one-shot link for NOW\".\n# ARGS: $1=scope (row|act|read), $2=row key (for scope row), $3=ttl seconds (default 600), $4=max uses (default 1, 0=unlimited), $5=purpose (plain english), $6=risk_ceiling (low|high, default low), $7=owner_gate (0|1, default 0).\n# EX: [CAP_MINT]row|NOW|600|1|demo for chatgpt[/CAP_MINT]\n[\"$1\",\"$2\",\"$3\",\"$4\",\"$5\",\"$6\",\"$7\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_MINT","json":"/api/directory/CAP_MINT","skill":"/api/directory/CAP_MINT?format=skill","oip_contract":"/api/dispatch?key=CAP_MINT"}},{"key":"GITHUB_TAIL","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The GitHub repository as a live object. Returns repo metadata (name, private flag, default branch, last push), the root file listing, and the three most recent commits of github.com/[OWNER_HANDLE]/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: the owner asks \"show the repo\", \"github tail\", \"what is in the oip repo\", \"last repo commit\", \"is the repo still private\".\n# ARGS: none.\n# EX: [GITHUB_TAIL][/GITHUB_TAIL]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/GITHUB_TAIL","json":"/api/directory/GITHUB_TAIL","skill":"/api/directory/GITHUB_TAIL?format=skill","oip_contract":"/api/dispatch?key=GITHUB_TAIL"}},{"key":"OIP_RECEIPT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Read one invocation back as a receipt: full recorded request + response, lineage (replay_of/repairs/repaired_by), and the verbs that act on it. A receipt is a live replayable object, not history.\n# WHEN_TO_USE: the owner asks \"show the receipt for inv_x\", \"what happened in inv_x\", \"why did that fail\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_RECEIPT]inv_wvitbmiym6[/OIP_RECEIPT]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_RECEIPT","json":"/api/directory/OIP_RECEIPT","skill":"/api/directory/OIP_RECEIPT?format=skill","oip_contract":"/api/dispatch?key=OIP_RECEIPT"}},{"key":"OIP_REPAIR","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Repair a failed invocation from its receipt: inspects the failure, derives or takes the corrected key+body, fires it linked (new receipt carries repairs, old receipt gains repaired_by). Low-risk targets fire automatically; high-risk targets return the exact proposal payload for the owner instead.\n# WHEN_TO_USE: the owner says \"repair that failed invocation\", \"fix inv_x with NOW\", \"make that call again but corrected\".\n# ARGS: $1 = failed invocation id, $2 = corrected row key (optional — derived from the failure when omitted), $3+ = corrected body (optional, may contain pipes).\n# EX: [OIP_REPAIR]inv_6ximjestte|NOW|[/OIP_REPAIR]\n[\"$1\",\"$2\",\"$3+\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPAIR","json":"/api/directory/OIP_REPAIR","skill":"/api/directory/OIP_REPAIR?format=skill","oip_contract":"/api/dispatch?key=OIP_REPAIR"}},{"key":"OIP_REPLAY","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Re-fire a past invocation with its recorded input. New receipt links replay_of to the old one.\n# WHEN_TO_USE: the owner says \"replay that\", \"run inv_x again\", \"re-fire it as it was\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_REPLAY]inv_wvitbmiym6[/OIP_REPLAY]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPLAY","json":"/api/directory/OIP_REPLAY","skill":"/api/directory/OIP_REPLAY?format=skill","oip_contract":"/api/dispatch?key=OIP_REPLAY"}},{"key":"CAP_EXPLAIN","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Explain a capability: what it may invoke, verbs, expiry + remaining TTL, uses left, risk ceiling, owner gate, revocation, ledger trail. Accepts the token itself (sh.…) or its fingerprint (cap_…). Never echoes the raw token.\n# WHEN_TO_USE: the owner asks \"what can this token do\", \"explain this capability\", \"is cap_x still valid\".\n# ARGS: $1 = capability token or cap_ fingerprint.\n# EX: [CAP_EXPLAIN]cap_1a2b3c4d5e6f7a8b[/CAP_EXPLAIN]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_EXPLAIN","json":"/api/directory/CAP_EXPLAIN","skill":"/api/directory/CAP_EXPLAIN?format=skill","oip_contract":"/api/dispatch?key=CAP_EXPLAIN"}},{"key":"CAP_REVOKE","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Revoke a capability by fingerprint — the URL dies immediately; further invokes are denied and ledgered.\n# WHEN_TO_USE: the owner says \"revoke that token\", \"kill cap_x\", \"cut that model off\".\n# ARGS: $1 = cap_ fingerprint.\n# EX: [CAP_REVOKE]cap_1a2b3c4d5e6f7a8b[/CAP_REVOKE]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_REVOKE","json":"/api/directory/CAP_REVOKE","skill":"/api/directory/CAP_REVOKE?format=skill","oip_contract":"/api/dispatch?key=CAP_REVOKE"}}]},"ontology":{"conformance_group":"article","inferred_from":["oip","kimi-import","self-explaining","voxel","concepts","what-is-convergence-catalogue","what","is","convergence","catalogue"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/what-is-convergence-catalogue/invocations?status=success","failure_events":"/api/articles/what-is-convergence-catalogue/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"what-is-convergence-catalogue","title":"What Is a Convergence Catalogue","body":"<!-- hierarchy:nav -->\n> **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**\n>\n> **Shelf:** Protocol Concepts · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# What Is a Convergence Catalogue\n\n## §SELF — what-is-convergence-catalogue\n\n**What this page is:** A definition of the convergence catalogue framework for identifying agreements across independent knowledge domains.\n**What it explains:** How a convergence catalogue selects and organizes claims that have been independently derived in multiple fields, and why this structure matters.\n**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.\n\n### What a Convergence Catalogue Is\n\nA 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.\n\n### Why It Matters\n\nIf 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.\n\n### The Key Idea\n\nA node is admitted to the catalogue only if it satisfies three criteria:\n\n1. **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.\n2. **Falsifiable prediction.** The claim must imply a test that could prove it wrong. A claim that cannot be tested does not qualify.\n3. **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.\n\nAn 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:\n\n- Ilya Prigogine (physics, 1967) — from studies of Bénard cells and non-equilibrium thermodynamics.\n- Erwin Schrödinger (biology, 1944) — from the question \"What is Life?\" and the observation that living systems feed on negative entropy.\n- Jeremy England (physics, 2013) — from the MIT driven matter theorem showing that matter under external driving spontaneously arranges to dissipate energy.\n\nThree independent derivations. Three different domains. Same underlying principle.\n\nThe catalogue contains 25 such nodes spanning physics, biology, economics, mathematics, philosophy, computer science, and systems theory.\n\n### What It Got Right\n\n- **Structured independence check.** The requirement for cross-domain derivation prevents field-specific bias from masquerading as universal truth.\n- **Falsifiability as a filter.** Requiring a testable prediction excludes unfalsifiable claims, keeping the catalogue grounded in empirical content.\n- **Rival exclusion.** Requiring that a named alternative has been tested and rejected strengthens each node's standing — the claim has survived competition.\n- **Replicable method.** Anyone can apply the three criteria to evaluate a new candidate node. The selection process is transparent and repeatable.\n\n### What It Got Wrong or Left Unfinished\n\n- **Does not quantify convergence strength.** Two domains agreeing is treated similarly to six domains agreeing. There is no weighting system.\n- **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.\n- **No formal update mechanism.** The catalogue does not specify how nodes are revised or removed when new evidence contradicts them.\n- **25 nodes is a starting point, not a ceiling.** The catalogue is incomplete. Many potential nodes have not yet been evaluated.\n\n### How It Connects to Other Ideas\n\n**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.\n\n**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.\n\n**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.\n\n### Sources\n\n- Prigogine, I. (1967). *Introduction to Thermodynamics of Irreversible Processes*. Interscience Publishers.\n- Schrödinger, E. (1944). *What is Life? The Physical Aspect of the Living Cell*. Cambridge University Press.\n- England, J.L. (2013). \"Statistical Physics of Self-Replication.\" *Journal of Chemical Physics*, 139, 121923.\n- Wilson, E.O. (1998). *Consilience: The Unity of Knowledge*. Alfred A. Knopf.\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [Protocol Concepts shelf](https://miscsubjects.com/a/oip-protocol-concepts) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [What Is Autopoiesis](https://miscsubjects.com/a/what-is-autopoiesis)\n- [What Is Capability-Based Security](https://miscsubjects.com/a/what-is-capability-security)\n- [What Is a Capability Token](https://miscsubjects.com/a/what-is-capability-token)\n- [What Is a Confused Deputy](https://miscsubjects.com/a/what-is-confused-deputy)\n- [What Is Context as Cursor](https://miscsubjects.com/a/what-is-context-as-cursor)\n- [What Is a Falsification Surface](https://miscsubjects.com/a/what-is-falsification-surface)\n- [What Is HATEOAS](https://miscsubjects.com/a/what-is-hateoas)\n- [What Is the History of Link Protocols](https://miscsubjects.com/a/what-is-link-protocol-history)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/what-is-convergence-catalogue`\n- JSON article: `https://miscsubjects.com/api/articles/what-is-convergence-catalogue`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20Is%20a%20Convergence%20Catalogue`\n","hero":null,"images":[],"style":{},"tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-convergence-catalogue"],"category":null,"model":"kimi-agent-import","ledger":{"href":"/api/articles/what-is-convergence-catalogue/ledger","live":true},"embeds":[],"widgets":[{"type":"note","title":"Zero-context","text":"This page is self-explaining: §SELF states what it is, what it explains, and why to read it."},{"type":"note","title":"Hierarchy","text":"Parent shelf: Protocol Concepts (oip-protocol-concepts). Hub: oip-thinker-reference. Root: /a/oip."},{"type":"note","title":"Voxel","text":"Each article is a node. Links Up the tree + Related form the traversable graph."},{"type":"stat","value":20,"label":"Protocol Concepts on shelf"}],"home":true,"claims":[],"sources":[],"reviews":[],"extra":{},"has_traversal":false,"register":"standard","status":"published","revisions":0,"contributions":[],"provenance":[{"ts":"2026-07-15T04:20:55.154Z","model":"kimi-agent-import","action":"write","prompt":"","input":"","response":"","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"dde30bb4c62e1711ce1c63434ef09303975f658f401c9f4eb8ad9a1568de8ec5"},{"ts":"2026-07-17T02:43:37.460Z","model":"owner","action":"voxel_divide","prompt":"","input":"what-is-convergence-catalogue","response":"33 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"dde30bb4c62e1711ce1c63434ef09303975f658f401c9f4eb8ad9a1568de8ec5","hash":"611893477fb6cb5c5fe30d5e502ca308983c3261af7840bd6806d93ef8a5523e"}],"energy":{"passes":2,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"kimi-agent-import":1,"owner":1},"head":"611893477fb6cb5c5fe30d5e502ca308983c3261af7840bd6806d93ef8a5523e"},"posted_at":"2026-07-15T04:20:55.154Z","created_at":"2026-07-15T04:20:55.154Z","updated_at":"2026-07-17T02:43:37.460Z","machine":{"shape":"article.machine/v1","slug":"what-is-convergence-catalogue","kind":"article","read":{"human":"https://miscsubjects.com/a/what-is-convergence-catalogue","json":"https://miscsubjects.com/api/articles/what-is-convergence-catalogue","bundle":"https://miscsubjects.com/api/articles/what-is-convergence-catalogue/bundle?format=markdown"},"traversal":{"prev":null,"next":null,"hub":null,"series":null,"position":null,"of":null},"ledger":{"claims":0,"sources":0,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/what-is-convergence-catalogue/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=what-is-convergence-catalogue","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"what-is-convergence-catalogue\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"what-is-convergence-catalogue\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/what-is-convergence-catalogue/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"what-is-convergence-catalogue\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/what-is-convergence-catalogue | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/what-is-convergence-catalogue","json":"/api/articles/what-is-convergence-catalogue","markdown":"/api/articles/what-is-convergence-catalogue/bundle?format=markdown","skill":"/api/articles/what-is-convergence-catalogue/skill","topology":"/api/articles/what-is-convergence-catalogue/topology","versions":"/api/articles/what-is-convergence-catalogue/revisions","invocations":"/api/articles/what-is-convergence-catalogue/invocations"},"editorial_review":null,"editorial_audit":{"slug":"what-is-convergence-catalogue","ok":false,"issues":[{"code":"heading_filing_label","message":"section heading “Why It Matters” is a filing label that gives a cold reader no claim","replacement":"Replace “Why It Matters” with the concrete claim, event, or object introduced in that section."},{"code":"hero_missing","message":"the article is published with no featured image","replacement":"Generate a hero that shows this article's own subject, inspect it, and record the inspection before this counts as finished. An article with no image is not finished."}]},"body_hash":"189ab7a77ae8efd09aab6765560bdfadce32ec00197a9b6357fd615a18c69d9f"}}}