The README is currently the entire public doc surface (design docs are deliberately local-only). For OSS adoption the project needs public documentation that explains the concepts, not just the commands.
What's needed
- Restructure README: product first (quickstart in <5 minutes: import → curate → experiment → gate), benchmark-engine content moved down or out.
- Public concept docs (docs/ on the repo, written fresh for public consumption): the sealed-partition firewall, pre-declared gate rules, earned-trust judging, money-safety, the optimize-proposes/gate-decides loop.
- A worked example with a small bundled dataset so
git clone → verdict works without Langfuse credentials.
- LICENSE + CONTRIBUTING before the repo flips public.
Note: the "no md except README on remote" rule was for private planning docs; public-facing docs written for users are a different category — confirm scope before pushing.
The README is currently the entire public doc surface (design docs are deliberately local-only). For OSS adoption the project needs public documentation that explains the concepts, not just the commands.
What's needed
git clone → verdictworks without Langfuse credentials.Note: the "no md except README on remote" rule was for private planning docs; public-facing docs written for users are a different category — confirm scope before pushing.