AuroraMed v0.2.0 is a synthetic-data pilot. See exactly what's built →

Ledger, sync, offline and hardware requirements · C0962

How would a terminal prove it has not been tampered with?

Designed, not yet built

Short answer

The on-site server, sealed terminals, hardware profile part of the specification (REQ-3305) says terminals must attest to the server at boot and per session (TPM/secure element) and refuse to render on mismatch. No. The specification describes it, but the pilot does not include it. Acceptance check: tampered image fails attestation and gets quarantined.

This is designed, not built.

Specification item
REQ-3305
Specification priority
P0 (of P0 to P3)
Tiers
Small, Medium, Large

Status as of September 30, 2026. Version 0.2.0, synthetic data only. See what's built today. Not legal, medical or security advice.

Related answers

See it in context: On-site server, sealed terminals, hardware profile · Search the help center · Ask a question

See the synthetic-data demo first.Request a demo