Chapter 13 · operating safely

Evidence quality and command safety

Collect decision-changing evidence while preserving authorization, context, and production safety.

1 min read·Updated 2026-07-24·3 role paths
01

Evidence quality standard

Evidence is useful when it is attributable, scoped, timed, reproducible enough for review, and connected to a decision. A copied error string without source and time is a clue, not a complete evidence record.

02

Command record requirements

Record 01
Field
Purpose
Required meaning
Which question the command answers
Record 02
Field
Target
Required meaning
Exact system, scope, or object
Record 03
Field
Access
Required meaning
Required privilege and owner
Record 04
Field
Safety
Required meaning
Read-only, controlled change, or prohibited
Record 05
Field
Expected signals
Required meaning
Outcomes and how they affect the path
Record 06
Field
Actual result
Required meaning
Captured output or observation
Record 07
Field
Timestamp
Required meaning
When the state was observed
03

Investigation versus change

Read-only collection can still create load, expose sensitive data, or require elevated access. Controlled change requires authorization, rollback, monitoring, and validation. OGO should explain the boundary; it should not imply that a command is safe simply because it appears in a guide.

04

Stop conditions

Stop when the target is uncertain, the command differs from the approved form, the result indicates a larger blast radius, rollback is unavailable, access is not authorized, or evidence preservation could be lost. Record the stop and route it to the accountable owner.

05

Redaction and handling

Remove secrets, tokens, personal data, customer identifiers, and unnecessary payload content before sharing. Preserve the structure required for interpretation without copying the entire environment into the dossier.