Reference Search docs

Event families

Event names use family.PastTenseFact shape. The design suite keeps a canonical inventory; new families must be cataloged before inventing backticked names in design or site prose.

Envelope (conceptual)

Every fact rides a shared envelope family of fields:

FieldRole
idULID — global causal-ish order
seqPer-stream total order
typefamily.PastTenseFact
stream / aggregate idOwnership boundary
causationId / correlationIdWhy / which workflow
tenant (+ project/env as applicable)Isolation claims
meta.idempotencyKeyExactly-once effects over at-least-once delivery
positionWhen read from DurableEventStore — store-local

Families you will hit often

FamilyExamplesNotes
compat.*GatePassed, GateFailedcan-deploy outcomes
contract.*Observed, Verified, EffectDeclared, EffectInvokedContract IR lifecycle
policy.*Decided, ObligationCreated, ObligationSatisfiedAlways decide, even allows
gatekeeper.*DecidedComposed gate result
resilience.*Attempt, TerminalSecondary resiliency layer
actor.*Activated, StateAppended, PassivatedActor host lifecycle
crew.*AgentDispatched, ActionProposed, ActionApplied, HandoffRequestedThin roster — no per-operator silos
incident.*Opened → … → Resolved / PostmortemFiledSRE loop
run.*Started, StepCompletedWorkflows / generation runs
deployment.*Planned / Applied / Deployed / Failed / RolledBackControl plane
broker.*Resolved, RejectedConductor placement
resource.*Provisioned / Failed / DriftDetectedResourceActors
token.* / identity.*Issued / Rotated / AccessedRefs only for secrets
config.* / secret.*Resolved, AccessedRefs only
meter.*UsageRecordedShowback facts
guardrail.*BlockedAI safety
trail.*Plan/run/cutover factsContinuous migration recipes
station.*Station/Rail lifecycleControl-plane isolation
replay.*Started / ChunkIngested / Ended / Accessed / …Session Replay lifecycle (not event-log replay)

Domain apps add their own families under app namespaces — do not overload crew.* or deployment.* for business cart events.

Sandbox lanes

Boundary virtualization tags envelope lane metadata. Baseline contract promotion ignores sandbox-lane observations by default so experiments cannot poison production contracts or training trajectories.

Rules

  1. Past tense only — commands are not events.
  2. Inspection and audit are replay of the log, not process memory.
  3. Poison bodies → *.Quarantined so folds skip deterministically.
  4. Crew roster facts stay on thin crew.* — operator-specific detail is payload, not family explosion.
  5. Streamer frames are not automatically domain events.

Architecture · Data plane · Crew shared model · EventStore