IRON LITANY

Published v0.3.1 — crew and cannon contact

6 October 2026. Game source frozen and tagged at 2aecf7f153be6a874e402aaa8096b64f1307dc89. Later source commits add release evidence only; the published/native runtime remains this exact revision.

Available delivery

The crew/contact record describes the original models, loading receiver, fitted controls, actual local first-halt journey and remaining art work. The asset manifest records dimensions, pivots, materials, provenance and candidate status. No cinematic or narrated gameplay was published; demo approval still gates those deliverables.

What was verified

All 126 source tests pass. The two new meaningful contracts check operator grips through parent motion and the traversed insertion/hand-release/gate sequence. Source syntax and 262 local references across 148 shipped files pass. The native CI run passed on actual Linux and Windows runners.

Both ZIPs passed full CRC, exact hashes for all 148 bundled files, their outer/inner manifests, pinned official runtime hash and native x64 executable inspection. Native smoke covered startup, actual WebGL rendering, camera switching, offline pages, saved-origin reload, first-person slit admission/rejection and positive/negative shared-world overhead cones. Linux used the documented isolated CI software-rendering configuration while retaining its sandbox. These checks are not human desktop combat acceptance.

The public GitHub API reports all six release assets with the expected sizes and SHA-256 digests. Both complete ZIPs and all four checksum/manifest sidecars were independently streamed anonymously and hashed. No duplicate downloads were retained. Linux is 146,331,661 bytes; Windows is 181,398,729 bytes. Raw hashes and all checks are in [native verification](native-v031/verification.json), [public readback](native-v031/public-release-verification.json) and download metadata.

The website preparation preserved all other game channels and the literal channel override tail. Both complete game trees matched all 148 frozen files. The complete production package retained trailers, routing, headers, redirects and edge configuration. All 11 download/channel checks passed, as did source references and the public-surface check. Deployment was 6ac522c4d2c169cc9a4bddd4. Nine canonical game entry/runtime files match the frozen bytes exactly; only the documented front-page dossier href patterns undergo extensionless hosting rewriting. All three changed canonical website scripts also match their prepared bytes. See [canonical readback](native-v031/canonical-web-verification.json) and [publication receipt](native-v031/publication.json).

On the new immutable deployment origin, ordinary controls completed the protected held-tool engine lesson, walked the corrected breech approach, entered first person and sampled the actual shot-driven loading cycle through seat. All recorded crew overreach was zero. The published loading frame, overhead frame and read-only sample record retain the evidence. The sample reported 60 FPS with no captured console error or warning; this is not a performance benchmark or a full campaign victory. The game page, cassette and download chooser showed v0.3.1 and both correct immutable download URLs.

The canonical game tab was inspected before refresh, confirmed at its unstarted welcome screen, then refreshed to v0.3.1 with Continue saved watch still present. The creator's saved watch was neither started nor replaced. Owned intermediate QA tabs were closed.

Private mirror publication terminally succeeded as appgdep_6ac5228470c4819192e24e97e1c7404f, with saved version appgprj_6ac407d6e1b481918ae8e5afe9c4f4ea~appgver_fcc9e73c320c81918e87bac51278ab3e from the frozen source/archive. [Mirror receipt](native-v031/private-mirror.json) records that result. No audience change occurred.

Acceptance boundaries

The local actual-input journey reached the first halt, made three crew replacements and restored the saved halt, then inspected final contact in Watch 2. It deliberately neglected maintenance while capturing art; two urgent repairs spent parts and spirit to recover cooling. This demonstrates a practical time/resource tradeoff, not optimal balance or a full three-watch victory. Crew hands, garment deformation, injuries, unique recruit identity and priest/tool contact remain candidate art work. Sustained human listening, touch journey and full new-campaign acceptance remain open.

Native artifacts were downloaded sequentially within a 660 MB peak budget, not extracted into redundant full runtimes. Website copying was bounded at 100 MB and deployment cache at 500 MB; actual resolved filesystem checks preserved the required 100 GB reserve. Final measured headroom is recorded in the publication receipt. No source, master, runtime or unrelated application was deleted or stopped.

Dossier generator mappings now include this evidence for the next deliberate source release. They were not rerun after freezing v0.3.1, so shipped bytes continue to match the native packages.