Reference
Current command, term, and artifact reference surfaces for WitnessOps operators, integrators, and reviewers.
Start with app CLI commands, app vocabulary, or results and reports. The operator and receipt-profile references below describe separate technical models, not additional app permissions or a production deployment claim.
Quick reference links
- Reference (current page)
- Commands
- Proof Artifact Classes
- Glossary
- man witnessops(7) — draft / not published as a primary public page; use Commands
1. Problem this page solves
Concept pages explain why mechanisms exist. Reference pages define what to call them and where to find the contract.
Without a stable reference map, teams drift on command names, artifact labels, and review language. This page prevents that drift by routing you to the source-of-truth surfaces.
2. What you should understand after reading
After this page, you should know:
- where command truth lives
- where artifact-class truth lives
- where shared term definitions live
- which claims this section does not make
- which page to open next for command-level detail
3. Truth map: commands, terms, and artifacts
| Surface | Truth defined here | Use when |
|---|---|---|
| Commands | source-backed app CLI tools, plus separately labeled OffSec helper commands and their boundaries | you need exact invocation shape and to know which toolchain owns an action |
| man witnessops(7) | draft operator-manual rendering; not published while draft: true | use Commands instead |
| Proof Artifact Classes | current artifact classes, ownership lanes, and status labels (live / public, retained-reference / corpus class, planned, not live) | you need class-naming discipline across docs, app, and review |
| Glossary | shared term definitions used across governance, operations, and evidence docs | you need precise meaning of recurring terms before interpreting workflow pages |
If conceptual pages and reference pages differ in wording, treat reference pages as naming authority and conceptual pages as mechanism explanation.
4. Bounded claims and explicit scope limits
This section is intentionally narrow.
- It defines reference routing and terminology boundaries; it does not authorize actions.
- It does not replace Governance, Authorization Model, or escalation policy pages.
- It does not widen receipt-only
/verifyinto agent observation, review intake, server collection, or runbook execution. Those are separate actions with their own authority and limits. - It does not freeze canonical bundle-verification or corpus-only vocabularies as universal live-web guarantees.
- It does not promote the draft man page as a public primary-flow entry; command contracts live under Commands.
- It does not prove conclusion correctness; receipts and verification prove bounded artifact-integrity claims, not perfect operational judgment.
5. Workflow crosslinks
Operator workflow links
Reviewer and approver workflow links
6. Next-page handoff
Next, read Commands for the app CLI tools and the separately labeled operator helper reference.