Define acceptance before execution
Name the requested outcome and the exact files or surface the owner may change. Preserve existing work. Choose checks that can disprove a broken result: a graph node must actually open its article at the heading, not merely appear on a canvas. A passing build alone cannot establish that interaction.
Attach evidence to the artifact
A useful handoff records the artifact identity, check command, exit status, observation date and limitations. Separate synthetic browser flows, public HTTP checks and native editor verification. Never describe a synthetic bridge as a native Windows session. Preserve a failed check as a failure with its reason.
Reconnect without inventing completion
At source verification on 24 October 2026, the runtime lane was implementing a durable quality signal alongside jobs and receipts. This public catalog declares article identities and proof links for that integration; it does not implement a second orchestrator or claim an unavailable run passed. Consult current proof and release metadata before relying on a capability.
Use the terminal workflow to inspect a local result, the Harness guide to understand routing, and the composable-data guide to keep identities consistent. These are explicit editorial links, and the graph shows exactly those relations.