Events

The public event posture for Auk lifecycle changes and how partners should reason about state progression.

Events are the public lifecycle signals around quotes, policies, claims, and other Auk runtime changes.

Why Events Exist

Partners should not have to infer state changes from browser behavior.

Events make lifecycle change explicit so external systems can:

reconcile state
trigger downstream workflows
power audit and support views
connect to webhook delivery later without changing the domain model

Lifecycle Shape

quote created
  -> policy bound
  -> trigger observed
  -> claim opened
  -> payout released or deferred

Event Lifecycle Foundation

The public event model is still the same lifecycle backbone the current Auk reads already expose. Even before a standalone event feed is fully published, the API tab can use this section as the event anchor for policy, claim, payout, and reconciliation summaries.

Public Rules

events should describe durable lifecycle facts
the event catalog should stay stable once public
browser clients and operator surfaces should reflect the same underlying event truth
future webhook delivery should reuse the same event semantics

Illustrative Event

{
  "type": "policy.updated",
  "policy_id": "pol_123",
  "status": "active",
  "occurred_at": "2026-03-20T10:12:00Z",
  "links": {
    "self": "https://api.parametrig.com/auk/v1/policies/pol_123"
  }
}

What Deepens Later

As the public reference expands, this page should grow into:

canonical event families
delivery guarantees
idempotency expectations
reconciliation notes
webhook mapping