Phase 2: lock and reproduce the scientific analysis environment #651
No reviewers
Labels
No labels
bug
cli
core
docs
event
experiment
figure
invariant
metrics
oracle
phase-0
phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
provenance
revocation
tests
workload
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erikinkinen/AES!651
Loading…
Reference in a new issue
No description provided.
Delete branch "phase2/p2-14-a-analysis-environment"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task
Closes #116 (P2-14-A).
Summary
Freeze the established protocol 2.2 analysis environment as a verified
Linux/amd64 image. The declared
.venv-research/bin/pythonpath launches thatimage, so analysis uses the recorded interpreter, package artifacts and thread
settings. Clean installation, image export and restoration have executable gates.
Scope
Included
distribution pins, wheel hashes/URLs, and the identified official base image.
numerical/import/rendering probes; a managed launcher preserving stdin and cwd.
separate build/export manifest identities, reproduction documentation and
hashed acceptance evidence.
Explicitly excluded
and the separate primary-bound leaves.
Design intent
Preserve the existing software versions and record every installation input.
Use a pinned base manifest, no network during installation, no layer reuse,
fixed build timestamp and a complete hash-required wheel inventory. Reproduction
must match the frozen configuration/rootfs identity and runtime report.
The archive manifest differs from the build-store manifest because export
compresses layers. Both are recorded and bind the same image configuration and
filesystem. The canonical
container_digestuses that common identity. A freshseparate VFS storage root verified actual archive restoration.
The sole 4 KB vendored wheel, autograd-gamma 0.5.0, is retained from the established
environment. Its Python module and included MIT license match the SHA-identified
upstream source. Its frozen bytes are the install input; a byte-identical new
source-to-wheel build is not claimed.
Phase discipline
Protocol 2.2 / backlog 2.2.1; prerequisite #84 is closed. This is a prospective
software lock before pilots or production analysis. Package or image changes
require the governing change-control process. Environment smoke fixtures do not
accept the later statistical methods or establish scientific results.
Verification
7eb6a62350d10234ea0271bbd473482700ca5b4d.and byte-identical runtime report: 35 distributions, 8670 installed-file hashes,
fixed threads, numerical/survival/rendering/schema/SQLite smoke probes.
into separate storage passed through the real verifier with an identical report.
and four OCI identity-graph cases. Actual fetch, build, launcher stdin/cwd,
export and restored-image commands all passed at the signed source.
is unchanged; the complete registered suite is 92 tests and remains required in
all eight final-head Forgejo checks before the one-step checklist update/merge.
Tracked records are under
artifacts/backlog/2.2.1/P2-14-A/.The large wheelhouse and OCI image are retained locally under
artifacts/environments/protocol-2.2/; their exact paths/sizes/hashes are in theacceptance evidence. The attachment contains verification receipts, source/release
metadata and logs. It does not claim those large files were uploaded. The committed
recipe and fixed artifact sources provide clean reproduction.