v3.2.0
v3.2.0 — M3: Decisions + Validations + Invariants
Goal: Decisions are recorded during Strategize and Execute phases and persisted to the database. Users can view the decision tree (plan tree), inspect individual decisions (plan explain), manage invariants (invariant add/list/remove), and correct decisions (plan correct --mode revert|append) with selective subtree recomputation.
Acceptance Criteria
- Decision records are created and persisted during Strategize and Execute phases
agents plan tree <plan_id>renders the full decision tree with dependenciesagents plan explain <decision_id>shows decision rationale, context snapshot, and alternativesagents invariant add/invariant list/invariant removemanage global, project, action, and plan-scoped invariantsagents plan correct --mode revert <decision_id>reverts a decision and recomputes affected subtreesagents plan correct --mode append <decision_id>appends new guidance without discarding prior decisions- Validation pipeline runs required and informational validations on resource-attached validations
agents validation attach/validation detachmanage validation attachments to resources- Definition-of-done gating blocks
plan applywhen validations fail inrequiredmode - Test coverage >= 97%
Technical Criteria
- Decision domain model with 12 decision types (prompt_definition, invariant_enforced, strategy_choice, subplan_spawn, etc.) and context snapshots persisted to SQLite.
- Influence DAG tracks downstream decision dependencies for selective subtree recomputation.
- Invariant precedence chain enforced: plan > action > project > global.
- Correction engine supports revert and append modes with BFS impact analysis.
- Validation pipeline distinguishes required (blocking) from informational (non-blocking) modes.
- Test coverage remains >= 97%.
44% Completed
Label
Project
Assignee
Sort