what you receive · the specification

Not notes on a wish.
A spec you can audit.

The audit-grade specification is the artifact a Praxis run hands you. Every requirement numbered, measurable, and traced back to the sentence it came from. Line by line, it holds up.

Request access
what it is

The one thing everything else answers to.

A normal spec is a document someone wrote once and nobody reads again. This one is the contract the whole pipeline runs on. The checks are built from it, the code is written to it, the deploy is read out of it, and the production signals are tied back to it. Change the spec and everything downstream knows.

what's in it

Every line carries its receipts.

numbered requirements
Each requirement gets an id and a measurable target. Not "the app should be secure", but a statement you can hold the work to and check off.
a source for each
Every requirement points back to the clause it came from. You can follow the thread from a line in the spec to the sentence in the ask, and back.
an assumptions register
What the spec takes for granted is written down, in the open. The ground the estimate stands on is visible, not buried in someone's head.
gaps named, not guessed
What the ask didn't say is left as an open question, flagged for you to answer. The model does not quietly fill the blank and build on it.
a status on every line
Stated, assumed, or open. You can see at a glance what is settled and what still needs a call, before anyone commits to a price or a date.
the spec, up close

A few lines. Their whole trail.

A slice of a real spec. Each line has an id, a measurable requirement, the clause it came from, and the check that proves it. The one still open is a gap named, not a blank quietly filled in.

why "audit-grade"

Hand it to someone who trusts none of it.

Audit-grade is not a compliment we pay it. It is a test it passes. You can hand this document to an evaluator, a regulator, or a sceptical client, and they can check it themselves without taking a single line on faith.

If the source didn't say it, the spec doesn't claim it.

And the same three checks that guard the code guard the spec. The maker writes it, a pilot re-checks every line against the ask, and a watcher outside the system holds back anything that can't show where it came from.

See the three checks
where it comes from, where it goes

Made once. Read the whole way.

Capture is the stage that writes it, out of a rough ask. From there it is not a document that gets filed. It is the live contract the rest of CRAFT reads from, all the way to a signal in production.

See how it's made See the whole pipeline