Marketing (Public Overview)

The Central Binary (CB)

Deterministic clearing for model and agent transactions.

CB sits between clients and model providers and provides:

Deterministic settlement (allow | transform | escalate | void)
Evidence-first operation (append-only WALs)
Operator-grade review (Ledger + Receipt + Audit Trace)

Who this is for

Teams that need auditable controls on model output.
Operators who need a Ledger-first surface instead of ad-hoc logs.
Builders who need an enforcement point that stays provider-agnostic.

What you get (outcomes)

A clearing decision you can justify: settlement outcomes are emitted as evidence.
A forensic trail you can replay: the system writes time-ordered WAL artifacts.
A stable basis for reporting: CB Index is derived from settlement evidence, not opinion.

How it works (at a glance)

Route (write routing.jsonl)
Execute (run provider/model)
Settle (write settlement.jsonl)
Seal (optional; write seal.jsonl)
Repro stamp (write repro.jsonl)
Archive (optional; write archive.jsonl)

Operator terminal (CBX)

The CBX Terminal is the operator surface.

Ledger is the primary surface.
Receipt shows the selected transaction’s fields.
Audit Trace aggregates WAL-derived events for the selection.

Call to action

Read the technical spec: whitepaper.md
Understand the rating model: cb_index.md
See what’s implemented vs pending: roadmap.md

Screenshots (drop-in)

Add images under docs/src/assets/ and reference them here.

![CBX Terminal — Ledger + Receipt + Audit](assets/cbx-terminal.png)

Download / run (developer preview)

Local run:

cargo test
cargo build --bin cb-runtime
NOT_RUNTIME_PORT=8714 ./target/debug/cb-runtime
cargo run --manifest-path bench/Cargo.toml

Implemented today vs roadmap

Implemented surfaces (repo-grounded):

Routing + routing WAL + routing stream
Settlement + settlement WAL + settlement stream
Repro stamp + verification endpoint
Evidence bundle export + verification tooling
Operator terminal: Ledger-first + Receipt + Audit Trace
Optional: S3 archival worker + archive surfacing

Roadmap (not implemented):

Identity-first orchestration (Ping)
External attestation (Merkle anchoring)
AP2 lifecycle
Market APIs and enterprise connectors

Learn more

architecture.md
evidence.md
operator_terminal.md