Validation record

This package was built as a sequence of validation gates: each gate is a bounded claim about equivalence with the reference implementation, together with the measurements that support it, the deviations that were found, and what was deliberately left out of scope. These documents are the primary evidence behind every "validated" statement in the README — kept in the repository so that any claim can be traced to what was actually checked, per the provenance rule in ../building.md.

They are working records, in chronological order, and read like it: raw numbers, dead ends, and corrections included. That is intentional — a validation trail that only shows successes is not a validation trail.

GateClaimRecord
FJ1package skeleton, typed data model, config hierarchyFJ1_STATUS.md
FJ2semantic parity of the pure functions against fixtures from the Python sourceFJ2_STATUS.md
FJ3native dynamics, observers, transition, exact NumPy RNGFJ3_STATUS.md
FJ4the POMDPs.jl model interfaceFJ4_STATUS.md
FJ5 / FJ5-Rlive reference backends + matched-state one-step parityFJ5_STATUS.md, FJ5R_STATUS.md
FJ6free-running full-episode rollout parityFJ6_STATUS.md
FJ7the four trained baselines, matched layer by layerFJ7_STATUS.md
FJ8online planning: solver contract, budget curves, comparisonFJ8_STATUS.md, FJ84C_STATUS.md
FJ9scientific visualization through reproducibility closureFJ9_STATUS.md, FJ96, FJ97, FJ98, FJ99
FJ10POMDP readiness auditFJ10_STATUS.md

fj54_stop_probe.json is a probe artifact referenced by FJ3/FJ5 (regenerated by tools/parity/run_stop_probe.jl).

For the narrative companion — what every file in the package is, why it exists, and where its evidence lives — see ../building.md.