Conversation
Captures Phase 5 exit per phase5-plan.md §6 + §10. Mirrors phase4-evidence.md shape: one section per gate, "what this proves" roll-up, then each §10 done-criterion cited green. Verified locally (gate outputs in the evidence doc): * pytest profile/build/ — 116/116 (51 prior + 65 across Phase 5) * make check-freshness — clean (worst=OK) * make check-links — clean (offline; 59 URLs catalogued) * make check-licenses — clean (worst=SKIP; 9 INVENTORIED + 1 SKIP for m-modern-corpus's mixed-per-subdir) * make check-schema-compat — clean (no bumps in this PR; no non- additive changes) * make handshake — 8/8 steps * make recipes-check — 4/4 clean * make validate-catalog — OK * make check-docs-prose — clean All seven §10 done-criteria cited green in the evidence doc: 1. check-freshness.py + 15 TDD + make target (PR #32 / e9e00cb) 2. check-links.py + 13 TDD + B0 binary-URL fix in validate-repo-meta.py + 5 TDD (PR #33 / 16bbd08) 3. check-licenses.py + 18 TDD + per-license signature dict (PR #34 / 5d9a995) 4. check-schema-compat.py + 14 TDD + fetch-depth:0 wiring (PR #35 / 8792787) 5. CI per-PR runs all four --offline variants 6. Weekly cron firing runs --strict freshness + live link-check + full LICENSE-fetch 7. This evidence file Also: * docs/ai-discoverability/README.md phase table — Phase 5 row flipped from "in flight" → "Closed 2026-05-11" with evidence link. * AI-discoverability-architecture.md "Phase 5 — in flight" section rewritten to "Phase 5 — closed 2026-05-11"; notes the operational loop is complete and future phases would address growth, not enforcement coverage.
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
1 participant
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.
Summary
Track E of phase5-plan.md §6. Phase 5 close-out — ships
docs/ai-discoverability/phases/phase5-evidence.mdcapturing clean runs of every Phase-5 gate plus the companion gates from earlier phases.Evidence captured
pytest profile/build/make check-freshness(Track A)make check-links(Track B, offline)make check-licenses(Track C, offline)make check-schema-compat(Track D)make handshake(Phase 3)make recipes-check(Phase 3)make validate-catalog(Phase 1)make check-docs-prose(Phase 0)All seven §10 done-criteria cited green
check-freshness.py+ TDD + make targete9e00cbcheck-links.py+ TDD + B0 binary-URL fix16bbd08check-licenses.py+ TDD + signature dict (10 repos)5d9a995check-schema-compat.py+ TDD + fetch-depth:0 wiring8792787--offlinevariants--strictfreshness + live link-check + full LICENSE-fetchphase5-evidence.mdcaptures clean runsCompanion updates
docs/ai-discoverability/README.mdphase table — Phase 5 row flipped from "in flight" → "Closed 2026-05-11" with the evidence link.AI-discoverability-architecture.md"Phase 5 — in flight" section rewritten to "Phase 5 — closed 2026-05-11"; notes the operational loop is complete and future phases would address growth, not enforcement coverage.What this completes
Pre-Phase-5,
verified_oncorrectness, URL liveness, declared-license accuracy, and schema-compat discipline lived in maintainer heads. Post-Phase-5, each has an automated gate. PR-mode runs the cheap--offlinevariants on every push/PR; the existing weekly Monday-14:00-UTC cron firing runs the full-fetch variants so upstream drift surfaces within 7 days (the parent-plan §7 Phase-5 exit criterion).Out-of-scope follow-ups (noted in evidence doc)
repo.meta.jsonper cron rather than committed-catalogverified_on).run-recipe.py's minimal YAML parser limitation (>block scalars /[]inline arrays).None blocks Phase 5 close.
Test plan