Bitcoin Ledger Automation Blueprint

This note captures the scripts and guardrails that keep the Bitcoin Satori ledger artefacts reproducible.

Artefact Sources

• docs/status/bitcoin-ledger/genesis.json — canonical genesis metadata.
• docs/status/bitcoin-ledger/template_emission.csv — emission schedule (replace the template once treasury data is confirmed).
• docs/status/bitcoin-ledger/treasury_transactions.json (planned) — signed hash commitments per payout period.
• docs/status/bitcoin-ledger/testnet.md — RPC topology, sample block hashes, and troubleshooting snippets.

Tooling

• tools/bitcoin/check_ledger.py — highlights missing genesis fields and placeholder emission rows (--strict for CI gating once data is live).
• tools/status/check_certs.py — confirms TLS coverage so RPC endpoints ship with valid certificates.
• scripts/workflows/build_bitcoin.sh — deterministic build pipeline wrapper (wire once the fork repository lands).
• scripts/workflows/quick_validation.sh — runs the ledger check in non-strict mode today; switch to strict when genesis is final.

Operational Flow

1. Capture data — run python tools/bitcoin/check_ledger.py --strict locally before committing new ledger artefacts.
2. Attach proofs — add emission CSV signatures and treasury transaction hashes to the repo, keeping raw secrets in /etc/zenpower/.env.secrets.
3. Regenerate docs — bash scripts/workflows/run_workflow.sh docs ensures compiled Markdown picks up the changes.
4. Publish status — make status-update to push the latest ledger snapshot to the public status portal.
5. Smoke — once nodes are online, extend tools/status/surface_smoke.py with RPC health probes and record outputs under docs/status/bitcoin-ledger/.

Log every completed step in docs/status/BLOCKERS.md so the Owner Ops cadence has a verifiable trail.