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

Security, privacy and audit requirements · C0902

How would audit records be chained, batched and anchored to the ledger?

Designed, not yet built

Short answer

Audit records must be hash-chained per node, batched into Merkle trees and the batch root anchored to the ledger at an interval (still an open decision). That is REQ-4502, a top-priority requirement for all three tiers. Not yet. It is designed in the specification and not built in the pilot. Test in the specification: deleting a local record breaks verification. Parts of it are explicitly marked as open in the specification.

This is designed, not built.

Specification item
REQ-4502
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: Audit · Search the help center · Ask a question

See the synthetic-data demo first.Request a demo