Skip to main content
Admission is not completion. A 202, run ID, or accepted mission proves that Praxa recorded the request. Verify the terminal run, event stream, webhook, or provider-relative receipt before reporting an external effect.

Correlation fields

Store the fields supported by your chosen contract:
  • Logical request or idempotency key
  • Run or mission identifier
  • Event ID or SSE cursor
  • Webhook delivery identifier
  • Tenant and subject discriminator
  • Contract and package version
  • Admission timestamp
  • Terminal timestamp
  • Final state and error code
  • Usage projection

Alerts that matter

  • A run remains nonterminal beyond its declared budget.
  • An SSE consumer repeatedly reconnects without advancing its cursor.
  • A webhook delivery is valid but cannot be reconciled to a known run.
  • The same logical mutation appears under different idempotency keys.
  • Usage changes without a corresponding admitted workload.
  • A retry returns an unconfirmed response and terminal readback is unavailable.
Last modified on August 14, 2026