# Riverton Landing reproduction — artifact 1.2.1

Both recorded runs reproduced the sealed Deliverable, canonical producer evidence,
post-seal verification and bounded public slice byte-for-byte. The fixture manifest and
source expectations are immutable inputs, verified unchanged, not recomputed outputs.
The table reports all five source-manifest digests plus the bounded-slice digest.

## Boundary

Model-assisted extraction reads the documents; the arithmetic downstream of extraction
does not vary between runs. These runs start from the sealed extraction output, not
the raw documents. Extraction accuracy, repeatability of fresh model calls, and rendered
HTML/CSS/JavaScript bytes are outside this claim. This is synthetic public-demo regression,
not a golden anchor, holdout accuracy result, or ratification evidence.

The extraction seal contains parsed workbook/PDF observations and the original
source-derived assembly observations. Its PDF structures came from the original
content-addressed model decisions (anthropic:claude-opus-4-8, resolved model
claude-opus-4-8) and were fused against the PDF text layer. No model was called to
create this report. The replay receives these sealed observations and reruns the real
backend structure, summary, reconciliation, detail, mapping, validation, kernel and
Deliverable assembly functions. Original source bytes are retained only for source
hashes and parser identity; the replay does not extract their contents again.

Backend revision: 7560ed0be754afd1040a06330baf8be4030e30ae

Kernel registry: 0.9.0. Package manager: pnpm 10.23.0. Dependencies were installed from
the frozen registry lockfiles. The bundled backend source snapshot contains the replay's
required files from that revision; every archived file is hash-checked before execution. No sibling checkout,
database, cache service or provider credential is required for replay.

Sealed extraction: sha256:10b56b4633e5472cd34efaddfdb86c8f1ba20d9308157c75e2c86511747d44e9

Producer evidence uses canonical-environment-free.v1: runtime and cache-preparation
metadata are omitted, per-decision cache-hit flags are omitted, and model identities,
versions, fingerprints and decision hashes are retained in decision-hash order.
Input authority, actual production stages, backend file hashes, extraction digest and
output digest remain covered. Runtime observations belong here, outside that digest.
This evidence reseal binds the merged INN-334/INN-374 implementation. The Deliverable's
property-tax terminology and run-manifest metadata change; its financial values do not.

## Recorded runs

Run A used a freshly unpacked, hash-verified backend snapshot with a fresh dependency
installation on macOS and an empty process environment except HOME and PATH.
Run B used a fresh Linux container and separate registry-installed dependency trees;
recomputation ran with Docker network access disabled and no credentials passed.
The publisher candidate was identical in both environments. Both hosts use ARM64;
this record does not claim an x86 run.

| Run | Started (UTC) | Completed (UTC) | Node | OS | Architecture |
|---|---|---|---|---|---|
| A | 2026-09-15T20:47:32.534Z | 2026-09-15T20:47:33.929Z | v24.14.0 | darwin | arm64 |
| B | 2026-09-15T20:48:43.418Z | 2026-09-15T20:48:47.331Z | v24.21.0 | linux | arm64 |

## SHA-256 comparison

| Artifact | Run A | Run B |
|---|---|---|
| fixtureManifestSha256 | sha256:b0250bed3ce927390e516ae8e170c73ed4129e2f88b83e829bb89291a422e5ec | sha256:b0250bed3ce927390e516ae8e170c73ed4129e2f88b83e829bb89291a422e5ec |
| deliverableSha256 | sha256:f730e14b43a955934c63126b5fef374d959df8f4c8a9579873af31c86c7fa305 | sha256:f730e14b43a955934c63126b5fef374d959df8f4c8a9579873af31c86c7fa305 |
| producerEvidenceSha256 | sha256:41cd9a61b3061483bd2549d9b8f8c6cda0652e8f253beaa7d30c0f3925c4a43b | sha256:41cd9a61b3061483bd2549d9b8f8c6cda0652e8f253beaa7d30c0f3925c4a43b |
| postSealVerificationSha256 | sha256:b9e9c5b4487b0330eaf90bba6f18f022583b06f3ed856cd8a503329ff64c9448 | sha256:b9e9c5b4487b0330eaf90bba6f18f022583b06f3ed856cd8a503329ff64c9448 |
| sourceExpectationsSha256 | sha256:12e6ce717e3e07aba8ece3ac98a27a06e336060641737f8502ff79191dec2bd8 | sha256:12e6ce717e3e07aba8ece3ac98a27a06e336060641737f8502ff79191dec2bd8 |
| boundedSliceSha256 | sha256:82d50d11a9b07024231c2b09681fde07bc41382efb4a7fcd554ef2e5505f1d92 | sha256:82d50d11a9b07024231c2b09681fde07bc41382efb4a7fcd554ef2e5505f1d92 |

## Repeat the check

From an atrium-web checkout containing this artifact, with Node 24 and pnpm 10.23.0:

```sh
pnpm install --frozen-lockfile
WORK=$(mktemp -d)
node sample-deal/reproduction/snapshot.mjs "$WORK/backend"
pnpm --dir "$WORK/backend" install --frozen-lockfile --ignore-scripts
node sample-deal/reproduction/check.mjs "$WORK/backend" "$WORK/run"
node landing-slices/generate.mjs --check
```

Repository and private package access are required to install the engine; this report
does not imply public access to its source. The public page ships this exact committed
report as a download, so reading it does not require GitHub access.

CI executes the same check on pull requests and before either sample-deal or landing-slice
package publication. Any extraction/source pin mismatch, changed Deliverable, evidence,
verification, bounded output, or landing projection fails the job before publication.
The committed machine-readable run records are adjacent to this report; future CI runs
print their own timestamps and digests rather than overwriting this dated record.