Skip to content
FlowBondFlowBond Protocol

The protocol beneath the worlds

A Layer 0 of identity, value and intelligence. Four primitives over one append-only ledger, private by construction, and built to keep working when the network does not.
Read the specificationHow this document is governed
The FlowBond five-plane stack, from Plane 4 Applications at the top down to Plane 0 Resilience Transport at the bottom. Each plane speaks only to the plane directly below it. PLANE 4Applications
Products built on the protocol, under identical license terms. Application profiles live here.
CONSUMERSPLANE 3Companion OS
Agents that act for a person — only ever through protocol primitives, through a spend gate, with no side doors.
AGENTSPLANE 2Protocol · Layer 0
FBID · FlowShare · StableFlow · LifeKey — four primitives written over one append-only ledger.
PRIMITIVESPLANE 1Privacy Core
Every primitive proves without revealing. Public state is commitments and proofs, never contents.
ZERO-KNOWLEDGEPLANE 0Resilience Transport
Sign locally, queue on the mesh, reconcile when a path exists. The floor never assumes the internet.
OFFLINE-FIRST

What this document is

Section titled “What this document is”

This is the base document of the FlowBond Foundation: the normative specification of the FlowBond Protocol. It defines four primitives (identity, split, credit, trust) over a single append-only ledger, and the obligations any implementation MUST meet to call itself conformant.

It is versioned, auditable and changed only through a public process. The git history of this repository is the audit log; the changelog is append-only; every release is tagged. Nothing here changes silently.

Current version: v0.1-draft. Draft means the primitives are stable enough to implement against and the wording is still open to challenge. See versioning policy.

The four primitives

Section titled “The four primitives”

FBP-01 · FBID

Portable identity. Verifiable claims, revocable links, five auth rails, recovery that never hands custody to anyone. Consumers get scoped grants, never ownership. Read →

FBP-02 · FlowShare

Splits and conditional payout as ledger events. Zero custody, ever. Splits MUST sum to the whole. Payment rails are adapters and stay out of the spec. Read →

FBP-03 · StableFlow

Closed-loop credits, one economy instance per consumer, with a spend gate agents must pass through. Credits NEVER redeem for cash, and no consumer can waive that. Read →

FBP-04 · LifeKey

Programmable trust. Parties, signatories, thresholds, conditions, soulbound bindings, and a counselor who advises and is NEVER a signatory. Read →

All four are written over FBP-00 · the ledger, which has one rule that shapes everything else: events are appended, never updated and never deleted.

Three commitments that are not negotiable

Section titled “Three commitments that are not negotiable”

Prove without revealing

Every primitive states what MUST be provable and what MUST NOT be exposed. Public state is commitments and proofs. Compliance happens through selective disclosure, never through open data. Privacy Core →

Work without the internet

Events sign locally and queue on a mesh. Reconciliation is deterministic when a path appears. Connectivity is a convenience, not a precondition. Transport →

Know nothing of its consumers

The protocol does not name the products built on it, and MUST NOT special-case them. Products appear only in the non-normative ecosystem index.

Where to start

Section titled “Where to start”

If you are reviewing

Read §1 Architecture for the shape of the system, then Privacy Core for the constraint that explains most design choices.

If you are auditing

Go to /audit: how to pin a version to a git tag, verify it, and read the machine-readable index at /spec.json.

If you want to change something

The RFC process is the only door. Issue → draft PR → public review → editor merge → changelog entry.

Audit this pageView sourceHistoryCHANGELOGHow to verify