# Bind confirmation identity to what the run reads

An inspection identity bound HEAD, the index, and Git status, so any commit to
the default branch between inspection and start invalidated a confirmation. That
made proposing an update from an unrelated session hostile in practice while
adding no content safety: HEAD says nothing about the bytes adoption reads or
writes. Identity now binds the selection, resolved materials, affected bytes and
modes, the product-state inventory, and, for discovery-backed runs, the discovery
observation. HEAD is recorded in the run for provenance but is not bound. Start
still requires a clean tree. The trade-off is that an unrelated commit can sit
between inspection and start; if it changes anything the run reads, the bound
content changes and the identity with it.

[ADR 0012](https://repo-standards.com/docs/decisions/0012-bind-content-not-location/) extends this decision: the
identity no longer binds the project root either, which the run records for
provenance like HEAD, and ignore inputs are bound by role and content rather
than by location.
