SUPERVISION/REPORTS AND EVIDENCE
06 / REPORTS AND EVIDENCE

Make every claim
traceable.

Evidence reports connect a run's claims to the artifacts, checks and provenance behind them. Reviewers can see what passed, what remains partial and which gaps still block promotion.

EXAMPLE MODEL This page describes a runtime surface; values and events are illustrative.
REPORT CONTENTS

A reviewable
sequence.

Each transition keeps its relationship to the mission and the state that authorized it. That makes later review more useful than a detached success message.

01 · CLAIM

State what the run asserts

Make the result reviewable as a claim with an explicit scope.

01
02 · ATTACH

Link source artifacts

Keep outputs, execution receipts, events and workspace changes traceable; receipts do not become evidence by themselves.

02
03 · CHECK

Record verification

Show which checks ran, their outcomes and any limitations in coverage.

03
04 · DECIDE

Apply the promotion gate

Keep a decision tied to the evidence available at review time.

04
WHAT THE OPERATOR CAN INSPECT

Context is part
of the control.

Claimscoped and versionedThe report says what is being asserted
Sourcesartifacts + receiptsEvidence links to its origin
Decisionpromote · hold · rejectGate outcome is recorded
“
RUNTIME PRINCIPLE
An evidence report makes a decision auditable; process completion and execution receipts do not replace domain-specific validation.
← Back to supervision overview