A single self-contained reading manual designed to bring a fresh agent
(LLM or human) to current-state proficiency in 30 min of reading +
30 min of environment validation, then have them run the next round of
ablation experiments without re-litigating questions already settled.
Structure:
§0 TL;DR -- what you are inheriting in 5 lines
§1 Reading order, tiered into Must-Read / On-Demand / Archive,
with reasons for each
§2 Current-state snapshot: trace/hardware/branches + claims verified
+ hypotheses pending
§3 The three ablation experiments (E1/E2/E3) with full CLI flag
specifications and environment-validation checklist
§4 Known gotchas (8 of them) with symptoms and fixes -- the most
important section to skim before you start
§5 CLI cheatsheet: run experiments / read data / plot / git
§6 Result-analysis checklist: numbers to collect, expected ranges
§7 FAQ for likely stuck-points
§8 Anti-patterns: what NOT to do
§9 Two specific deliverables the main agent expects back
Appendix A: file location lookup table
Appendix B: commit lookup table (by intent)
Goals encoded into the doc:
- Frame "your job is ablation, not new development" -- the new agent
should not be tempted to start D->P sync work; that goes on the
feat/d-to-p-sync branch in a separate phase.
- Make abort-accounting / max-input-len / mooncake-TCP-default
pitfalls extremely visible up front so they don't get repeated.
- Provide expected-result ranges so a 2x deviation is treated as a
config check, not a "finding".
- Make the critic-vs-production framing explicit so the new agent
knows when an audit-style "MAJOR" is actually a design intent.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
5a2fb8799c