Operations

The harness should be understandable in failure, not only in success.

Operator surfaces

• harness doctor for prerequisites and path validation
• harness status for run visibility
• harness report for structured outcome review
• approval flows for gated tasks
• audit and compliance artifacts for deeper inspection

Default operator habits

1. validate setup before the first run
2. run one bounded task before scaling up
3. inspect structured artifacts before diving into raw logs
4. keep recovery behavior predictable and documented

What good product behavior looks like

• a new user can run one task without reading source
• a failed run points to the next corrective action
• example configs validate even in offline environments