# Archive Signal Proof Room — synthetic evidence pack

**DRAFT FOR REVIEW. Entirely fictional. No real operational or personal data.**

This pack demonstrates how source records, stable joins, interpretations and gaps can be inspected together. It does not demonstrate ownership of a real archive, rights clearance, buyer demand, model fitness or performance uplift.

## The two fictional episodes

- **SYN-EP-042 / EP-042:** a first intervention is followed by a recorded PASS, then a report of the same symptom returning. A different intervention has a later recorded PASS and a bounded follow-up report. Root cause and lasting causal repair remain unverified. See claims SYN-C-003–012 and their source record references in `dataset.json`.
- **SYN-EP-043 / EP-043:** a similar symptom on another asset leads to a review and an administrative CLOSED status. Outcome verification is absent at the cutoff. Success and failure both remain unestablished. See claims SYN-C-013–018.

All identifiers begin `SYN-`. Display labels such as EP-042 are shortened for reading only. Dates are fixed in 2025 and use UTC solely for deterministic ordering. The records contain no repair procedure, safety-critical specification, real sensor measurement, robot action, or actual permission.

## Contents

- `dataset.json`: complete structured dataset; all interpreted claims cite source record IDs.
- The companion web page uses a separate `data.js` adapter containing the identical object as `window.PROOF_ROOM_DATA`. This web-only file is not included in the standalone ZIP; use `dataset.json` there.
- `raw/SYN-R-001.md` through `raw/SYN-R-014.md`: inspectable invented source records.
- `raw/records.csv`, `raw/events.csv`, `raw/claims.csv`, `raw/joins.csv`: flat exports for independent inspection.
- `evidence-and-rights.md`: claim limits, missing evidence and real-rights diligence boundaries.
- `owner-first-sample-checklist.md`: blank sample-scoping guide.
- `buyer-acceptance-template.md`: blank buyer-specific acceptance template.
- `MANIFEST.sha256`: SHA-256 hashes of the standalone pack's content files. It excludes itself, the web-only adapter, the ZIP, its separate checksum and the source-only manifest.
- `evidence-pack.zip`: this pack, excluding the ZIP itself and its separate checksum.
- `evidence-pack.zip.sha256`: hash of the downloadable ZIP, distributed outside it.
- The authoring source also retains `SOURCE-MANIFEST.sha256`, outside the ZIP, covering the full source directory except that source manifest itself.

## Evidence legend

**Observed:** explicitly recorded in a fictional observation or activity note. This does not verify a real event or the truth of a note.

**Reported:** stated by an invented operator or reviewer, independently unverified.

**Inferred:** an interpretation of the cited invented records. Its limitation remains attached.

**Unknown:** the cited records do not establish the answer. Missing evidence does not establish success or failure.

Record evidence levels describe a source's role; a claim can have a different level when it interprets or combines sources. For example, SYN-R-004 records PASS, while the conclusion that this does not establish lasting resolution also relies on the later report SYN-R-005.

## Inspect and verify

Open `dataset.json` or a CSV in an editor. Resolve any claim's `sourceRefs` against `records[].id`, then open the record's `path`. Follow `joins.csv` to inspect the stable keys. The rights register is SYN-R-014.

On macOS, from the extracted sample directory, run `shasum -a 256 -c MANIFEST.sha256`. On systems with GNU coreutils, run `sha256sum -c MANIFEST.sha256`. Use the separate ZIP checksum from the same directory as the ZIP.

Hashes detect changes to files relative to this manifest. They do not establish authenticity, ownership, lawful use, source completeness, or chronology outside this fabricated pack. No certification is implied.

## Using the blank templates

The templates help parties define a task, a bounded sample, permissions to investigate, and an evidence bar. They are not a contract, executed permission, legal opinion, valuation, or promise that any buyer will accept data. Use non-sensitive descriptions first; actual disclosure and collection require separate authorization and terms.