> ## Documentation Index
> Fetch the complete documentation index at: https://docs.domesystems.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Operate

> Investigate audit events, stream live events, and subscribe to outbound notifications

**Operate** makes governed traffic visible and actionable. You query the durable audit trail, stream live events, and subscribe external systems to signed deliveries.

Refer to [Audit events](/concepts/audit) concept for how the one trail works and [Events](/reference/events) reference for the shared envelope and catalogs.

## How Operate surfaces events

The following surfaces share one operational story:

* **Audit Events** queries and filters the durable Audit v1 trail. You investigate by class, actor, resource, correlation, and payload, then follow activity chains across configuration and runtime events.
* **Stream Live Events** shows that same trail in real time and adds live operational signals such as calls and denials, health and latency, token usage and cost, Quotas, OpenTelemetry, and product telemetry.
* **Subscribe to Events** pushes a public projection of selected events to your HTTPS endpoint or a provider. Deliveries are signed, retried, and replayable. They are not a substitute for the audit trail or for batch export under [Manage](/manage/export).

Audit Events is the durable record. Stream Live Events and Subscribe to Events are the live surfaces: stream inside Dome, subscribe when another system must react as events occur.

The typical workflow is:

1. [Audit events](/operate/audit) to query, get, and correlate retained events when you investigate a decision or prepare evidence.
2. [Stream live events](/operate/observe) for governed traffic in real time, and optionally review token usage, cost, OpenTelemetry, or product telemetry.
3. [Subscribe to events](/operate/webhooks) to create destinations and subscriptions for the event types your automation must handle.

After setup, you can add destinations, widen subscriptions, or change retention without touching Connect or Govern configuration.

## Next steps

* [Connect](/connect) when you still need agents, resources, or Gateways
* [Govern](/govern) to authorize actions, set usage limits, and inspect content
* [Manage](/manage) to configure platform access, environments, integrations, and data exports
* [Develop](/develop) to send runtime credentials, Gateway endpoints, and Act-As envelopes from the application