The specification we deliver against
Every engagement is built against a document with this structure, reviewed and signed before a line of production code is written. It is the artefact you hold us to, so we publish its shape here.
Auric North · System specification · template
[System name to be supplied]
1. System overview & context
What the system is for, who depends on it, and the constraints it must live within. Written so a new engineer, or a procurement reviewer, can orient in one reading.
- Problem statement · [to be supplied]
- Stakeholders & dependents · [to be supplied]
- Constraints (regulatory, technical, operational) · [to be supplied]
2. Data contracts
Every dataset and interface the system consumes or produces, with schema, ownership, freshness and quality guarantees stated explicitly.
- Contract register · [to be supplied]
- Schema definitions & versioning policy · [to be supplied]
- Ownership & escalation per contract · [to be supplied]
3. Failure modes
What can go wrong, how the system behaves when it does, and how operators find out. Each mode carries a detection method and a rehearsed response.
- Failure mode register · [to be supplied]
- Degradation behaviour per mode · [to be supplied]
- Alerting & rollback procedure · [to be supplied]
4. Acceptance criteria
The definition of done, written precisely enough to be tested. Delivery is complete when these pass, and not before.
- Functional criteria · [to be supplied]
- Non-functional criteria (load, recovery, security) · [to be supplied]
- Verification method per criterion · [to be supplied]
5. Sign-off
Named individuals on both sides commit to the scope above. Changes after sign-off are renegotiated in writing, not absorbed silently.
- Client signatory · name, role, date
- Auric North signatory · name, role, date
- Change control procedure · [to be supplied]
A sanitised specification from a real engagement will be available for download here. [PDF to be supplied]
Tell us what must not go wrong.
Bring us the system that keeps you up at night. The first conversation is technical, and the first artefact you receive is written.
Book a 30 minute call