Edison Jwa
bba6273af7
- Move ASPICE docs to chanoraapp/docs submodule at docs/ - Move development docs to dev-docs/ (superpowers, offline-knowledge, impl-mapping) - Add AGENTS.md with project conventions for AI agents - Add impl-mapping.md (SAD component → source file mapping) - Archive completed plans to dev-docs/superpowers/plans/_archived/ - Remove AGENTS.md from .gitignore (now tracked)
69 lines
2.6 KiB
Markdown
69 lines
2.6 KiB
Markdown
# SWE.2/SWE.3 Baselines Implementation Plan
|
|
|
|
> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
|
|
|
|
**Goal:** Add reviewable SWE.2/SAD and SWE.3/SDD baselines so the DV document chain is no longer missing the architecture and detailed design layers.
|
|
|
|
**Architecture:** Keep SWE.2 in `docs/architecture/sad.md` and SWE.3 in `docs/architecture/sdd.md`, matching the README document tree. Update DV traceability and verification-plan wording to consume these baselines while preserving honest limitations for areas that still need deeper detail.
|
|
|
|
**Tech Stack:** Markdown, existing SysDes/SRS baselines, current Flutter/Rust workspace structure.
|
|
|
|
---
|
|
|
|
### Task 1: Write SWE.2 SAD Baseline
|
|
|
|
**Files:**
|
|
- Create: `docs/architecture/sad.md`
|
|
|
|
- [x] **Step 1: Create SAD with architecture views**
|
|
|
|
Write sections for purpose, upstream sources, components, static view, runtime flows, interface catalogue, dependency rules, non-functional allocation, architectural decisions, verification handoff, traceability, and open architecture risks.
|
|
|
|
### Task 2: Write SWE.3 SDD Baseline
|
|
|
|
**Files:**
|
|
- Create: `docs/architecture/sdd.md`
|
|
|
|
- [x] **Step 1: Create SDD with module designs**
|
|
|
|
Write sections for purpose, upstream sources, module catalogue, detailed API/data/state design, persistence, diagnostics, platform adapters, build/release design, verification hooks, traceability, and open detailed-design risks.
|
|
|
|
### Task 3: Update DV Traceability
|
|
|
|
**Files:**
|
|
- Modify: `docs/governance/traceability-matrix.md`
|
|
- Modify: `docs/verification/verification-master-plan.md`
|
|
|
|
- [x] **Step 1: Remove SAD/SDD missing limitation**
|
|
|
|
Update traceability text so it says SAD and SDD baselines exist, with known depth limitations instead of missing-document limitations.
|
|
|
|
- [x] **Step 2: Update verification plan inputs**
|
|
|
|
Update verification master plan to reference SAD and SDD as current inputs for SWE.4/SWE.5.
|
|
|
|
### Task 4: Verify SWE.2/SWE.3 Pack
|
|
|
|
**Files:**
|
|
- Inspect created and updated docs.
|
|
|
|
- [x] **Step 1: Sentinel-language scan**
|
|
|
|
Run the sentinel-language scan over `docs/architecture`, `docs/governance`, and `docs/verification`.
|
|
|
|
Expected: no matches introduced by this baseline pack.
|
|
|
|
- [x] **Step 2: File presence check**
|
|
|
|
Run: `ls docs/architecture`
|
|
|
|
Expected: `sad.md` and `sdd.md` are listed.
|
|
|
|
---
|
|
|
|
## Self-Review
|
|
|
|
- Spec coverage: creates SAD and SDD baselines and updates DV traceability consumers.
|
|
- Placeholder scan: no incomplete instructions are present.
|
|
- Type consistency: document names match README paths.
|