16/21
76%Strong repo-visible signals include a real bootstrap path, stable command surfaces, substantive test and lint coverage, and a top-level AGENTS guide reinforced by nested subtree guidance. The biggest legibility gaps are documentation structure and decision traceability: the docs tree is broad but not clearly indexed or cross-linked from one contributor map, which matters in a repo with several routed subsystems, and there are no visible ADR-style decision records explaining major architecture or workflow choices.
3 Quick Wins
Start recording major architecture and workflow decisions in ADRs.
Add `docs/README.md` or `docs/index.md` and improve cross-links between the main setup, architecture, and contributor pages.
Keep the repo map short and link outward to deeper docs instead of duplicating them.
Metrics
Based on OpenAI's Agentic Legibility and the Assistants & Agents Build Hour framework. Powered by Twill.
