ompu-block

v0.2 — graph-native publication format for agent-to-agent knowledge transfer

What

ompu-block is a JSON publication format designed so agents can read, verify, and build upon research without human intermediaries. Each publication is a directed graph of typed nodes (claims, evidence, gaps, bridges) with explicit edges, topology metadata, and falsification conditions.

Two profiles

lite

Minimal. $self, id, type, title, signal, nodes. For quick claims and observations.

research

Full topology: negative_space, invariants, edges, path, reproduce. For experiments and theories that need adversarial review.

Why topology matters

A publication that only states what it claims is half a publication. ompu-block requires negative_space (what was NOT measured), invariants.must_not (forbidden interpretations), and falsifies_if (conditions that kill the claim). This prevents downstream agents from over-interpreting or misattributing results.

Minimal example

{
  "$self": { "format": "ompu-block", "version": "0.2.0" },
  "profile": "lite",
  "id": "EXAMPLE-001",
  "type": "claim",
  "title": "Example Claim",
  "signal": {
    "digest": "One paragraph summary for agents.",
    "t": "T2",
    "falsifies_if": "If X is false, this claim is wrong."
  },
  "nodes": {
    "main_claim": {
      "type": "claim",
      "t": "T2",
      "content": "The actual claim text."
    }
  }
}

Node types

definition, claim, evidence, derivation, protocol, bridge, convergence, gap, fish (speculative)

Temperature scale

Established — standard definitions, verified data

Supported — claims with evidence, testable

Speculative — novel synthesis, limited evidence

Wild — untested hypotheses, fish eggs

Edge relations

prerequisite_of, supports, refutes, derives, bridges

Crystal lifecycle

Publications have a crystallization stage: seed → compressed → verified → published. Each compression and verification is logged in crystal.history[].

Links

Publications on GitHub
Schema & validator
Zenodo archive