# MERIDIAN 1.3.1 — Delivery record

## Working product

MERIDIAN is a self-contained GW150914 replay workspace. This portable project contains the interface, original public scientific files, processing source, receipt verifier, tests and numerical reproduction tools. The public deployment is hosted on Vercel at https://meridianlab.xyz/.

Version 1.3.1 improves first-use comparison, mobile navigation, pending-setting validation, receipt preservation, transaction-reference recovery, and Windows build/release portability. Read GUIDE.md for the user workflow and docs/ACCEPTANCE.md for physical-device, wallet, deployment, and product-validation work still requiring external participation.

| Area | Implemented behavior |
| --- | --- |
| Signal replay | Real H1/L1 input hashes, worker processing, adjustable filters, strain/time-frequency/lag plots and recorded-speed audification. |
| Published context | Official posterior samples and sky localization with source attribution and explicit reference labels. |
| Reproducibility | JSON/HTML reports, SHA-256 identity, imported-report replay, independent SciPy implementation and six-configuration comparison. |
| Run archive | Up to 20 local runs, comparisons, rerun receipt retention, complete JSON backup and atomic restore after every report reproduces. |
| Wallet evidence | Explicit desktop extension selection via EIP-6963, OKX injection fallback, EIP-191 signatures, compatible legacy signatures, and optional zero-value self-transactions on Base Sepolia or Base. |
| Receipt recovery | Verify an existing included transaction and attach its receipt without a new transaction or a wallet connection. |
| Network checks | Chain, sender, recipient, digest, zero value, successful status, block identity and transaction position; pending and unavailable states remain explicit. |
| Delivery | English interface, responsive layout, local fonts/data, source download, standalone verification and executable integration checks. |

## Reproduce the release checks

Use Node.js 22.22.2+ (22.x), 24.15+ (24.x), or 26+ and Python 3. The scientific dependency versions are in `requirements-validation.txt`.

```sh
npm ci
python -m pip install -r requirements-validation.txt
npm run verify:release
npm start
```

`dist/data/release-checks.json` records actual successful checks, source hashes, runtime, generation time and the default report digest. It is generated by the project, not a third-party certification. A failed command stops generation. `npm test` and `npm run test:integration` can also run separately without NumPy/SciPy; use `npm run build` first after changing browser source.

The release command directly starts Node scripts on all platforms, including Windows. Set `PYTHON` to an executable path if the desired Python is not discovered automatically. `npm run test:tooling` checks Python path handling and complete source packaging, including paths containing spaces and invocation from another working directory. Starting a release check invalidates its previous local success record; a new success record is written only after every required check passes.

Regression coverage includes tolerance-matched imports with existing or conflicting signatures, pending/invalid settings, visible retry feedback, storage-full and unavailable states, failed transactions, and transaction-reference removal that preserves the prior receipt when storage fails. Network and wallet interfaces in DOM tests remain simulated.

Desktop wallet regression checks also cover simultaneous OKX/MetaMask-style providers, duplicate and late discovery announcements, OKX-only injection, explicit selection, rejected signatures, fixed-provider network switching and submission, and analysis without a wallet. Real installed Chrome extensions still require wallet-holder acceptance.

The source archive includes these checks. No test needs a funded wallet, account, API key or public-network transaction. The local EVM test creates disposable accounts and executes the actual receipt transaction locally. DOM tests use real signal processing and cryptography with simulated browser wallet, audio and RPC interfaces. They do not substitute for physical-device or live-wallet acceptance testing.

## Verify a real network receipt

```sh
node scripts/verify-chain.mjs /path/to/MERIDIAN-report.json
```

This read-only command checks the exported report and the selected Base network's public RPC. Exit 0 means included and consistent, 3 means pending/not found, and 1 means the check failed. It never signs or sends a transaction. Public RPC availability is required; inclusion is not finality or independent consensus verification.

## Archive portability

Use **Back up all runs** to download a portable JSON file. **Restore backup** verifies every report and reruns its calculation before one atomic save. Existing runs remain intact when a report is damaged, cannot reproduce, exceeds capacity or cannot be stored. Matching reports merge compatible missing receipts. Existing receipts take precedence when wallets or transactions differ; keep the original backup for the other receipts. Restoring a saved transaction does not recheck its current inclusion: use **Check confirmation** for that.

## Explicit boundaries

- Only GW150914 is supported. Adding arbitrary events requires a separately reviewed data and analysis configuration.
- The browser does not run Bilby parameter estimation or infer a new sky map. Mass/distance posteriors and the sky map are published GWTC-1 products.
- Saved runs are local to a browser. Backups move them between devices; there is no hosted user database or automatic cloud synchronization.
- Wallet signing requires an injected EVM wallet. There is no WalletConnect relay or custodial key storage.
- The MRDN community token is issued through Pons on Robinhood Chain at `0x234a1618785262813266c5a439dcab31da674d75`. This website links to its public record; its scientific workflow has no token requirement, staking, rewards, trading execution, or scientific ownership claim.
- Public-network signing, gas payment and transaction approval belong to the wallet holder. No such transaction was executed for the automated release check.
- The production website and its downloadable project archive are public.

These boundaries describe this release. They are not completed features or hidden promises of future delivery.