Event Register
Semantic-Timeline event stores per domain
Bundle → Layer → Finding → Questions Incomplete
4 bundles · 8 layers · 0 findings · 0 questions
capture Getting events into the log correctly
eventSchema
typed event payloads and their subject references
appendDiscipline
who may append what, idempotency, no in-place change
ordering Making the timeline a timeline
sequenceAssignment
monotonic sequence numbers and checkpoints
temporalSemantics
occurrence time versus record time and their reconciliation
integrity Making tampering evident
hashChaining
each event bound to its predecessors by hash
proofPublication
signed tree heads and inclusion proofs offered to verifiers
consumption Reading history safely
replayAndQuery
cursors, subscriptions and subject timelines
retention
how long payloads persist and what compaction preserves
Note: Legacy card: layers named, findings and questions never written.
Classifiers Filled
- Family
- World Models
- Category
- Cross-cutting context
- Entry kind
- pattern
- Navigation path
- NAV.XCT.EVREG
- Domain
- XCT.EVREG
- Industry
- Cross-industry
- Tags
- eventregisterxct.evreg
- Also called
- R3
What it is Derived, awaiting review
Semantic timeline event stores, one log per domain: what happened, in what order, provably untampered.
Note: First sentence of the legacy card introduction.
Why it exists Filled
Semantic-Timeline event stores per domain
Distinguishing features Missing, in the backlog
Not described yet. This gap is in the card backlog.
What robots and AI may and may not do Missing, in the backlog
Not described yet. This gap is in the card backlog.
Moral aspects Derived, awaiting review
- Read and replay access is granted by that owner through the S1/S2 access and consent models, with all access itself auditable via S4.
Owners Filled
Steward
Each log is owned by the domain registrar whose history it keeps; the registrar guarantees append-only discipline and proof publication.
Links to other meta-models Filled
composes
- (inbound) - domain models across the catalogue, for example world.registry (R1), world.ledgerAndAccount (R2) and world.lifeEventsAndCivilStatus (B12), publish their Events into logs of this model
- world.registryFederationAndMirroring - mirrors synchronize by replaying source logs under federation rules
references
- world.identityRegister - producers, consumers and event actors resolve to anchored identities
extends
- world.audit - the audit trail specializes this model for access and disclosure events
imports
- mu-event - ALIGN: the shared semantic shape of an event, its subject references and time semantics
- merkle-logs - ALIGN: hash-chained log structure for tamper evidence
- rfc-6962 - ALIGN: verifiable log proofs, signed tree heads and consistency checking
requires
- vr.wm-per-002
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Derived, awaiting review
- eventAppended: a new domain event was written at the next sequence position
- checkpointSealed: a range of events was closed under a sequence marker
- proofPublished: an integrity proof for a sealed range was made available to verifiers
- retentionApplied: expired payloads were compacted while hashes and proofs were preserved
- integrityViolationDetected: verification found the chain inconsistent with a published proof
- subscriptionOpened: a consumer began following a log from a stated position
Legacy events listed as state transitions.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- appendContract: which producer may append which event types to a log, under what schema version
- replayContract: a consumer's scope for reading or subscribing, by subject, type and time range
- proofVerificationContract: public terms for obtaining inclusion and consistency proofs without payload access
- retentionContract: the agreed retention period, compaction rules and legal-hold behavior for a log
- subjectTimelineView: all events concerning one subject in order; omits events of other subjects sharing the log
- inclusionProofView: proof material for one event; omits the payload entirely
- logHealthView: sequence continuity, checkpoint cadence and lag for operators; omits payloads and subjects
Context of use required Filled
- Read and replay access is granted by that owner through the S1/S2 access and consent models, with all access itself auditable via S4.
Sources Missing, in the backlog
Not described yet. This gap is in the card backlog.
Open questions
- Superseded by a researched world model? Map this legacy card to its successor or retire it.
Machine files
Provenance
legacy MMAS card (world-models v0.2) · legacy
Built from: models/world-r3-event-register/spec.yaml, models/docs/registries-ledgers/R3-event-register.md