Reproducible technical evidence
Unseen OS / Unseen Lifeline v0.3 Verification
The local prototype was reconstructed from one frozen private working archive and passed the final expanded acceptance gate on clean GitHub-hosted Windows and Linux runners. This page records what was actually verified, the exact Release Candidate identity, the privacy boundary around the source, and what remains outside the claim.
Final verification snapshot
Two operating systems. Expanded state changes. One gated Release Candidate.
The final gate used private source code and fictional test records. No personal database, private inbox, credentials, or production user data are published here.
Source and release identity
The evidence traces from one exact working package to one exact Release Candidate.
The source package and Release Candidate are retained privately in the controlled build hierarchy. Their hashes make the validation boundary reproducible without publishing private runtime data.
Validated source archive
Validated v0.3 Release Candidate
Unseen_Lifeline_v0.3_Working_Upgrade_Pass2.zip
SHA-256: a2f7c4602e9cfba3c7ac272ee4bdd7718ccb20719b867d4f65246711c74651fbValidated v0.3 Release Candidate
Unseen_Lifeline_v0.3_Release_Candidate.zip
SHA-256: 1da6b8513d8d8e9234e06c18cefe7d044d643a2f305202180b231a27b60ce91eThe frozen Unseen OS v0.2 package remains the rollback baseline. The v0.3 Release Candidate is a verified local-first demo, not a public production service.
What passed
Verified behavior from installation through state changes, exports, reset, and recovery evidence.
The expanded browser run supplements the unit/core pipeline by exercising the application through the real local UI and HTTP surface on both Windows and Linux.
Windows exercised the project’s PowerShell setup path; Linux used a fresh virtual environment installed from requirements.
Five fictional notices/documents were parsed, analyzed, persisted, and converted into continuity records by the deterministic local fallback path.
The local UI surfaced five processed records through Dashboard and Life Archive views.
A synthetic extracted field was explicitly confirmed through the browser, verifying the human-review state transition.
A synthetic notice was reprocessed, the evidence view refreshed, and the modal returned cleanly to the navigation flow on both operating systems.
Continuity Board and Notice Response rendered the linked action/evidence model for the synthetic test records.
A fictional follow-up action was created through the UI and then changed from New to Done through the Continuity Board.
The application generated a weekly review plus action-summary and document-summary CSV exports.
The reset removed designated sample/test records while preserving non-sample records, matching the UI’s stated scope.
A timestamped local SQLite backup was verified before the sample/test reset operation.
Non-loopback Host requests were rejected; state-changing requests required the local mutation header; security response headers were verified.
The gated package contains source, synthetic fixtures, documentation, setup scripts, and empty runtime placeholders, with no populated database or private archive.
Hardening discovered by verification
The test process found defects and cross-platform edge cases instead of merely confirming the happy path.
Issues found during clean-run validation were corrected in the Release Candidate path before this final evidence record was published.
Dynamic HTML output encoding
Mutable values inserted into browser-rendered HTML were not consistently encoded. Output encoding and constrained CSS-state classes were added.
Inbox placeholder handling
A repository .gitkeep placeholder could be interpreted as an inbox document. Placeholder files are now excluded.
Filter-value contract
Default HTML filter values did not match the renderer contract, hiding valid records in Archive and Continuity views. The contract was aligned.
UI presentation recovery
Recovered dashboard and Notice Response elements were missing a small set of presentation classes. Spacing and fact-card hierarchy were restored without changing the data model.
Reprocess continuity
Document identity and modal-state behavior after reprocessing were exercised as first-class acceptance paths so stale or cross-platform UI state could not silently pass.
CSP-compatible interaction
Browser interaction hardening was aligned with the application’s Content Security Policy rather than weakening CSP to accommodate unsafe inline behavior.
Security and privacy boundary
Local security and privacy controls.
The validated prototype binds locally and preserves private source/runtime state outside the public portfolio. The Release Candidate inspection found no populated SQLite database, private processed archive, absolute personal path, or credential file; the environment example contains a placeholder only.
The optional Gemini-provider path was not exercised because no provider credential was supplied to the clean validation runners. The deterministic local fallback path is the validated behavior represented here.
Evidence files
View the public verification record.
These files contain the machine-readable public subset of the final expanded validation record. Private source code, Release Candidate bytes, and runner artifacts remain outside the public site.