Cross-Domain
Grants Is the First Domain This Was Built For. It Is Built to Change Many.
The grants standards inherit their rigor from two standards that know nothing about grants. CRAFT makes a domain's data checkable. WALKRI makes any field an instrument. This is cutting-edge precision-standards work, not a generic layer, and grants is only where it was proven first.
The same machinery is built to bring that rigor to any field that takes in claims and has to decide on them, and that work is only beginning.
The Meta-Standard
CRAFT
Chains Reveal Attested Falsifiable Truth. Any system that takes in information to make a decision has the same weak point: the path from the world to the decision runs through stages where a judgment can go wrong invisibly, so the final output looks sound while resting on a break upstream. CRAFT calls this , by analogy to chain of custody for evidence. If any hand the evidence passed through is undocumented, it is inadmissible, however genuine it is.
is only the input-stage version of this. CRAFT covers the whole chain, not just the front door.
Its core move is . You cannot refute what you cannot inspect, so a chain becomes checkable only when every stage can be read off the published specification alone, with nothing load-bearing left in a private process. That is what it means to make a domain's data checkable.
The Six Conditions
Decision Context
State the decision, the parties, the population, and what is being estimated, before any data is collected.
A Technical Ontology Adequate to It
Define the terms precisely enough that the decision context can actually be expressed in them.
Valid Measurement Instruments
Use measures that actually capture what the ontology names, not labels that stand in for them.
Pre-Specified Criteria
Fix what counts as passing before the answers arrive, not after.
Explicit Decision Logic
Write the rule that turns the assessment into a decision, rather than leaving it implicit in a process or in code.
Feedback With Propagation
Carry what each cycle learns forward, so a correction at one stage reaches the stages it affects.
Field and Instrument Quality
WALKRI
Working Architecture for Legible, Knowable, Reliable Instrumentation. WALKRI is the standard that turns a label into an instrument. A question that cannot be answered wrongly is not measuring anything; WALKRI specifies what a question must carry before it counts as a measurement, so that two people reach the same reading from the same evidence.
What an Instrument Has to Carry
Criterion Intent
what the question is actually trying to establish
Operational Definition
the precise rule that decides what counts
Response Form
the shape an admissible answer has to take
Evidence Form
what proof must travel with the answer
Conformance Threshold
where the line between passing and not is drawn
And What the Data Has to Hold Up As
Validity
it measures what it claims to
Integrity
it cannot be quietly tampered with
Precision
it is exact enough to act on
Reliability
it gives the same reading on the same input
Timeliness
it is current enough to trust
The Rigor Sandwich
The Bread Never Changes, Only the Filling Does
CRAFT and WALKRI are the bread: the same rigor in any domain. Whatever field you work in slots into the middle. Grants is simply the first filling built.
CRAFT
the meta-standard · cross-domainMakes a domain's data checkable: legibility before refutability, across six conditions.
CROSS
grants · normativeWhat a grant round must commit to before applications open.
GRAIN
grants · abstraction layerOne shared representation of a grant that everything above it reads the same way.
WALKRI
field and instrument quality · cross-domainMakes any field a measurement instead of a label.
Swap the filling and the bread still holds. Grants is the first filling built; another domain slots into the same two standards. That is what cross-domain means here.
The Source Boundary
ORE
Origin, Reliability, Exposure. CRAFT covers the whole chain; ORE is its companion specification at the front door, for the sources a chain did not create. Sources are graded as uncertainty rather than judged as quality, and every output wears the grade profile of what it rests on. The source boundary →
Why It Reaches
Neither standard mentions grants. CRAFT says what any rigorous standard must do, and a domain fills it in; WALKRI says what any field must carry to produce data instead of noise. The same six conditions and the same instrument discipline could ground a standard for clinical trials, academic peer review, or supply-chain integrity, each built by analyzing that field's own failure modes. Grants is the proof of concept. The reach is the point.
Ahead of Formal Verification
The Specification Layer, Where the Real Failures Live
Formal verification proves an implementation does what its specification says, and it takes the specification as given. A proof against a flawed spec is a faithfully verified flaw: the system provably does what it was told, when what it was told was wrong. The break is in the spec, upstream of anything the proof can see.
CRAFT sits ahead of that, on the specification itself: legibility before refutability, you cannot verify what you cannot inspect. WALKRI does the same on a single field, a proof can show a measurement is computed exactly as defined, but only validity asks whether the definition captures the real thing. Faithfully computed, faithfully wrong.
This is why it is a security approach, not just a quality one. The costliest failures are not implementation bugs a proof catches; they are specification failures, value lost above the layer that cryptographic verification, oracle networks, and formal methods all operate at. CRAFT and WALKRI are the discipline at that layer. They do not replace verification; they make the thing it verifies worth verifying.