Front-door + product-surface files (README, GRIMOIRE, FEATURES,
FOR_RECRUITERS) keep their concrete v60 content — these are the pages
that need to project ambition and inform potential users / cohorts /
recruiters.
Three files trimmed to vague:
- ARCHITECTURE.md — drop syscall numbers (469-485), specific module
names, "11-region brain", "83.54% Rust", "8-node Tailscale mesh".
Keep the synaptic gap framing, four pillars by name, three-image
table, axioms. Specs invite "well actually" issues; philosophy
doesn't.
- ROADMAP.md — keep v60 as the current generation marker, drop the
v44–v60 codesprint table (16 codenamed campaigns is a lot of
fact-checkable claims), drop the explicit v61–v70 horizon bullets.
Replace with broad theme prose. "What we're heading into" rather
than "what we promise by when".
- CONTRIBUTING.md — drop the explicit "what's coming" promises (lab
marketplace, CVE channel, community calls, public source release
date). Drop the "open an issue with title X" workflows that invite
unbidden submissions. Keep the long-game framing and quiet-channels
posture.
Net: front-door pages still impress with specifics; the surfaces a
random reader might use to file noise issues now offer none of the
hooks for it.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- README.md: Complete project overview with features, download, quick start
- ARCHITECTURE.md: System design, components, security architecture
- Includes technology stack, deployment models, performance specs
- All non-sensitive IP suitable for public consumption
