Platform, configuration and devices · C0834
Who signs each release of the element type registry, and how is it checked before use?
Designed, not yet built
Short answer
Designed, not built: there is no code for this in the pilot. For reference, REQ-0103 (a top-priority requirement, all three tiers) says Registry releases must be signed by AuroraMed compliance, verified by the on-site server before activation, and their hash must be anchored to the ledger. Check: unsigned or tampered release is refused; an anchor transaction exists for each activated release.
This is designed, not built.
- Specification item
- REQ-0103
- 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
- What does the element type registry record about each type of clinical content? Designed
- Can administrators add new members of an artifact family without waiting for a software release? Designed
- How many jurisdiction profiles does one deployment load, and who has to sign it? Designed
- What happens if someone submits a content type that the system does not recognise? Pilot
See it in context: Configuration, Element Type Registry and Jurisdiction Profiles · Search the help center · Ask a question