The Standard · NXC-A02 · proprietary

Readings a government can check.

A standard for auditable reference states: what one is, the six states a query can exit through, the six requirements a conformant collection must meet, and the boundary that keeps it honest. Ours. Disclosed to clients in confidence.Verified

Document NXC-A02Version v2.1Revised 9 Sep 2026Status ALIGNEDEngine v17.23Classification Proprietary · disclosed under engagement
§ 01 The minister's question
Why a standard, and not a dashboard

Which source. Observed when. Coded by whom. Checked how. Superseded by what.

Fig. — The card index · every claim keeps its card

A government commissioning a view of its own economy is usually offered a dashboard. A dashboard is a display surface: it shows numbers, and it is silent about what stands behind them.

When a minister is asked, in public, why a tile said what it said — which source, observed when, coded by whom, checked how, and superseded by what — the dashboard has no answer, because nothing in its construction required one. The failure that follows is never "bad data" in the abstract. It is always a specific sentence, in a specific published surface, that the evidence no longer supports — discovered by someone else first.

A reference state is built so that question can always be answered. Every claim carries its evidence, its dates, its checker and its status. A dashboard may sit on top of it — but every tile inherits an answer-state from the record beneath, and shows it as plainly as its value.Verified

The boundary
"We certify answerability, not truth."
No standard can certify that a system's claims are true of the world. What can be tested is whether a system knows what it may say, says no more than that, and refuses the rest in a governed way. Every clause is a property of the system — which is why a third party can check it.
§ 02 Six ways to answer
The instrument

Every question exits through exactly one state.

Ask a reference state anything and it returns two things: an answer, and a declaration of what kind of answer it is. "Cannot answer" stops being a conversational shrug and becomes a governed output. Six states. Set them yourself.

ANSWER-STATE Answerable A1
Fig. — The instrument
Click a state to set it
NXC-A02 · engine v17.23
A1
Answerable
A2
Qualified
A3
Contested
A4
Insufficient
A5
Stale
A6
Out of scope
Names only. What each state requires, and where its thresholds sit, is disclosed under engagement.
Three scenes — illustrative, not readings
You ask
Which institutions set the terms for a supply chain your programme depends on?
The record answers
A structured reading — who conditions whom, and through what.
And declares
A2 · Qualified — with two limitations returned alongside it, in writing.
You ask
The same question, about a period after the record's observation window.
The record answers
It does not. It says why.
And declares
A5 · Stale — with the refresh that would change it.
You ask
What will happen next year?
The record answers
It does not, and it does not pretend to. Structure is not causation.
And declares
A6 · Out of scope — a prediction is not a relationship class the record represents.
Scenes are illustrations of the taxonomy, not readings. No reading is published.
Fig. — The dial · a standard is a measuring instrument
§ 03 Six questions a record must be able to answer
Conformance

Never the word "certified."

Conformance is stated for a declared scope, never as a blanket. A conformant collection has to be able to answer six questions about itself. The questions are here. What counts as a passing answer is disclosed under engagement.

R1 · Declared scope
What does this record cover — and what does it not?
R2 · Provenance
Where did each claim come from, and who checked it?
R3 · Temporal integrity
When was this true — and when did that stop being so?
R4 · Independent verification
Who checked the person who coded it?
R5 · Governed refusal
What happens when the evidence isn't there?
R6 · Reproducible evaluation
Does it fail in both directions — answering everything, and refusing everything?
§ 04 Ours, and disclosed
The line we hold

The standard is not published. It is demonstrated.

The taxonomy, the requirements, the collection architecture and the implementation that codes to them are Nixus's own. They are shown to clients in confidence, and what we commit to under them — conformance, for a declared scope — is committed in writing under the engagement.Verified

A conformant collection is built from three layers of evidence, each with its own provenance and verification discipline, and separates decision-grade readings from restatements of the input by testing every measure against a null. Readings produced under it are demonstrated, not published.

"This conclusion was not written.
It was measured."
A standard is a measuring instrument. What it measures, and to what tolerance, is shown in the room.
§ 05 Document control
Reference
Nixus Intelligence (2026). Collecting an Economy. NXC-A02, v2.1, 9 September 2026. Engine alignment v17.23. In confidence.
Revision history — append-only
v2.19 Sep 2026First canonical issue.
v21 Sep 2026Second draft.
v11 Sep 2026First draft.

Superseded versions are retained, not overwritten.