The path

23 min total

  1. Validation receipts: making “tests passed” tamper-evident

    An agent that says the tests passed is making a claim about work you did not watch. A receipt binds that claim to a commit, a command set and the logs, so a wrong one is refused instead of believed.

    13 min read
  2. Provenance accounting: every commit on the branch explained exactly once

    Receipts prove that a commit was validated; they do not say where it came from. Closing a pass of coding agents only when every commit on the branch has exactly one recorded origin is what keeps unexplained work out.

    10 min read

Series in this path

  • Parts 1 and 2 of Building a harness for coding agents