Engine · Available

Event

The nervous system — publish, subscribe, catalog.

@keystone/engine-event

Purpose

Platform events move between engines and applications without hard-wiring modules together. Domain catalogs stay in app packs; Keystone owns the transport, the catalog, and an in-process bus with a durable-enough recent log.

In a product

When a tracker record changes status, Event carries that fact to Automation — without Tracker importing Automation, and without Automation reading Tracker’s database.

How it works

  1. Engines and apps publish named events (for example tracker.record.updated or flow.instance.phase.advanced).
  2. Subscribers listen by exact name or prefix pattern.
  3. A platform catalog lists known types; apps can register their own industry events in packs.
  4. Event boots first so every other engine can publish and subscribe at startup.

Capabilities

  • KeystoneEvent / DomainEvent envelopes
  • In-process bus with exact and prefix subscriptions
  • Platform event catalog (tracker, flow, automation, trigger, notification, document, AI, report, billing, user, org, …)
  • Recent event list for debugging and tooling
  • Optional strict catalog mode for production discipline
  • Always first in the runtime boot order

Related

Tracker · Workflow · Trigger · Automation · Notification · Billing

All enginesBuild on Keystone