Event API contracted

Events use the committed AsyncAPI contract plus the event taxonomy and NATS stream configuration for operational context.

Event Rules

• Events use the standard envelope with event id, type, timestamp, version, correlation id, and payload.
• Producers write domain state and outbox rows in the same transaction.
• Consumers subscribe through configured NATS stream/consumer ownership.
• Portal reference pages should be generated or linked from canonical artifacts.

Synced Artifact

The portal check copies the committed AsyncAPI contract into the static portal bundle:

• Download AsyncAPI YAML

Consumer Path

• Use Idempotency And Retries for event retry, acknowledgement, and DLQ expectations.
• Use Contract Artifacts for synced YAML artifact links.
• Use AsyncAPI Rendering Path for the generated event-reference roadmap before adding a renderer dependency.

Current Boundary

The portal can explain event ownership, NATS stream posture, and consumer behavior. It should not hand-copy payload schemas; event payload shape remains owned by the synced AsyncAPI contract.

Canonical sources

• doc/api/asyncapi.draft.yamlraw
• doc/api/asyncapi/manifest.yamlraw
• doc/architecture/Event_Taxonomy.mdraw
• doc/architecture/NATS_Stream_Config.mdraw
• packages/docs/scripts/sync-contracts.mjsraw
• packages/docs/docs/developer-apis/asyncapi-rendering/index.mdxraw