Commit Graph
5 Commits
Author SHA1 Message Date
weichen 714d641be8 Document stock repos adoption matrix and new project admission spec
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
2026-10-16 08:42:37 +00:00
weichen 24185ac066 Document shared executor architecture audit for 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
2026-10-16 07:16:07 +00:00
weichen d58d5bc1dd Review design docs and freeze cockpit contract decisions
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
2026-10-16 06:25:19 +00:00
weichen 5466f2cddb Document visualization cockpit design 2026-10-16 06:03:17 +00:00
weichen 5ff0a4d510 Design project-level execution agent routing
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
2026-10-15 01:45:15 +00:00