Files
whetstone_DSL/sprint97_plan.md

1.3 KiB

Sprint 97 Plan: Autonomous Patch Proposals with Human Approval Gates

Context

The system can now propose concrete fixes for adapter gaps, but must remain human-approved before production adoption. Sprint 97 adds patch proposal flow.


Goals

  1. Generate candidate adapter/policy patches from failure evidence
  2. Validate candidates in sandboxed certification loops
  3. Present diffs with semantic impact summaries
  4. Require explicit human approval for promotion

Steps

Step 1199: Patch proposal schema and provenance model (12 tests)

Step 1200: Candidate generation engine from failure taxonomy (10 tests)

Step 1201: Sandbox validation runner for candidate patches (10 tests)

Step 1202: Semantic impact estimator for patch diffs (10 tests)

Step 1203: Candidate ranking and recommendation model (10 tests)

Step 1204: Approval workflow integration with governance ledger (8 tests)

Step 1205: whetstone_generate_patch_candidates MCP tool (8 tests)

Step 1206: whetstone_validate_patch_candidate MCP tool (8 tests)

Step 1207: Patch proposal review report artifact (8 tests)

Step 1208: Sprint 97 integration summary + regression (8 tests)


Approval Rule

  • No autonomous patch is deployable without explicit approval record.