Event Metadata Standard¶
Executive Summary¶
Event Metadata Standard defines the required logical metadata for Algosure events. Metadata supports tenant isolation, traceability, auditability, correlation, causation, versioning, idempotency, and future replay.
Why This Exists¶
Events are used across Domains, AIOS, notifications, analytics, integrations, and future delivery infrastructure. Without standard metadata, event flow cannot be trusted, audited, replayed, or safely consumed.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Standard metadata makes event-driven behavior explainable, secure, tenant-aware, and diagnosable.
Required Metadata¶
| Metadata | Requirement |
|---|---|
| Event ID | Unique identifier for this event instance. |
| Event name | Business-readable past-tense event name. |
| Event version | Version of the event contract. |
| Occurred at | Time the business fact occurred. |
| Published at | Time the event was published, when different from occurrence time. |
| Tenant ID | Tenant boundary for isolation and authorization. |
| Organization ID | Customer organization context where applicable. |
| Source domain | Domain or module that owns the fact. |
| Source aggregate ID | Aggregate or business object that produced the fact where applicable. |
| Correlation ID | Identifier tying related events and actions into one business flow. |
| Causation ID | Identifier of the command, event, or action that caused this event. |
| Actor ID | Human, system, or AI actor associated with the action where applicable. |
| Trace ID | Operational trace reference where available. |
| Schema reference | Logical reference to the event contract definition where available. |
Metadata Flow¶
flowchart LR
Command[Command or External Observation]
Event[Event with Metadata]
Consumer[Consumer Reaction]
Audit[Audit Trail]
Command -->|causation ID| Event
Event -->|correlation ID| Consumer
Event -->|tenant and organization IDs| Audit
Metadata Rules¶
| Rule | Meaning |
|---|---|
| Tenant ID is mandatory for tenant data | Events that relate to customer data must carry tenant context. |
| Organization ID is mandatory where business context exists | Organization-scoped events must carry organization context. |
| Correlation ID spans a business flow | Related events in one workflow or process should share correlation. |
| Causation ID explains why | Consumers must be able to trace what caused an event. |
| Event version is explicit | Consumers should know which contract version they received. |
| Metadata is not business payload | Metadata supports routing, audit, and traceability; payload carries business facts. |
Non-Implementation Boundary¶
This document does not define JSON structure, headers, serialization format, database columns, or framework-specific metadata carriers.