Events and ratings

This chapter covers the event-driven billing path:

1. Record business facts as events.
2. Match events with active event rating policy versions.
3. Emit rating intents and materialize ratings.

What this chapter covers

• Event pipeline mental model and boundaries.
• Policy lifecycle and safe rollout.
• DSL design and validation references.

What this chapter does not cover

• Direct gate ingest (/gate/ingest) runtime semantics.

Direct ingest is documented in Gate ingest.

Core docs

• Outcome model: Outcome-based billing model (events then ratings)
• Events write path: Events API rules
• Runtime conversion (single-event): Single-event processing
• Runtime conversion (aggregate): Aggregate processing
• Policy lifecycle: Event rating policies lifecycle
• DSL reference: Events to ratings DSL
• Hands-on flow: Tutorial: events then ratings (ingestion first)

Verify checklist

• You can explain when to use events pipeline vs direct ingest.
• You can explain single-event and aggregate processing boundaries.
• You can promote policy versions with validation before activation.
• You can trace from a recorded event to downstream rating outputs.