• title: Bidirectional Structured Substrate — Core Producttype: conceptcreated: 2026-06-10tags: [substrate, bidirectional, data, protocol, product]
• Bidirectional Structured Substrate
  • The Core Product
  • What Makes It Bidirectional
  • What Makes It Structured
  • What Makes It a Substrate
  • Properties
  • Comparison

§title: Bidirectional Structured Substrate — Core Product type: concept created: 2026-06-10 tags: [substrate, bidirectional, data, protocol, product]

§Bidirectional Structured Substrate

§The Core Product

Kapnet’s core product is a bidirectional structured data + protocol layer. Not just a messaging system. Not just a database. A substrate where data flows in both directions, is typed and validated by protocol, and is permanently anchored to Bitcoin.

§What Makes It Bidirectional

Traditional data flows are one-way: client → server → database. Kapnet’s substrate is bidirectional:

Agent A ←→ TXXM ←→ Agent B
   ↓                    ↓
Braid ←→ Knot ←→ State Tree
   ↓                    ↓
Bitcoin (settlement anchor)

Every action produces a reaction. Every state transition produces a reverse-proof. Every coordination bid creates a coordination ask.

§What Makes It Structured

Every message on the substrate is typed:

• Submission — new coordination act
• Review — attestation of a submission
• Governance — proposal, vote, execution
• Membership — access grant/revoke
• Chat — ephemeral coordination
• Document — persistent collaborative state
• Signal — discovery/liveness
• Anchor — Bitcoin commitment

Every type has a schema. Every schema is validated. Every validation is deterministic.

§What Makes It a Substrate

The substrate is not a product users interact with directly. It’s the layer on which products are built. Like TCP/IP for the internet. Like HTML for the web. Kapnet’s substrate is the coordination layer on which institutions are built.

§Properties

• Deterministic: Same inputs → same outputs, always
• Replayable: Any participant can replay the full history
• Forkable: Disagreements produce visible forks, not hidden rollbacks
• Settlement-anchored: State can be committed to Bitcoin
• Namespace-scoped: KOR isolation with cross-KOR communication
• Identity-based: npub = identity, no passwords, no centralized auth
• Censorship-resistant: Any relay can carry messages, any node can participate

§Comparison