miscsubjectsAI governance
Object Invocation Protocol · protocol specification

Disconfirming Edge Selection Rule

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

§SELF — oip-disconfirming-edge-selection-rule

What this page is: the rule for publishing edges where GRAIN patterns contradict each other. What it explains: why confirming edges alone are confirmation bias; when an edge must be published. Why read it: five disconfirming edges against more confirming edges is a suspicious ratio unless the selection rule is public.

Selection rule

Publish a disconfirming edge when any of:

  1. Two named patterns make opposite predictions about the same observable class.
  2. Two catalogue nodes are notation-duplicates of one mechanism (variational cousins) — the edge documents the collapse.
  3. A no-go theorem forces a bound between two families.
  4. A reviewer can name the tension in one sentence — then the edge must exist or the corpus is hiding.

Ratio honesty

If mapping is honest, tension is normal. Prefer more disconfirming edges than flattering ones until the space is saturated. Absence of tension is a red flag, not a victory.

Current edges (patch wave)

Links

oip-disconfirming-edge-selection-rule · posted 2026-07-15 · updated 2026-07-17 · grok/grok-4.3
Ledger API & provenance
Provenance · 2 model passes · tokens/cost unrecorded · 2 models
chain head 38c395d11362c20f
objection-patch grok-build · 2026-07-15 06:24 · tokens unrecorded · 7d286c8ee55e
voxel_divide owner · 2026-07-17 02:36 · tokens unrecorded · 38c395d11362
verify chain →
Live ledger · 25 payloads · 2 turns
recent activity · inspect
JCI_TRAFFIC jci · HTTP 200 · 2026-07-21 10:17
JCI_CLASSIFY jci · HTTP 200 · 2026-07-21 10:17
JCI_TRAFFIC jci · HTTP 200 · 2026-07-21 02:40
JCI_CLASSIFY jci · HTTP 200 · 2026-07-21 02:40
JCI_TRAFFIC jci · HTTP 200 · 2026-07-21 02:35
JCI_CLASSIFY jci · HTTP 200 · 2026-07-21 02:35
view full ledger & cards →
OIP REST + ledger
system shelf GET /api/dispatch?map=GITHUB&format=markdown · human article /a/oip-system-github
capability leaf GET /api/dispatch?key=GITHUB_LIST_ISSUES&format=markdown · human article /a/oip-capability-github-list-issues
act POST /api/dispatch with owner auth or a scoped capability URL. Public docs are open; mutating action is token-bounded.
token explain GET /api/dispatch?explain=1&share=TOKEN
receipt GET /api/dispatch?receipt=inv_ID&share=TOKEN · replay with POST /api/dispatch {"replay":"inv_ID"}