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

Ledger, sync, offline and hardware requirements · C0928

Would typing rhythm or location be used to judge a session's risk?

Designed, not yet built

Short answer

Designed, not built: there is no code for this in the pilot. For reference, REQ-3007 (a top-priority requirement, all three tiers) says session risk bands (0-3) may use keystroke cadence, location and timestamp; keystroke cadence must be a review flag only and never a sole lockout trigger. Check: simulated cadence anomaly alone creates a review item, not a lockout.

This is designed, not built.

Specification item
REQ-3007
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: Federated ledger, spheres, tokens, wallets, bridges · Search the help center · Ask a question

See the synthetic-data demo first.Request a demo