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

Ledger, sync, offline and hardware requirements · C0971

How are out-of-schedule signals from the analog layer handled?

Designed, not yet built

Short answer

REQ-3502 is a lower-priority requirement for the large tier only: out-of-schedule signals must be flagged to all nodes. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says injected out-of-schedule signal produces ALERT token.

This is designed, not built.

Specification item
REQ-3502
Specification priority
P3 (of P0 to P3)
Tiers
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: Analog timing layer · Search the help center · Ask a question

See the synthetic-data demo first.Request a demo