Phase spec — skeleton
Download the MarkdownSkeleton_Phase_Spec.md · 1.8 KB · from The delivery method
Headings and field lists only. Re-typed from the delivery SOP used on a sovereign OSINT platform built for a defence innovation challenge; no content from that or any other project.
Rules the skeleton enforces. Written before any code. Non-functional targets are declared now and measured live before sign-off. The evaluation floor is pinned before implementation; a missed floor is reported, never quietly absorbed. A spec is never written to justify work already done.
Status
One of: draft, approved for build · built, awaiting sign-off · signed off — with approver (role) and date.
Never "complete" before sign-off.
Objective
Why the phase exists, framed for the end user.
Design decision · scope decision · model choice
- Design decision: the key choice, named.
- Scope decision: what is deliberately deferred, and why (recorded so it is not re-litigated).
- Model or technology choice: what, and the reason.
What must be true — the contract
- Interfaces
- Data shapes
- Validation rules
- Acceptance criteria (each one falsifiable)
How it will be built
- Components
- Sequence of operations
- Integration choices
Out of scope
What is recorded for later.
Non-functional targets
| Target | Numeric bar | Scale it applies at | Measured value (before sign-off) |
|---|---|---|---|
| Latency (percentile) | |||
| Throughput | |||
| Restart and replay integrity | |||
| Index coverage | |||
| Backpressure | |||
| Storage growth |
Evaluation plan
| Dataset | Metric | Floor (pinned now) | Measured |
|---|
Exit checks
The literal script run before sign-off. Each check names its mechanism. "Tests pass" is not an exit check.
Sign-off
Date · approver (role) · measured values · demo reference · tag.