Alpha hardening — planning index
Pre-release alpha audit + grilling (2026-07-04). Research complete; planning complete; Bucket 1 blockers next.
Locked scope: one settlement tracker, open node join, devnet mock-USDT, reputation carries forward → fraud must be bounded. See ADR-0016.
Artifacts
ADRs (this feature)
| ADR |
Title |
| 0016 |
Alpha scope & known limitations |
| 0017 |
Tracker authentication & authorization |
| 0018 |
Fraud detection, verification & reputation (flagship) |
| 0019 |
Money-path consistency — design accepted, impl deferred |
| 0002 |
Amended — settlement superseded by 0015 |
| 0010 |
Amended — TLS alpha reality (relay only) |
Recommended implementation order
Implement Bucket 1 first. Fraud arc depends on auth foundation (02 + 20), hive gossip enforcement (01), and persistence (05).
Phase 1 — Trust boundary (alpha blockers)
Phase 2 — Fraud arc (after Phase 1)
Prod gate: 21 honest-noise calibration corpus must complete before enabling production TOPLOC audit thresholds (issues 09–10 in prod). Dev/staging TOPLOC wiring (06–08) may proceed in parallel.
Phase 3 — Bucket 2 (post-alpha, design tracked)
Phase 4 — Doc hygiene (parallel anytime)
First 3 to implement
- 02 + 20 — Unified auth boundary + validator service token (shared helper and roles)
- 01 — Apply hive auth to billing/accounts/stats gossip endpoints
- 05 — Persist strike/ban/reputation (penalties must survive restart)
Research anchor
Fraud design cites .scratch/alpha-hardening/research-verifiable-inference.md:
- ADOPT TOPLOC (§8–9, build-vs-adopt table)
- On-demand commitments, not every request (§8 layer 1 footnote; ADR-0018 §3)
- 5% audit budget as target, not cap (§1.1, §6)
- 19× deterrence via full pending forfeiture (§1.1)
- Hop bisection blame pattern (§1.2, §8 layer 3)
- Honest-noise corpus before prod thresholds (§8 layer 3; issue 21)
- Roadmap-only: zkML, TEE, Gensyn RepOps (§9)