Object Invocation Protocol · protocol specification

Causal Contact Rule — Convergence vs Synthesis

#oip#convergence#synthesis#objection-4#self-explaining

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-causal-contact-rule
**This page as JSON:** https://miscsubjects.com/api/articles/oip-causal-contact-rule
**Machine bundle:** https://miscsubjects.com/api/articles/oip-causal-contact-rule/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.

<!-- hierarchy:nav -->

Path: OIPConvergence CatalogueCausal Contact Rule
Attack type answered: equivocation between independently derived and deliberately assembled

Causal Contact Rule — Convergence vs Synthesis

§SELF — oip-causal-contact-rule

What this page is: the tagging rule that separates true cross-domain convergence from synthesis (designer read the sources). What it explains: why computing lineage (Simula, Smalltalk, ocaps) cannot carry the same independence load as Prigogine/Schrödinger/England without contact. Why read it: one word was load-bearing for both; naming the difference makes the strong claim bulletproof.

Scores (use on every convergence node and thinker mapping)

| Score | Meaning | Example class | |---|---|---| | 10 | Causal contact impossible or vanishingly unlikely (centuries/fields apart, no shared lab) | Cross-domain physics/biology | | 7–9 | Weak or indirect contact possible | Parallel rediscovery in adjacent fields | | 4–6 | Shared intellectual climate | Same era conferences, shared textbooks | | 1–3 | Designer demonstrably read or inherited the source | Computing lineage in OIP build history | | 0 | Direct assembly / citation chain | This corpus's own prior pages |

Claims that survive

  • Convergence claim (strong): only nodes with high causal-contact scores.
  • Synthesis claim (honorable): low-score computing/philosophy lineage deliberately integrated. Still valuable; not independent discovery.

How to attack this page

Show a node labeled 10 that has documented causal contact, or a node labeled 1 that was never in the designer's reading. Fix the tag, not the word "convergence."

Links

oip-causal-contact-rule · 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 Causal Contact Rule — Convergence vs Synthesis. 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.
Loading more articles…