Design Inputs and Evidence
The reference implementation is entireio/cli at commit caa0c9be90261fb2b64bf6cfc7147ee3981494db, inspected from a local checkout on 2026-08-10. It is a design input, not a runtime dependency.
Relevant Entire CLI evidence:
docs/architecture/sessions-and-checkpoints.mdseparates an active Session, ephemeral full-state checkpoints, persistent summaries, and session content.api/checkpoint/interfaces.goseparates checkpointRead/Listfrom session-content reads and seals persistent writes behind typed operations.cmd/entire/cli/checkpoint/checkpoint.gomakes ephemeral checkpoints full worktree state on shadow branches, while persistent checkpoints keep metadata and commit linkage.cmd/entire/cli/checkpoint_resume.goandcmd/entire/cli/resume.goshow that Entire resume may switch branch/worktree context and write an agent's native session log. Better Harness must not inherit either behavior.docs/architecture/ref-checkpoint-backend.mdsolves remote Git-ref storage, discovery, push, and migration. Those problems are outside this local MVP.
Relevant Better Harness evidence:
scripts/harness-analysis/run-dir.mjsallocates collision-safe report run directories.scripts/harness-analysis/render-report.mjspublishes an artifact set through a staging directory.scripts/harness-analysis/report-run.mjs, in contrast, states thatharness analyzenormally writes no files. A checkpoint therefore anchors a completed artifact run, normally afterharness render, not every analysis call.scripts/harness-analysis/learning-capture-state.mjsrestores one validated field projection from an earlierfindings.json, but its implicit fallback recursively scans.qoder/better-harnessand chooses by modification time.scripts/harness-component-snapshot/already owns component identity, revision, digest, diff, and rollback-reference resolution. Its resolver explicitly returnsmutationAuthorized: false.scripts/session-analysis/selection-plan.mjsowns the selection profile and private fact snapshot. Those artifacts bind an eligible population but do not retain the actual plan or selected subset. Profile and snapshot digests are therefore a drift anchor, not selection-resume state.- Architecture Principles require capability ownership, public imports, parser-safe output, read-only defaults, explicit mutation, argv-array dispatch, and honest evidence classes.