docs: sync README with closed judge search, Milestone 1, and a legal notice - #12
Merged
Conversation
…notice - Fix stale counts: the suite is 26 tests, not 8 (four places), and docs/DESIGN.md now runs D1-D16, not D1-D14 (two places). - Rewrite the Status row, Roadmap, and Limitations for the actual state: judge iteration is closed after six judges, Milestone 1 is complete at 20/20 titles, and the three confirmed leaks are documented with both mechanisms (model memory vs. Wikipedia's own overview section). - Drop the Roadmap item that still framed retrieval as not started and the judge gap as the thing blocking it; both are resolved. - Expand the project layout with retrieval.py, retrieval_groq.py, retrieval_prompts.py, stats.py, external_dataset.py, train_spoiler_classifier.py and the three newer calibration scripts, and correct judge.py's description from two judges to six. - Replace the placeholder License section with a real notice: explicit copyright reservation (no LICENSE file exists, so public visibility is not a grant), and the third-party terms it cannot relicense (TMDB, Wikipedia CC BY-SA, the IMDb Spoiler Dataset, cited quotes). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MDoFHbKZRxhUhyFQuYVFUc
serpeigd
marked this pull request as ready for review
August 13, 2026 19:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed and why
Scheduled documentation-sync run.
README.mdonly — no product or measurement-track code touched.The README had drifted behind D15/D16. Its Roadmap still listed "Resolve the judge-trust gap before Milestone 1 (retrieval)" and its Limitations still said "this is why Milestone 1 hasn't started" — but Milestone 1 is complete at 20/20 titles, and the judge search has been closed after six attempts.
Stale numbers, verified against the tree
tests/judge.pyStatus / Roadmap / Limitations rewritten to match reality
SubstringJudgestays the default stated plainly: not because it's good, but because missing things is a bounded failure mode and inventing them isn't. TheSimilarityJudgeresult that ended the search is included — a film's own public premise scored 0.561, higher than the one confirmed real leak at 0.525.overviewsection carries those films' core spoilers verbatim — the GREEN corpus itself wasn't safe for them. Come and See has the same risk latent. Milestone 1's real gain is stated alongside it (grounding 0.0 → 1.0, judge-independent; the five highest-risk twist titles clean) without letting it read as a safety guarantee.--save-briefsplus a human reading the text, which caught all three leaks when no judge caught any.Project layout
Filled in the modules added since the last sync:
retrieval.py,retrieval_groq.py,retrieval_prompts.py,stats.py,external_dataset.py,train_spoiler_classifier.py,generator.py/demo_generator.py, and the three newer calibration scripts.Legal notice (requested directly)
## Licensepreviously read "No license defined yet — personal portfolio repo." It's now an explicit notice: copyright reserved, with the point that public visibility on GitHub is not itself a licence, plus the third-party terms this repo can't relicense — TMDB's non-commercial attribution terms, Wikipedia's CC BY-SA, the IMDb Spoiler Dataset (gitignored, never redistributed; direct scraping prohibited by ToS and not done), and the cited director/critic quotes incontent/researched/*.json.No
LICENSEfile was added — choosing a licence is the author's call, not something a docs-sync run should decide. Flagged below.Verification
Counts and module lists come from the tree itself (
tests/,evals/judge.py,docs/DESIGN.md,run_eval.py's argument parser), not fromCLAUDE.md.pytestisn't installed in this environment, so the suite wasn't run locally — CI is the check.Needs a human decision
Whether to add an actual
LICENSEfile (and which one). The README now states the default reservation accurately in the meantime.Generated by Claude Code