Reading wallet
Bitcode docsZero-to-hero

Learn Bitcode from AssetPacks to proof.

Bitcode docs teach the complete path: what an AssetPack commodity is, how BTD measures scalar volume and rights, why BTC settlement money and proof readback authority matter, and how /deposits, /reads, /packs, MCP, ChatGPT App, and Bitcode Chat stay source-safe.

For new readers

Start from the AssetPack before touching value-bearing controls.

For operators

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

For builders

Map MCP, ChatGPT App, Bitcode Chat, GitHub, webhooks, compute, and storage into proof readback.

Start readingAction manual
Walkthrough

The recorded walkthrough is being refreshed. Use the docs chapters and the Packs activity ledger 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 AssetPacks so Bitcode reads as measured technical intelligence, not a generic app.

02

Learn the product surfaces

Then learn /deposits, /reads, and /packs before opening value-bearing controls.

03

Practice write/read discipline

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

04

Audit the system

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

Chapters15 pages

V45 / V46 claim boundary

Product docs map back to the active canon.

Protocol docs map back to active law. Public docs explain; proof readback decides. The public docs teach the current product routes in user order: AssetPack commodity, BTD scalar volume and rights, BTC settlement money, proof readback authority, /deposits, /reads, /packs, interfaces, and configuration.

Protocol

Commercial protocol map (V48)

AssetPack lifecycle, BTD volume and rights, Bitcoin settlement, proof readback, interface disclosure, and promotion truth.

Proofs

Witnesses, replay, and disclosure

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

Settlement

BTD volume and Bitcoin settlement

Needs-fits scores, volume and rights, finality receipts, delivery unlock, compensation, and /packs reread.

Interface API references

Build against Bitcode without losing proof readback authority.

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 proof readback confirms the outcome.

MCP API

Public machine interface reference

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

ChatGPT App

Conversational interface reference

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

Action map

Every write has a read-back expectation.

The action 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

Route readback 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

Packs

Read the activity frame

Inspect network AssetPack activity: measurements, needs-fits, settlement, compensation, delivery, and repair — without exposing unpaid source.

Read

Request Reading

Express a Reading, review a synthesized Need, request needs-fits scores, inspect a source-safe AssetPack preview, and settle for knowledge delivery.

Deposit

Prepare supply

Attach permitted source, synthesize AssetPack options, review measurements and obfuscations, and list only the IP you approve.

Protocol

Audit the canon

Canonical Bitcode protocol semantics: AssetPacks, BTD volume and rights, BTC settlement, proofs, and fail-closed promotion posture.