eric/geth
Watch
1
0
Fork
You've already forked geth
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: add dogfood evidence checklist

Browse source
This commit is contained in:
Eric Wendland 2026-07-05 23:52:58 +02:00
commit 251bcf36c3
2 changed files with 198 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/production-readiness-roadmap.md
View file

@ -329,6 +329,11 @@ Goal: make first deployment the start of a controlled compatibility story.
Goal: prove the system works as an actual base layer before broader use.
Use [`dogfood-checklist.md`](dogfood-checklist.md) to record command output,
platform/version details, and evidence for this gate. This phase cannot be
marked complete from local unit or integration tests alone; it requires two real
machines and tagged pre-release upgrade evidence.
- `[ ]` Complete two-machine dogfood checklist.
Acceptance criteria:
- `[ ]` Fresh install works on at least two real machines.
@ -344,11 +349,12 @@ Goal: prove the system works as an actual base layer before broader use.
## Working Order
1. `[x]` Finish Phase 0.
2. `[~]` Refactor `geth-node` into daemon subsystems.
2. `[x]` Refactor `geth-node` into daemon subsystems.
3. `[x]` Add stable contract and golden JSON tests.
4. `[x]` Harden store migrations and backup.
5. `[x]` Complete security-boundary test coverage.
6. `[x]` Replace prototype private CAS cryptography.
7. `[ ]` Add fault-injection sync tests.
8. `[ ]` Improve automation commands and JSON errors.
9. `[ ]` Add operational health, doctor, and release gates.
7. `[x]` Add fault-injection sync tests.
8. `[x]` Improve automation commands and JSON errors.
9. `[x]` Add operational health, doctor, and release gates.
10. `[ ]` Complete the two-machine dogfood gate.