docs(governance): 📝 add operational implementation plan with exit gates and stop conditions#49
Merged
justapithecus merged 4 commits intomainfrom Mar 18, 2026
Conversation
…es and stop conditions IMPLEMENTATION_PLAN.md is the operational companion to MILESTONE_PLAN. It encodes what the milestone plan does not: - Concrete acceptance criteria per phase - Schema freeze ritual (canonical JSON fixtures in Phase 0) - Test strategies with specific test patterns - Exit gates with measurable criteria - Dogfood schedule (Bonsai self-dogfood + Futureson manual spike) - Kill criteria for staged execution (>30% wall-clock regression) - Product-level stop condition for adapter expansion - Evidence digest requirement for prompt reinjection - Stage cap enforcement (≤3 stages in default bundles) - Output discipline (grouped by source type, not fully intermixed) - contract_refs timeline (functional from Phase 2, not Phase 5) Also updates MILESTONE_PLAN: - Phase 1 narrowed to 3 adapters (gitleaks, golangci-lint, generic) - Phase 1.5 added: Semgrep adapter + Futureson spike - Version mapping updated Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…y milestone labels - Version mapping: labels are internal milestones, not release tags. Actual releases use strict vX.Y.Z per CONTRACT_RELEASE. - Futureson dogfood: advisory (recommended signal), not mandatory (release-blocking gate). Bonsai's roadmap must be reproducible from this repo alone. - Self-dogfood (Bonsai) remains mandatory at every phase. - Phase 6 prereqs: Bonsai self-dogfood is sufficient; external repo dogfood is recommended but not required. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…e residual external gate - ADR_0006 + CONTRACT_TOOLS: Phase 1 is now 3 adapters (gitleaks, golangci-lint, generic). Semgrep and test-runner listed under Phase 1.5, matching MILESTONE_PLAN. - Phase 2 dogfood: no longer claims mixed tool+skill output — that requires Phase 3 staged executor. Phase 2 only proves skill findings are in unified schema. - Stop condition: "Bonsai and Futureson" → "Bonsai (and optionally external repos)". External dogfood is advisory throughout. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…plementation plan CONTRACT_POLICY_EXECUTION and ADR_0005 still said ≤4 stages while IMPLEMENTATION_PLAN enforced ≤3 via tests. Unified to ≤3 everywhere. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
justapithecus
deleted the
worktree-andrew/docs/governance/implementation-plan
branch
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
Adds IMPLEMENTATION_PLAN.md as the operational companion to MILESTONE_PLAN.md. Where the milestone plan defines what to build per phase, this document defines how to verify it works, when to stop, and where to dogfood.
Highlights
Test plan
🤖 Generated with Claude Code