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 dependencies
  • agents plan explain <decision_id> shows decision rationale, context snapshot, and alternatives
  • agents invariant add / invariant list / invariant remove manage global, project, action, and plan-scoped invariants
  • agents plan correct --mode revert <decision_id> reverts a decision and recomputes affected subtrees
  • agents 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 detach manage validation attachments to resources
  • Definition-of-done gating blocks plan apply when validations fail in required mode
  • 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%.
2026-02-26
44% Completed
fix(resources): fix resource_kind field to use physical boolean per spec and add cloud resource types
Some checks failed
CI / lint (pull_request) Failing after 53s
CI / quality (pull_request) Successful in 1m30s
CI / typecheck (pull_request) Successful in 1m38s
CI / security (pull_request) Successful in 1m37s
CI / coverage (pull_request) Has been skipped
CI / helm (pull_request) Successful in 25s
CI / build (pull_request) Successful in 32s
CI / push-validation (pull_request) Successful in 33s
CI / integration_tests (pull_request) Failing after 3m45s
CI / e2e_tests (pull_request) Successful in 3m38s
CI / unit_tests (pull_request) Failing after 15m19s
CI / docker (pull_request) Has been cancelled
CI / status-check (pull_request) Has been cancelled
auto/needs-reevaluation
MoSCoW
Must have
Priority
Medium
State
Paused
Type
Bug
#10647 opened 2026-04-19 00:20:24 +00:00 by HAL9000 1 change request 3 conflicting files