VATS™
Evidence Readiness for AI
Prove what trained your AI—and disclose honestly what you cannot prove.
VATS creates tamper-evident, independently verifiable records of how an AI model was built—the datasets, transformations, training events, versions, and declared gaps. Records created when the work happens, not reconstructed when someone asks.
Demo 001 — Baby Shakespeare
A 117,888-parameter AI trained from scratch on Shakespeare. Its full lineage—corpus, weights, certificate—is confirmed on Bitcoin mainnet and published to Arweave permanently.
COMMONS-VATS-001 — Specification Record
BTC chain-tip metadata
Block 952,835
Recorded at anchor creation — not an OP_RETURN commitment
Bitcoin commitment
PENDING
No OP_RETURN confirmed for this record yet
What anchoring proves
A Bitcoin anchor might prove that a particular fingerprint existed no later than a certain time. It does not, by itself, prove authorship, accuracy, lawful possession, contractual assent, or the truth of the underlying document.
Three Reasons Teams Anchor
Trust
Today
For startups, researchers, and open-source developers who want to show exactly how their model was built.
Auditors ask.
Users ask.
Partners ask.
Your answer becomes a documented lineage—not a reconstruction.
- ·Training lineage
- ·Dataset declarations
- ·Version history
- ·Declared limitations
- ·Independent verification
Evidence
Today
For commercial AI vendors answering procurement questionnaires and standing behind contractual representations.
VATS does not reduce legal risk.
It improves evidentiary posture.
It creates:
- ·Contemporaneous documentation
- ·Tamper-evident records
- ·Reproducible lineage
- ·Independent verification
If your training process is ever questioned, your documentation already exists.
Compliance
Ahead
Documentation requirements continue to expand across AI governance frameworks.
Evidence cannot be created retroactively.
Records you do not create during development become gaps you must explain later.
Regulatory deadlines move. Evidence windows don't.
Evidence Readiness
Cybersecurity taught organizations incident response:
Prepare before the breach.
Preparation after the breach isn't preparation.
AI now requires its equivalent.
Evidence Readiness means the documentation describing how your model was built exists before anyone asks—a customer, an auditor, procurement, opposing counsel, or a regulator—and remains tamper-evident and independently verifiable.
That's what VATS produces.
Not a promise about outcomes.
An evidence path.
When Procurement Asks
Enterprise AI procurement increasingly asks questions such as:
- —How is training data governed?
- —Can you document model provenance?
- —How do you maintain traceability?
- —Can an independent party verify your documentation?
A VATS record answers with:
- Declared artifact states
- Dataset declarations
- Lineage history
- Declared gaps
- Verification instructions
The answer stops being a promise.
It becomes a documented path.
Demo 001 · Meet Baby Shakespeare
Meet Baby Shakespeare.
A 117,888-parameter character-level model trained from scratch on The Complete Works of William Shakespeare.
Pure NumPy. One CPU. 8 minutes and 1 second of training.
He did not learn to write like Shakespeare.
He learned character names, dialogue formatting, punctuation rhythms, and fragments of English structure. His attention weights were frozen, so the honest description is: a character-frequency model inside a transformer-shaped architecture. Modest by design.
Is he good?
Wrong question.
He is a baby. He babbles — which is exactly what training with frozen attention should produce. He knows the shape of the language before he knows the language.
Baby Shakespeare — Demo 001
117,888 params · NumPy · 1 CPU · 8 minutes, 1 second of training
He did not learn to write like Shakespeare. He learned character names, dialogue formatting, punctuation rhythms, and fragments of English structure. His attention weights were frozen — honest description: a character-frequency model inside a transformer-shaped architecture. Today he mostly speaks nonsense. That is exactly what he should do.
The model is not the point.
The question is: can a stranger who was not in the room reconstruct what happened without simply trusting us?
Section 2
What the Record Proves
VATS separates evidence from assertion.
What Demo 001's preserved record establishes
- The source, corpus, split files, manifest, weight file, and certificate artifacts either match or do not match their sealed SHA-256 hashes.
- The preserved transformation sequence can be inspected.
- The declared configuration and environment can be examined.
- The published records can be retrieved independently of the ICPO X website.
- Demo 001's preserved artifacts can be checked against their sealed hashes and replayed under the specified environment.
- Independent third-party reproduction remains open and has not yet been completed.
What the record does not establish
- —That the Training Intent Manifest existed before training without relying on ICPO X's internal database chronology. Its Bitcoin commitment followed the run; that ordering is disclosed.
- —That an anchor makes source data accurate, lawful, licensed, authorized, complete, or ethically obtained.
- —That every declared training event occurred exactly as described merely because its declaration was committed.
- —That a large model learned only from a declared dataset.
- —That the method was optimal.
- —That VATS establishes legal or regulatory compliance.
The public record preserves both the result and the gaps.
Artifacts missing from an original run remain declared missing. Corrections extend the record. They do not rewrite the past.
Section 3
Products and Pricing
Fees are sovereign service fees for evidence design, anchoring, publication, and registry operations.
THE ANCHOR — One-time evidence services
Dataset Anchor
$7,500
one-time per dataset record
Available
- SHA-256 commitment to the approved dataset state
- Hash-only Arweave evidence envelope by default
- Bitcoin OP_RETURN commitment after final customer authorization
- Commons Anchor ID + independent verification instructions
- Public commitment status + correction lineage
Lineage Certificate
$35,000
one-time per initial model certificate
- Up to 10 previously approved Dataset Anchors
- Model and training-event manifest
- Declared evidence and gap record
- Cryptographically sealed JSON Lineage Certificate
- Arweave publication + Bitcoin OP_RETURN at issuance
- Public registry record + verification instructions
This fee covers the initial certificate. Each registered fine-tune requires a child certificate, separately scoped and billed unless included under an active annual program.
THE PROGRAM — Optional annual services
Layered on top of the permanent evidence records. The annual program does not control whether underlying commitments remain valid or independently checkable.
VATS-LITE
$12,000/year
For independent labs, researchers, and single-model teams.
- One registered model
- Registry Node ID + VATS participation badge
- Protocol review + public audit trail
- Scheduled record review
Dataset Anchors and Lineage Certificates purchased separately unless a written proposal states otherwise.
VATS-PRIME
Flagship$120,000/year
For AI labs, multi-model teams, and regulated deployments.
- Up to 10 registered models
- Provenance-query API access
- Priority protocol review + public audit trail
- Scheduled record review
- Child-certificate allowance as defined in written proposal
Anchors and initial certificates purchased separately unless a written proposal states otherwise.
REGULATORY EVIDENCE PACKAGE
$250,000
flat-fee engagement
Designed to support documentation and evidence preparation for AI governance frameworks, including the EU AI Act where applicable. For operators preparing evidence packages for counsel, auditors, procurement teams, or internal governance review.
Final regulatory positioning remains subject to legal review. Does not determine whether an AI system is in scope, satisfy every applicable obligation, constitute legal advice, replace a compliance assessment, or establish regulatory conformity. Final scope depends on data classification, model count, legal review, and the evidence that actually exists.
Potential deliverables
· Up to 10 Dataset Anchors
· Initial Lineage Certificate per model
· Training Run Record schema
· Anchored training-event records
· Honest Gap Declaration
· Evidence index for counsel and auditors
· VATS-Prime membership, first year
· Direct founder engagement
Bitcoin accepted as payment for ICPO X services.
·
ICPO X does not custody customer crypto-assets or keys.
·
diplomacy@icpoxinc.comSection 4
How VATS Works
Register the Dataset State
Hash the approved dataset state with SHA-256. By default, publish only the cryptographic commitment, declared metadata, source and rights declarations, transformation information, and known gaps. The customer retains the underlying dataset. Full-content upload requires separate written authorization and is blocked for prohibited data classes.
Record the Training Event
Create a Training Intent Manifest before execution. Record approved dataset anchors, model and code version, environment, seed and deterministic settings, intended training steps, initial weights or initialization state, authority for the run, and known limitations. A registered run can produce an anchored training-event record. Anything not preserved must be declared.
Issue the Lineage Certificate
After the required artifacts are persisted and hashed, create a sealed JSON record describing the subject model, datasets and prior records, training-event evidence, resulting weights or model artifact, verification instructions, declared gaps, and correction and version lineage. Each registered fine-tune creates a child record linked to its parents.
Register the Result
Publish the approved evidence envelope to Arweave. Commit its hash to Bitcoin via OP_RETURN. Register the resulting evidence state in the VATS registry. Corrections create new linked records. They do not overwrite earlier states.
Section 5
The Birth Record
Source bytes
→ normalized corpus
→ train/validation splits
→ Training Intent Manifest
→ initial weights
→ training run
→ final weights
→ Lineage Certificate
Every preserved artifact has a SHA-256 hash.
The corpus catalog and provenance records are published on Arweave.
Bitcoin chain-tip metadata and Bitcoin commitment status are disclosed separately rather than blended together.
And here is the standard:
Under the specified environment, a result that does not match the sealed weight hash defeats the relevant reproducibility claim.
The discrepancy then becomes part of the record rather than something concealed. Independent third-party reproduction is open.
Verify It Yourself
No account. No API key. No dependence on the ICPO X website.
Fetch the Arweave record
The record exposes the commitment envelope and its snapshot hash.
https://arweave.net/n3_kK787awYvGSnh9SDhG7FVlj2HR99lzHr2OUrmQpQ
Check Bitcoin status
PENDING: No Bitcoin commitment has yet been confirmed for this record. Bitcoin block 952,835 is chain-tip metadata, not an OP_RETURN commitment.
Convenience check (trusts ICPO X server)
The independent path is the Arweave record, SHA-256 verification, and the actual Bitcoin transaction when confirmed.
https://www.icpoxinc.com/api/qisl/commons/verify/COMMONS-VATS-001
Section 6
What a Bitcoin Commitment Proves
A Bitcoin commitment establishes that a particular hash was included in a transaction no later than the block containing that transaction. When an artifact presented later produces the same hash, a verifier can confirm that its bytes match the committed state.
That is what the commitment establishes.
It does not establish
Dishonesty remains possible.
VATS makes declared claims, known gaps, corrections, and later contradictions harder to erase.
A changed hash does not prove a lie. It proves a discrepancy.
The discrepancy must then be explained. We applied that standard to our own demonstration before asking customers to adopt it.
Section 7
The Lineage Receipt
Not an accredited conformity certificate.
Not a legal opinion.
Not proof that the underlying claims are true.
It is a cryptographically sealed JSON evidence record describing what was submitted, what was preserved, what was committed, what remains unproven, and how to verify the record.
Illustrative Schema — Not a Live Customer Certificate
{
"protocol": "ICPO X VATS - Lineage Record",
"spec_version": "VATS-2.0",
"record_id": "VATS-EXAMPLE-001",
"pq_algorithm": "ML-DSA-87 (FIPS 204)", // signed - substitution defense
"key_version": "ICPOX-001-K1", // signed - check key inventory
"disclaimer": "Cryptographic proof of existence and signing - not proof of factual truth, authority, identity, or safety.",
"is_canary": false,
"issued_at": "YYYY-MM-DDT00:00:00.000Z",
"issued_by": "ICPOX-001",
"subject": {
"qisl_id": "ICPOX-EXAMPLE",
"model_name": "ExampleModel-1",
"model_org": "Example Labs"
},
"evidence": {
"dataset_anchors": ["COMMONS-EXAMPLE-001"],
"training_event_record": "VATS-RUN-EXAMPLE-001",
"model_artifact_hash": "sha3-256:a3f9c2e1..."
},
"honest_gap_declaration": [
"Training data before VATS registration is not independently evidenced.",
"The commitment does not establish lawful possession or authorization.",
"No regulatory conformity determination is made."
],
"pq_signature": {
"algorithm": "ML-DSA-87 (FIPS 204)",
"hash_algorithm": "SHA3-256",
"canonicalization": "RFC 8785 (JCS)",
"signing_context": "VATS-2.0", // FIPS 204 ctx parameter
"public_key": "EXAMPLE_BASE64_1952_BYTES",
"public_key_sha3_256": "FINGERPRINT_VS_KEY_INVENTORY",
"signature": "EXAMPLE_BASE64_3309_BYTES",
"content_sha3_256": "HASH_OF_CERT_WITHOUT_THIS_BLOCK"
},
"publication": {
"arweave_tx": "EXAMPLE_TX_ID",
"bitcoin_status": "pending_or_confirmed",
"bitcoin_txid": "EXAMPLE_IF_CONFIRMED",
"confirmation_block": "EXAMPLE_IF_CONFIRMED"
},
"verification": {
"standard": "COMMONS-VATS-001",
"instructions": [
"Retrieve the record from Arweave. Report each layer separately.",
"L1: remove pq_signature, canonicalize (JCS), SHA3-256 -> content_sha3_256.",
"L2: verify ML-DSA-87 over the raw 32-byte digest, ctx = 'VATS-2.0'.",
"L3: match the embedded key's fingerprint against the anchored key inventory - the trust root. A valid-but-unauthorized key must FAIL.",
"L4: SHA-256 the complete JSON vs the Bitcoin OP_RETURN (chronology - not post-quantum)."
]
}
}SHA3-256 Sealed
A single-byte change produces a different hash, making silent alteration detectable. Keccak construction — no length-extension attacks.
Post-Quantum Signed
Every newly issued VATS-2.0 certificate carries an ML-DSA-87 (FIPS 204, Level 5) lattice signature, with the algorithm and key version signed into the certificate itself — no substitution, no downgrade. Correctly labeled ML-DSA-65 artifacts remain historical-verifier compatible only.
Anchored Key Inventory
The trust root is a published, versioned key inventory anchored to Arweave and Bitcoin — not the certificate's own embedded key. A valid but unauthorized key fails verification.
Proof, Not Truth
A signed disclaimer travels inside every certificate: the signature proves existence and signing — never factual truth, authority, identity, or safety of the claims.
Section 8 — Proof of Thesis
The Fabrication Incident
July 11, 2026
On July 11, 2026, the failure mode VATS is designed to address occurred during an external AI model session.
The model was asked to recall a prior gap declaration. It answered with confidence and produced a complete declaration as though it were remembered. The declaration was reconstructed from contextual patterns. No recoverable original had been found.
Before anything was made permanent, the verification step asked:
How did you recall this?
The model then acknowledged that it had reconstructed the text.
The fabricated declaration was not anchored as an original. The incident was documented instead.
A confident fabrication, made permanent without verification, would have created a durable false record. Verification changed the outcome. The missing original remains missing. Its loss is preserved as a gap rather than concealed by a replacement.
That is the thesis:
The system does not make AI infallible. It makes evidence states, corrections, and unresolved gaps explicit.
Section 9
Compliance and Procurement Use
AI developers and deployers may need to document:
- ·Training data and data sources
- ·Preprocessing and transformation
- ·Model versions
- ·Known limitations
- ·Record-keeping and change history
Traditional documentation is often held in mutable internal systems.
VATS is designed to support evidence collection and record integrity relevant to data-governance, technical-documentation, and record-keeping obligations.
It does not determine whether a system is in scope.
It does not satisfy every applicable obligation.
It does not establish regulatory conformity.
It does not replace legal advice, an audit, or a conformity assessment.
It changes the audit surface:
From mutable assertions to tamper-evident evidence records with independent verification paths.
Enterprise Procurement
When a purchaser asks: "Can you support what you say about your training data and model history?"
A VATS record provides:
- Committed artifact states
- Declared source and rights information
- Change lineage
- Known gaps
- Independent verification instructions
The answer is not merely a promise. It is an evidence path.
Section 10
How VATS Evidence Differs
| Property | Mutable internal documentation | VATS published evidence |
|---|---|---|
| Change detection | Depends on retained versions, permissions, logs, and institutional controls. | A byte change breaks the sealed hash and creates a detectable mismatch. |
| External verification | Usually requires access granted by the record holder or its auditor. | Published records can be retrieved and checked without an ICPO X account. |
| Dependence on the issuer | May depend on the institution or vendor continuing to host the record. | The public verification path does not depend on the ICPO X website remaining available. |
| Corrections | Prior versions may be replaced, overwritten, or difficult to reconstruct. | Corrections create linked records while preserving the earlier state. |
| Chronology | Depends on internal timestamps and system controls. | A confirmed Bitcoin transaction supplies an external temporal commitment to the submitted hash. |
| Privacy model | May keep sensitive content inside institutional custody. | VATS keeps the underlying dataset with the customer by default and publishes a hash-based evidence envelope. |
VATS complements documentation, audit, and certification processes. It does not replace them.
Section 11
The Specification Record
COMMONS-VATS-001 is the published record for this specific VATS specification artifact.
It does not establish that no earlier idea, method, or competing implementation existed.
Status
Arweave publication
June 8, 2026
n3_kK787awYvGSnh9SDhG7FVlj2HR99lzHr2OUrmQpQ
BTC chain-tip metadata
Block 952,835
Bitcoin commitment
PENDING
Snapshot hash
bdb90247c8ee9fa74ad867ef474a684f6b2e61c6fbf70311576c6393b95acf62
ICPO X earns fees for real services: specification stewardship, implementation, evidence design, anchoring, registry operations, verification support, correction lineage, and maintenance.
Section 12
ICPO X, Declared Honestly
One founder directed and authored the VATS specification and coordinated its implementation through AI-assisted development.
Current state — as of today
· ICPO X LLC has no employees and zero enterprise customers today.
· No regulator has endorsed VATS.
· No insurer has priced it.
· Independent third-party reproduction of Demo 001 remains open.
What exists:
- Public evidence records
- A working demonstration model
- Sealed artifacts
- Declared gaps
- A published verification path
- A commercial service ready for counsel-reviewed launch
The permanence architecture is not dependent on one company server. Approved evidence records are published to Arweave and, when broadcast, committed to Bitcoin.
We hold ourselves to the standard we sell.
Our demonstration declares what it cannot prove. So do we.