Glossary: Auditability
Mirrored from
docs/design/auditability/references/glossary.md. Edit the source document in the repository, not this generated page.
This glossary covers Orbit-specific auditability terms only. Generic observability, database, and security terms are excluded unless Orbit assigns them a specific meaning.
| Term | Meaning |
|---|---|
| Audit channel | One of Orbit’s distinct audit storage paths: command audit rows, v2 envelope JSONL, loop audit JSONL, blobs, or invocation metrics. See ../2_design.md §1. |
| Blob reference | A sha256 string stored in an audit event that points to redacted content-addressed payload bytes. See ../2_design.md §5. |
| Command audit row | A compact SQLite AuditEvent record for a CLI or targeted runtime operation. See ../2_design.md §2. |
| Coverage matrix | The prescriptive map from operation class to required audit channel. See ../2_design.md §3 and ../specs/coverage-matrix.md. |
| Invocation trace | A metrics-oriented usage record keyed by job run, activity, task ids, agent, model, tokens, and tool-call summaries. See ../2_design.md §8. |
| Loop audit event | A provider/tool-level event emitted by the HTTP loop engine for sessions, HTTP turns, tool calls, iteration boundaries, or policy denials. See ../2_design.md §5. |
| Redaction boundary | The point before durable write where Orbit removes known secret shapes from audit payloads or error strings. See ../2_design.md §6. |
| Run trace | The workspace-local file-backed reconstruction material for one activity/job run: v2 envelope JSONL, loop JSONL, and blobs. See ../2_design.md §4. |
| Task history | The persisted lifecycle and comment trail attached to a task, used beside command/tool audit rows to show task-state changes over time. See ../2_design.md §7 and ../specs/coverage-matrix.md. |
| V2 audit envelope | The activity/job wrapper event containing schema version, event id, run id, agent identity, optional parent id, optional workspace path, and a typed body. See ../2_design.md §4. |
| Workspace provenance | The workspace_path attached to file-backed v2 audit envelope events so traces can be filtered back to the repository that produced them. See ../2_design.md §4. |