materialized-files

Provenance

• Source: .spec/spexcode/spec-cli/sessions/injected-context/harness-delivery/materialized-files/spec.md
• Source SHA-256: f3f1240f2d9c745f3dc0f587efb302f1e07743d11be4717b474d26add1ba51a6

Derived harness artifacts are a target state, not an instruction to write. The one writer compares the existing bytes with the desired bytes and writes only on a difference; copied package files use the same rule. This gives all materialize consumers one operational idempotence law: a correct target keeps its filesystem identity, while a changed target receives exactly the requested bytes. It does not decide which paths belong to a materialize pass or which stale paths to remove; those are the owning renderer's target map.