Evidence and diligence · not a funding claim
What is true today
SIMULATED PILOT — TESTNET CREDITS ARE NOT MONEY — NO CUSTOMER. Public demo means an anonymous synthetic walkthrough. It does not mean a buyer, an audit, or production custody.
Status: NOT AUDITED. Customer data: NOT READY. Rehearsal tenant rehearsal-testnet-local is a local label, not an account on a public ledger.
Status
- Anonymous synthetic demoAvailable on this siteYou can run Action Guard and Recovery without a wallet.
- Action GuardLocal synthetic demoMock provider only. MOCK_STAGED is not a merge.
- Recovery labLocal synthetic demoBrowser crypto on a synthetic file. Not a customer restore.
- File handoffPassPublic cards and releases move as files. The file text is not in the public pack.
- Three isolated browser profilesPassFive persistent browser profiles used separate storage. Secrets did not cross.
- Three-process ceremonyPassSeparate browser processes finished the file-only handoff on one machine. That is not three phones held by three people.
- Vault, seal, testnet deskExisting product surfaceTestnet HBAR and QVUSD are not money. A mirror file 404 does not mean the hash is missing.
- Live GitHub checkCheck run onlyA GitHub App can read a public or private repository and publish a check. No merge, no deploy, no secret read. MOCK_STAGED stays on the synthetic desk.
- Independent auditNot auditedA passing self-check is not a third-party review.
- Real customer dataNot readyNo named operator, signed scope, or data-handling approval.
- Paid pilot or fundingNot establishedA rehearsal tenant id is not a customer and not revenue.
Key lifecycle
A new synthetic file gets a fresh DEK. The owner wraps it with ML-KEM. A separate recovery root is split 2-of-3 and each share is wrapped to a guardian public key. Rotating the owner key rewraps the same DEK and leaves the ciphertext digest unchanged. If the DEK may be compromised, the remedy is a new DEK and a new ciphertext. Old copies cannot be recalled. Signing keys do not decrypt the file. Lost vault material with no earlier wrap stays lost.
Threats this demo does not close
A compromised browser sees the keys it generates. One operator holding three guardian files is not three guardians. A malicious maintainer is only rehearsed as a named fixture. Dependency compromise, a missing mirror, and a break of ML-KEM confidentiality are out of scope. There is no RFC 3161 timestamp. Hash-based and lattice signatures here share one process.
Pilot template, blank
Proposed scope, data class, retention, success criteria, and exit steps are not filled in. No logo, invoice, or testimonial belongs here. Support contact is not a form: do not send secrets, private keys, or confidential files to this site. A real pilot stays closed until a named operator and a signed scope exist.
If something goes wrong
Stop the demo, reset lab state in the tab, and do not upload the identity files. A synthetic failure does not page a customer. There is no production on-call because there is no production custody. Escalate a suspected leak of a real key outside this demo to the person who holds that key, not to this page.
Business questions still open
Who would pay, for which document, and instead of what control, is not answered. No market size is stated. No competitive logo wall is stated. Pricing is not offered. Validation stays UNKNOWN until interviews and a signed scope exist.
Questions
What works now?
A visitor can run the safe Action Guard walkthrough and a synthetic recovery rehearsal in the browser. The lattice desk pages are unchanged.
What is simulated?
Repository writes, maintainer identity, dual signatures, and the rehearsal tenant. Testnet credits are not money. There is no customer.
How does file-key recovery work?
The file key is separate from the owner's ML-KEM key, a 2-of-3 recovery root, and the signing keys. Two guardian releases reconstruct the root and unwrap the file key locally.
What if no recovery wrap existed before the key was lost?
The file cannot be recovered by adding a sidecar later. An anchor does not restore key material or plaintext.
What does an anchor preserve?
A commitment to bytes. It does not store the file, the private keys, or the ability to decrypt.
What are the cryptographic limits?
Signatures are a one-process demo, labeled SIMULATED_DUAL_SIGNATURE. SLH-DSA-SHA2-128f is not a strength match for ML-DSA-65. ML-KEM does not sign. This is not an audit.
How would a real pilot start?
It needs an owner-approved scope, a named operator, a data classification, and a support contact. This page does not collect documents or secrets.
Where is the test evidence?
Run the gates on this page or on Recovery. The count is whatever that run executed. Real-world validation stays UNKNOWN.
What leaves this browser on these buttons: nothing to a Q-VITRN API. The page itself loads fonts and the application bundle. Downloaded JSON stays on your machine unless you move it.