Implementation specs
Only the next actionable slice receives a detailed spec. Milestone-level intent lives in ROADMAP; workflow and authority live in SDD.
| Spec | Status | Baseline | Milestone |
|---|---|---|---|
| SPEC-001: packed consumer compilation baseline | Blocked | 9d2635e | M1 |
| SPEC-002: H3 consumer type closure | Blocked | f258fc3 | M1 |
| SPEC-003: Analog request lifecycle and Angular DI feasibility | In review | c671ba4 | M2 |
Two tracks run side by side. H3 consumer qualification (SPEC-001, SPEC-002): both were
executed and remain Blocked; SPEC-002's measured no-go is upstream-blocked by H3/crossws
declarations and does not close M1. Analog integration / Server Component feasibility
(SPEC-003): @strata-sc/analog never exposes H3 v2 declarations, so the H3 blocker does not gate it.
SPEC-003 is implemented with a CONDITIONAL GO and awaits Astra's acceptance.
Use sequential IDs and descriptive filenames. A spec is authoritative for that slice's intended behavior, not for the framework's entire future. Keep no more than one Ready/In progress spec.
Required template
Each spec starts with ID, title, status, baseline, milestone, owner roles, dependencies and related ADRs/risks, followed by these sections:
- Context — current source and evidence; distinguish implemented behavior from assumptions.
- Problem — one bounded missing capability or hypothesis.
- Goals — observable outcomes.
- Non-goals — adjacent work deliberately excluded.
- Public API impact — exact new/changed signatures or an explicit statement of no impact.
- Architecture — ownership, data flow, allowed file areas and fixed implementation boundaries.
- Constraints — dependencies, runtime/compiler rules and forbidden shortcuts.
- Acceptance criteria — numbered, verifiable outcomes with failure behavior.
- Required tests — map test cases and commands to acceptance IDs; include negative controls.
- Compatibility concerns — exact starting tuple, affected peers and unproven targets.
- Risks — relevant register IDs and what this slice can/cannot resolve.
- Definition of Done — code/test/review evidence and documentation updates.
- Explicitly out of scope — a final implementation guardrail.
Add alternatives and decision rules for a spike. Specify its reproducible experiment and what a no-go report must contain. Do not ask a small implementation agent to invent the architecture. When accepted, append result/PR/evidence links and deviations; preserve the original intent. Keep unrun checks visible and do not label a completed investigation as a proven production capability.