PRODUCT EXECUTION RECORDINGS — 23 October 2026

These files record actual local product executions, replayed by the website.
They are not live services, AI-agent trajectories or paid model runs.

TAMPERWARD
Version: npm tamperward@2.47.0
Source revision: 362d8a6fe414eeba7e0381898a40baca7d3d9938
Fixture: a line-total function, with one-item and three-item Node tests.
The scripted candidate removes the three-item test and stops multiplying quantity.
Actual CLI outcomes include a test-deletion finding, visible pass/pristine fail
(MASKED_FAILURE, exit 1), legitimate pass (exit 0), and missing-base refusal (exit 2).
The JSON includes source strings, commands, results, CLI output and limitations.
No model or live coding agent participated. Passing these checks is not a
semantic-correctness guarantee. Local verification is not repository authority.

AI INSTITUTION
Source revision: 3fffc1641a0cf5389f51376244390134d9e75a4c
Executed the repository's runReferenceInstitution with SqliteHistoryStorage,
then opened a new storage instance on the same file and executed again.
The first run produced a policy allow and certified deterministic reference
execution with 17 audit entries. The reopened execution returned the same
receipt identities and stream versions. No external write, live model or
business office ran. This proves the narrow reference history behaviour,
not a live office, agent team, refund or external-action recovery.
The refund lab is a separate deterministic browser teaching model.

REPRODUCTION
Website source: scripts/capture-product-evidence.mjs in
https://github.com/hexrift/hamsasoftware-web
Install the exact Tamperward npm version above in a disposable directory.
Obtain the pinned AI Institution source revision (repository access required).
Use Node 24; the capture was executed on Node v24.19.0. The full AI Institution
repository currently declares Node >=24.20.0 <25 for supported development.
Set TAMPERWARD_CLI to dist/cli/index.js from that Tamperward installation and
AI_INSTITUTION_SOURCE to the pinned AI Institution checkout, then run:
  node scripts/capture-product-evidence.mjs
The capture only creates temporary local fixture repositories and a local SQLite
file, then removes them. It does not contact a model, send a message or pay money.
A new capture has different temporary commit hashes and timings; compare the
verdicts, fixture bytes, evidence and receipt identity invariants.