Read This First

• Flow: completed run -> topology/target binding -> analysis intake/validation adapter -> sealed envelope substrate -> Better Harness user-state store -> read-only inspect or allowlisted learning-context load.
• Native report/selection/component meaning stays in harness-analysis/checkpoint-adapter.mjs; generic sealing stays in harness-checkpoint/.
• The normative object is in Envelope Contract, path/discovery rules are in Storage and Lifecycle, callable behavior is in Public Surface and Errors, and growth rules are in Versioning and coexistence.
• V1 never retains artifact bytes, restores code, resumes native sessions, merges platform-scoped catalogs, or turns selection/component anchors into mutation.
• Multi-host rule (HRC-AC-16): implicit learning scan is Qoder-only; every other host must supply --previous-checkpoint or --previous-findings for host-correct continuity.

V1 invariants: create is explicit; one immutable envelope is written; artifacts are referenced rather than copied; artifact kinds and four anchor rows are closed; topology root plus target identity binds continuity; only learning capture grants resume-context; Better Harness owns one Git-neutral state store; platform is provenance/filter data; selection and component state never authorize mutation; V2 is required before widening any of those semantic boundaries.