REPRODUCE.md

Independent replay packet

This packet makes it easy for an independent reviewer to reproduce the integrity and internal-consistency checks on this synthetic-only release. It does not ask the reviewer to endorse the profile, test a provider, or make a security finding.

Independence boundary

An independent replay should be executed and recorded by a person or organization other than the release maintainer. The result may be consistent, inconclusive, or not_run; a failed or inconclusive result is useful evidence and must not be rewritten as a pass.

Replay steps

1. Download and extract the fixture bundle in a fresh directory.

2. Record the bundle's SHA-256 and the Python version used.

3. Run the three commands below, preserving stdout and exit status:

   python3 scripts/verify_bundle_manifest.py
   python3 scripts/validate_profile.py
   python3 scripts/validate_viewer_split.py
   

4. Copy review/replay-record.template.json outside the bundle, fill only factual observations, and validate it:

   python3 scripts/verify_replay_record.py --record replay-record.json
   

5. Keep the completed record with its command-output digests. Do not include credentials, target configuration, customer data, or provider observations.

Supported conclusion

If every command succeeds, the reviewer may conclude only that the downloaded synthetic bundle was internally consistent in their recorded environment. This does not establish target behavior, conformance, certification, or security of any provider or untested environment.