# Reporting Contract

Use this reference when the authored plan or run charter needs to define what the master should report for status, completion, or stop.

## Status Fields

- run phase
- active pairwise edges or owned child loops
- completed results
- blockers or late conditions
- next planned actions
- completion-condition posture
- stop-condition posture when relevant

## Completion Fields

- final synthesized result
- why the completion condition is satisfied
- relevant plan or run references when needed

## Stop Summary Fields

- stop mode used
- which edges completed before stop
- which active edges were interrupted or drained
- preserved partial results
- remaining unfinished work or known blockers

## Guardrails

- Keep status current and operational rather than historical by default.
- Keep completion and stop summaries tied to the authored completion and stop conditions.
