phase5-plan: continuous enforcement hardening plan#31
Merged
Conversation
Phase 5 first move per AI-discoverability-plan.md §6 + AI-discoverability-architecture.md §5. Authors the plan doc that the four enforcement gates (freshness / link-check / license-reconcile / schema-version) will be built against. * New: docs/ai-discoverability/phases/phase5-plan.md. Five tracks following the established phase0-/3-/4-plan shape: A freshness, B link-check (+B0 carry-over fix for the validate-repo-meta.py UTF-8-decode bug on binary URLs), C license-reconcile, D schema-version policing, E close-out evidence. Tracks A-D are independent (no file overlap, no shared mutable state); any pair is safe to run in parallel. Each track ships one profile/build/check-*.py gate + one Make target + one CI step. PR-mode runs the --offline variants; weekly cron runs the live-fetch variants. * docs/ai-discoverability/README.md: added the Phase 5 row to the phase table. * AI-discoverability-architecture.md "Phase 5 outlook" rewritten — now points at the plan doc and summarises the five-track shape. This PR is plan-only — no enforcement gates ship here. Tracks A-E land as their own PRs per the calling convention in §8.
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.
Summary
Phase 5 first move per AI-discoverability-plan.md §6 + AI-discoverability-architecture.md §5 "Operational invariants". Authors the plan doc that the four enforcement gates will be built against. No enforcement gates ship in this PR — Tracks A–E land as their own PRs per the calling convention.
Phase 5 scope
Four enforcement gates, each watching one architectural promise that's currently held by maintainer discipline:
verified_onacrossrepo.meta.json+ recipesllms.txt+ every*_urlintools.json+docintask_index.jsonlicensevs LICENSE-file signatureschema_compatbumps on*.schema.jsonTrack layout
Five tracks. A–D are independent (no file overlap, no shared mutable state); any pair is safe to run in parallel. Each track ships:
profile/build/check-<gate>.py(TDD-covered)make check-freshness/check-links/check-licenses/check-schema-compat)PR-mode runs the
--offlinevariants (fast, no flake). Weekly cron runs the live-fetch variants on the same firing as the existing handshake-live cron.Track B carries a Phase 4 follow-up as B0: fix
validate-repo-meta.py's UTF-8-decode bug on binaryexposes.*URLs (the workaroundARGS=--no-resolveexists today; B0 removes the need).Phase 5 done definition
Seven criteria (plan §10). When all green, the framework's operational loop is complete — every architectural promise has an automated watchdog.
Other changes
docs/ai-discoverability/README.md— Phase 5 row added to the phase table.docs/ai-discoverability/AI-discoverability-architecture.md— "Phase 5 outlook" section rewritten to point at the plan + summarise the five-track shape.Test plan
make check-docs-prose— cleanmake recipes-check— 4/4 cleanmake handshake— 8/8 steps green