Deterministic Resume · Engineering Evidence

Source of truth

Same WO as Recovery. Generated artifact ledger lives inside the resume packet, one row per packet/overlay with checksum=sha256:<hex>.

Mechanism

The resume packet is rendered deterministically from PG state. Each render emits a SHA-256 over the packet bytes; the hash is stored alongside the file path. Replaying the render at the same PG snapshot produces the identical hash.

Evidence

stand-down history · sha256 per generation

WO: wo:demo:platform-cleanup
Stand-down history (8 events):

  gen 1   sha256:42a501d5faeec04ead89bb952928300b80499e9713093757393f0f4e6fa6eb67
  gen 2   sha256:c08b895b1020f56ca78a370fbda2a8d22b09f6c8c115c29aadef231877de8d24
  gen 3   sha256:a1b0c59fbd27f14dc63d4aaef93051ebdc9ef474f5d1b9bef878d3ad2d4db313
  gen 4   sha256:907501eaad84e489485843ea4cb5a8ddc999d1013518192c322d911f291e2d07
  gen 5   sha256:dcc82b7966200841e136aea08ee66021935f4727176141401d32f7481bc7365b
  gen 6–8 sha256:…

  Same PG state → same SHA-256.
  Determinism is a property of the bytes, not a promise from the model.

Reproduction

reproduce · regenerate and hash

Source artifact

<wo>/grounding/generated/resume_generation_<N>.md + the checksum row in RESUME.md

Command

agentos-hook standdown checkpoint --wo-dir <wo> (twice, no state advance between calls)

Expected output

two resume_generation files; identical bytes; identical sha256

Verification

sha256sum on both files; expect matching hashes

Caveats

The 8 generations above show 8 different hashes because PG state advanced between stand-downs. The claim is same state → same hash, demonstrated by replaying the command without state change.

← Previous

Memory Grounding

Cost Attribution

Run the commands yourself.