The framework document is the foundation. Everything else — the live build, the simulator, the zero-dependency deploy — is features built on top of it. Speed comes from the methodology being tight, not from skipping verification. Nothing carries the AION Verified badge before it has been red-teamed and audited.
Every engagement starts with a domain statement and a failure mode declaration. From those two inputs, the framework document is built first — always. The live build, the simulator, the embeddable widget: none of them are built on top of a brief. They are built on top of a verified framework document. That sequence is what makes the turnaround credible rather than reckless.
The AION Verified badge is not issued on delivery. It is issued after the prototype has passed three gates — in sequence, all mandatory. A prototype that fails any gate does not receive the badge. It receives a findings report and a revised scope. The badge is the evidence that all three gates passed. Not the claim — the evidence.
Every prototype type listed here has been built and delivered under the AION methodology. The methodology is domain-agnostic — the type of prototype changes, the verification standard does not. Where a type is not in scope, that is stated plainly below rather than discovered in the delivery conversation.
Pricing reflects what is being delivered — not the domain, not the client size. The framework document is the constant. The live build, the repository, the zero-dependency deploy are what the tier determines. All tiers include the full verification sequence before the AION Verified badge is issued.
The Roller Coaster Physics Simulator is the clearest demonstration of what the methodology produces: citation-backed physics, zero dependencies, fully interactive, red-teamed before badge issuance, running live with no maintenance overhead. It was not built as a portfolio piece. It was built because physics simulators used in safety contexts need to be verifiable — and the AION methodology is the verification infrastructure.
Every case study here is a documented engagement — not a hypothetical, not a demo. Real brief. Real timeline. Real verification record. The methodology either held or it didn't. The record says which.
That is the entire intake requirement. A clear domain statement and a willingness to specify what the prototype must not do wrong. The scoping conversation takes less than 30 minutes. The framework document follows in 24–48 hours.
All engagements via LinkedIn DM.
No RFP. No brief template. Just the domain and the failure modes.