# Local verification — September 29, 2026

Scope: extension of the September 28 public-site source release feff50804aeee114. No production deployment performed. Node v26.8.0-alpha.0.0.0 on Windows x64; Codex in-app browser at localhost. No external package installation.

## Implemented

- Existing Home design and website-service offer retained; its Explore link now names Preserve, Ask, Verify.
- All generated page headers use the existing Home shell, including supporting pages and Operator Access. Operator destinations and existing recovery demonstration remain.
- One browser-local text document with up to 100 versions, 20,000 characters each, stored in a separate IndexedDB database. A successful transaction precedes acknowledgment. Concurrent writes compare the complete expected snapshot inside the transaction and reject stale tabs.
- Deterministic local comparison with source-version references and Show the Record. No AI model is invoked or impersonated.
- Fingerprint and sequence consistency verification, explicit Continue event, raw JSON export, and content removal retaining only deletion timestamp and count. No cloud transport is implemented for these records.

## Executed

- 21 automated tests passed. Existing 16 tests retained, with the navigation test extended to supporting pages and the former prohibition on public Jameson Constant content narrowed to keep only the original private draft excluded, as authorized in this request.
- Five new tests cover retained source versions and continuation, tampering/reordering rejection, invalid/duplicate/oversized input, JC comparison boundaries, and deletion receipt content with a fresh subsequent chain. Raw output: test-results.tap.
- Browser: preserved “Review on Monday.”, then “Review on Tuesday.”; Ask identified source versions 1 and 2; Show the Record displayed both complete texts and linked fingerprints. Continue was refused before Verify. Verify → Continue produced a third version, retained after reload.
- Browser: two tabs loaded the same history. The first saved a new version. The stale second tab was refused; its draft remained visible and newer storage was not overwritten.
- Browser: stopped the preview server, reloaded from the warm public cache, saved another text, asked, verified, continued, and reloaded. Six versions and the latest text remained. This checks server-unavailable local operation, not a physical network disconnect or a full browser/device restart.
- Desktop visual inspection retained the navy/orange design and readable form layout.
- JC-001: PowerShell launched a real child that exited 23. Parent-captured stdout and stderr conflict with the unchanged false completion claim. Both are in jc-001.json. Unique run directories retain earlier attempts. Hashes bind the tested source and harness. The original blocked attempt remains in jc-001-blocked.json.

## Limits and untested areas

Browser storage can be cleared, evicted, or read/rewritten by a compromised same-origin application or browser profile. Fingerprints provide internal consistency, not authenticity, authorization, truth, tamper-proof history, or guaranteed physical durability. This is not a secure node or encrypted vault. Operator authorization in the separate beta was not altered or retested.

The deletion transformation was unit-tested; the final browser deletion control and export download were not exercised. Deletion does not remove external copies, exports, browser/device backups or stale copies held in other tabs, and is not verified physical erasure. No device identity, ownership transfer, secure erasure, or Blututh OS implementation is delivered.

No live AI integration, multi-node sync, quarantine of network changes, production storage fault injection, power-loss test, complete browser restart, physical touch-device test or screen-reader audit was performed. Optional future network services must preserve authority and privacy boundaries. Historical foundation and public-site reports retain their original scope and are not rerun production claims.

## Reproduce

Run npm run build, npm test, and node preview.mjs 8794 from the supplied source folder. Open /explore/. For JC-001, run scripts/jc-001.ps1 in PowerShell; each invocation creates a unique docs/current/runs directory with the claim, stdout, stderr, execution observation and final report. The earlier Node parent harness remains for examination of the blocked attempt. Public text copies of the harness should be placed in the same scripts layout to reproduce from individual downloads.

Failures and corrections: failures.md. The raw test transcript is captured before embedding it as a public asset; a final packaging test is retained separately with the release review.