feat: promote draft decisions when creating plans

Promote referenced drafts deterministically with system provenance, causal
Plan links, supersession history and recovery from publication failures.
Preserve direct human approval and historical records.

Add JVM and native regression coverage and update the portable protocol.
Record the WRK-0007 importer decision and six-step plan, and complete
WRK-0008 with verification evidence.
This commit is contained in:
Nilton Constantino
2026-11-16 12:35:06 +00:00
parent 95c28e2e79
commit 3d2abb487f
101 changed files with 5322 additions and 14 deletions
+15
View File
@@ -183,6 +183,13 @@ in history. Use `decision revise` for a new draft based on a prior accepted/reje
decision; acceptance supersedes the prior accepted decision while retaining history.
Accepted decisions cannot be silently edited. Use `--by` and `--reason` on changes.
Creating a Plan from a DRAFT decision promotes it automatically. This deterministic
framework action needs no LLM or preceding `decision accept` command. It records
`origin: SYSTEM_PLAN`, the causal `planId`, actor `system:planning` and
`humanApproved: false`, preserving history and any supersession. It is distinct
from the explicit human-attestation route above. Drafts still need nonblank context,
approach and rationale; rejected/superseded decisions remain invalid Plan inputs.
## Planning and adaptive execution
Use `plan create WRK --title TEXT [--decision DEC]`, then `plan step add` for a
@@ -191,6 +198,14 @@ records OPEN, ACTIVE, BLOCKED, COMPLETED or CANCELLED. Dependencies must be comp
before starting dependent steps. Completed steps require a result (`--reason`) and
owned `--evidence ART`. Plan decisions must be accepted for execution.
`plan create --decision DEC` promotes its referenced drafts before returning the
new Plan. Already accepted decisions are unchanged. Inputs are validated together
under the project lock; ordinary publication failures roll back promotions.
Crash-interrupted publication may still need deliberate repair; use `work validate`
to inspect causal Plan links and revision history. `plan update` does not promote
drafts. Historical human approvals remain readable and are never rewritten into
system approvals. New system-promotion records require a CLI with this capability.
The CLI records work and can apply validated fixture proposals; it does not execute repository commands. Observe results,
reconsider hypotheses and replan explicitly when evidence changes. OODA is adaptive,
not a mandatory four-stage pipeline. No autonomous repository executor, orchestrator,