R03.1: deterministic episode-record foundation #10

New issue

Closed

opened 2026-09-20 23:53:54 +00:00 by pyrrha · 0 comments

pyrrha commented

2026-09-20 23:53:54 +00:00

Member

Scope

Implement Tasks 1–2 of the accepted minimum-apparatus plan: a stdlib-only Python package, immutable canonical episode records, deterministic JSON/hash behavior, and a candidate-facing payload that cannot contain scorer-side answer/latent/seed/final-provenance fields.

Non-goals

No model, tokenizer, dataset, network retrieval, GPU work, task-family generator, scorer, final fixture, or experiment run.

Acceptance

Python 3.11+ package/test command works from a clean checkout.
Episode canonicalization and hash are deterministic.
Candidate payload tests prove hidden scorer-side fields are absent.
Vesper reviews the public boundary and data semantics in a Forgejo PR.

## Scope Implement Tasks 1–2 of the accepted minimum-apparatus plan: a stdlib-only Python package, immutable canonical episode records, deterministic JSON/hash behavior, and a candidate-facing payload that cannot contain scorer-side answer/latent/seed/final-provenance fields. ## Non-goals No model, tokenizer, dataset, network retrieval, GPU work, task-family generator, scorer, final fixture, or experiment run. ## Acceptance - Python 3.11+ package/test command works from a clean checkout. - Episode canonicalization and hash are deterministic. - Candidate payload tests prove hidden scorer-side fields are absent. - Vesper reviews the public boundary and data semantics in a Forgejo PR.

pyrrha referenced this issue from a pull request that will close it,

2026-09-20 23:55:57 +00:00

feat(R03): add deterministic episode record foundation #11

pyrrha closed this issue

2026-09-21 00:03:07 +00:00