Blueprint
Explains topology and expected flow with static descriptive data.
It does not claim that execution occurred.Runtime boundary
External coding agents perform the work
Claude Code, Codex, Hermes, and other connected coding agents implement changes. The harness starts or observes sessions, normalizes allowed events, binds artifacts to repository identity, and evaluates proof.
Presentation modes
The interface must identify the data source and cannot present static or replay data as live execution.
Live Run
Shows events from an application programming interface, command-line tool, Model Context Protocol server, connector, or watched artifact.
It can support runtime claims only when the source identity and artifacts verify.Replay
Reconstructs a recorded run from stored events and artifacts.
It must identify the original run and cannot present replay data as live data.Event contract
Identity
Events bind the target repository, commit, run, connector, and actor before they can support a claim.
Allowed input
Connectors accept contract-valid events and watched artifacts. Invalid or out-of-order completion cannot bypass the route.
Artifact integrity
Recorded artifacts carry digests. Mutation or deletion after completion quarantines trust.
Authority
Coding agents cannot grant human approvals, create trusted external receipts, or self-attest independent review.
Runtime is not the coding interface
The harness is a repository runtime adapter and assurance control layer around external coding agents. It does not replace their editor, terminal, account, or model interface.