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

# Run-scoped observability

> Telemetry keyed by stable run identity and queryable across concurrent work.

Every captured event belongs to a run. That stable key lets a customer correlate model calls, tool
calls, spans, logs, and process output across a large concurrent workload without relying on a Pod
or sandbox provider id.

## Capture boundary

`hiloop run` wraps a host-side command and captures supported process, network, and OpenTelemetry
signals. It stamps trusted run identity before export:

```sh theme={null}
hiloop run --project demo -- python3 agent.py
```

Sandbox lifecycle events are platform metadata and flow independently. The sandbox runtime does not
need a second run for workload capture: every sandbox's managed session writes supported entrypoint,
exec, SSH, cooperative HTTP, and OTLP activity to the ambient run returned by create.

## Query boundary

The query engine scopes every request to the authenticated organization and exposes a constrained
`SELECT` surface over events. Use `run_id` and, when present, `lineage_path` to group related work.
Logical run lineage does not imply that runtime filesystem fork is available.

See [capturing telemetry](/guides/capturing-telemetry), [the event model](/concepts/event-model),
and [querying telemetry](/guides/querying-telemetry).