Reading wallet
Bitcode docsZero-to-hero

Learn Bitcode from Source Shares to proof.

Bitcode docs teach the complete path: what a Source Share is, how Exchange state works, how Terminal writes and reads, why proofs and $BTD settlement matter, and how connected commercial interfaces stay bound to the same system.

For new readers

Start from the market object before touching Terminal controls.

For operators

Learn every write, expected read, proof signal, and readiness blocker.

For builders

Map MCP, ChatGPT App, GitHub, webhooks, compute, and storage into Exchange.

Start readingTerminal action manual
Walkthrough

The recorded walkthrough is being refreshed. Use the docs panels and the Bitcode Terminal while the next capture is published.

First-time path

Read in this order if Bitcode is new.

The docs are intentionally chaptered. You can jump anywhere, but the first path moves from concept to product to proof without assuming prior Bitcode context.

01

Understand the object

Start with Source Shares so Bitcode reads as measured technical intelligence, not a generic app.

02

Learn the product surfaces

Then separate Exchange state from Terminal operation before opening write controls.

03

Practice write/read discipline

Use the action guide to learn what every Terminal write should make rereadable.

04

Audit the system

Finish with V26, proofs, settlement, and interface docs so the under-the-hood system is clear.

Chapters15 pages

V26 coverage

Product docs map back to the canon.

The public docs teach the whole V26 system in user order: Protocol, Exchange, Terminal, proofs, settlement, interfaces, and configuration.

Protocol

V26 source-to-shares canon

Gates, domain model, operator chain, subsystem boundaries, validation, generated evidence, and promotion truth.

Proofs

Witnesses, replay, and disclosure

Proof families, theorem IDs, witness artifacts, generated appendices, projection, redaction, and fail-closed posture.

Settlement

$BTD exact accounting

Fit-quality receipts, journals, settlement participation, wallet readiness, payment modes, and source-to-shares allocation.

Interface API references

Build against Bitcode without losing the Exchange contract.

The interface docs now read like product-facing API docs: every feature says when to call it, what inputs it accepts, what should return, and which Terminal or Exchange read confirms the outcome.

MCP API

Public machine interface reference

Active MCP tools are documented by feature, request shape, expected output, failure posture, and Terminal reread.

ChatGPT App

Conversational interface reference

ChatGPT App tools list how to use each call, required inputs, returned metadata, and confirmation rules for writes.

Terminal action map

Every write has a read-back expectation.

The Terminal guide documents the write actions operators can take and the exact read surfaces that should confirm the result before they move into proof, settlement, or history.

Open action guide

Command deck

Choose the active scenario

The Terminal rereads deposit, read, fit, and closure against the selected scenario rather than treating it as a cosmetic filter.

Command deck

Set projection

The rest of the Terminal should make clear which posture is being read before any state-changing work is trusted.

Command deck and closure controls

Set branch mode

Branch, settlement, and proof panels should reflect the selected mode as an operator-visible Bitcode decision.

Repository context

Select provider and repository

Repository supply, deposit provenance, and later closure reads should all stay attached to that selected source perimeter.

Repository context

Record repository anchor

Recent Terminal activity shows repository posture beside deposit, read, proof, and settlement records.

Deposit-side supply

Search, filter, and select supply

Selected inventory remains explicit and can be carried directly into deposit, deposit, fit, and closure.

Proof and readiness reads

Read what changed before trusting the flow.

Bitcode Terminal

Terminal activity results

You can search, filter, page, and reopen activity without losing the selected detail read.

Bitcode Terminal

Selected activity detail

You can decide whether to stay at summary level or open exact proof, branch, settlement, or ledger detail.

Experience frame

Read window

The central ledger remains primary while deeper modes and proof views are deliberate follow-through.

Command deck, deposit, and closure controls

Transaction readiness

If readiness is incomplete, branch, deposit, signed settlement, and closure stay fail-closed while review can continue.

External interface readiness

External interface readiness

Live, modeled, boundary-only, and blocked states are visible before downstream proof or settlement work is trusted.

Fast routes

Exchange

Read the public market frame

Read pack activity where source supply, measured reads, settlement posture, compensation, delivery, and repair state meet.

Terminal

Operate the ledger

Open the full Terminal for proofs, history, and deposit-to-settle detail.

Protocol

Audit the canon

Read the public Bitcode protocol specification for system semantics, value flow, proofs, and operating posture.