Why: W3 remainder is implemented on RDM draft PR #451 and needs the user's stage 6 review before merging into the initiative.
Evidence: RDM f3fa0c0 target tests and domain/rdmapp packages pass locally (SELF); fresh-session review PASS-with-fixes with no blocking findings.
Impact: task cards and review docs only; placement checks recorded as a W4 write-entry prerequisite.
Refs: feature/rdm-two-trees-followup-w3-rest, RDM PR #451
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=2b7fdc39a1f44163f4766701429d61ffd6926f1a.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The two-trees follow-up initiative needs its first increment (W0 catalog
guard, dynamic svc test ports, W3 gap check) packaged for user stage 6 review.
Evidence: Targeted unittest run on 000a2d2 recorded in the task card (SELF);
PR CI on the final HEAD is the GATE.
Impact: Task card and review spec only; implementation landed via agent-exec
transport 000a2d2.
Refs: .task/feature-rdm-two-trees-followup.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: RDM and Frontend units must implement one citation interface.
Evidence: Derived from the merged U6 evidence batch model (RDM 703e41d) and current cockpit/inspect read models.
Impact: Spec only.
Refs: docs/superpowers/plans/2026-10-18-regulations-knowledge-base-plan.md U7
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: U1 of the regulations KB plan requires a verified import inventory before any schema or ingestion work.
Evidence: dump sha256 matches manifest; 2878/2907 originals hash-verified in a disposable pgvector container (SELF).
Impact: Spec only; no corpus data or product code changed.
Refs: docs/superpowers/plans/2026-10-18-regulations-knowledge-base-plan.md U1
Co-authored-by: Cursor <cursoragent@cursor.com>
Why:
Provide phased rollout roadmap (Phases 1-5) for stock repositories and mandatory defaults for new projects under governance v2.
Evidence:
Specification documented in docs/superpowers/specs/2026-10-16-stock-repos-adoption-matrix.md.
Impact:
Clarifies U6 and U7 governance deliverables for multi-repo rollout without ambiguity.
Refs:
feature/development-governance-v2
Why:
Audit differences between Agent-System-Dev agent_exec.py and Development-Manager runner.go to clarify layer responsibilities for governance v2.
Evidence:
Architecture specification document created in docs/superpowers/specs/.
Impact:
Provides guidance for U3 shared executor convergence without duplicating logic across repositories.
Refs:
feature/development-governance-v2
Why: user approved the four design documents and authorized implementation
(/goal); the plan's section-7 tradeoffs gate the I1 public DTO and had to be
frozen before any implementation unit starts. A read-only audit of the RDM
backend (Agent-System-RDM main 5df66106) supplied the source facts.
Evidence: audit findings recorded in rollout section 7 (tree is doc->section
only, no confidence field, no persisted conflict entity, per-project event seq
complete); review fixes folded into the read-model contract (statReasons,
structuralGap, AssertionSummary); precheck receipt READY imported via
task-resume.
Impact: unlocks I1 implementation in the RDM repo; design deliverable ready
for PR/CI/merge; no business code, pins, database or deployment touched.
Refs: .task/feature-document-visualization-plan.md
Why: Let each project route expensive implementation work across available Agent CLIs while the host model retains planning and delivery control.
Evidence: The specification passed placeholder, consistency, scope, path, and whitespace self-checks; implementation and runtime validation remain NOT_RUN.
Impact: Defines a review-only R1-R10 design for Markdown configuration, adapters, run-everything execution, receipts, recovery, and host fallback without enabling the new route.
Refs: .task/feature-goal-first-delivery.md
weichenandCursor