Release notes and known limits

Evidence and site planning live — September 29, 2026 UTC

Explorer now links to evidence and site planning with its selected county, workspace, indicator and tract. Authorized users can see tract indicators, population uncertainty, candidate sites and loaded provider listings together, retain road-access screens, compare compatible candidates and export analytical maps with tract tables and source identities. Read the Evidence and site planning section of the operations guide for the workflow.

Schema62 stores analytical captures separately from ordinary planning notes. Saving and reporting require current export/source permission; changed or revoked evidence is withheld. A compatible rollback can read ordinary planning notes without exposing retained analytical values. Populated restore and isolated writer/browser qualification passed before migration; production checks use read-only accounts.

Road access uses one geometric interior point per tract and a retained Washington car network. Descriptive population totals cover represented tracts, not residents known to be within a drive-time area. Missing road results remain unknown. Comparisons require matching evidence, geography, network, cohort and threshold; no overall clinic recommendation or patient-demand estimate is inferred. Clinic listings remain contextual and outside analytical exports.

Shared rural planning live — September 29, 2026 UTC

The authenticated rural planning workspace and care service directory are live on schema61 for authorized Thurston, Lewis and Pierce workspaces. Projects, tasks, dated funding criteria, program-specific rural screening, sites, feasibility evidence, financial and road-travel scenario comparisons, outcome tracking and private printable/evidence workbooks are implemented. Planning changes retain their actual author and immutable history. The earlier private Lewis analytical brief remains available separately.

The HRSA classification is a retained official Washington rural-tract list with source hash and review date. It is not reused as USDA or Washington eligibility. Travel uses an independently prepared and pinned Washington OSM/OSRM car network, with source date and explicit limitations; there is no live-traffic or population-coverage claim.

The existing local Soldier Data app at 127.0.0.1:14310 accepts the evidence-and-manifest JSON in its Government CHIP planning-input form. The actual browser import, mobile layout, thirteen intake tests and TypeScript check passed. Import fills empty planning fields and one open task; reviewers must complete and approve the receiving form. This is user-mediated file transfer, not background synchronization or a hosted Soldier Data deployment. Real provider verification, site findings, grant decisions and client participation still require actual evidence.

The schema61 migration preserved existing facility reviews. A compatible rollback image, populated-journal restore rehearsal, county HTTP canaries and compiled browser checks qualify the software. No synthetic planning records were inserted in production. Routing is loopback-only, hash-pinned and included with the schema61 recovery tooling; full-host recovery is not claimed.

Care-access verification live — September 29, 2026 UTC

The next rural planning software increment adds five structured care-access groups to the authenticated facility review page: hours, patient access, payment options, accessibility and service-specific availability. All retain dated evidence, actual reviewer identity, revision conflict checks, source-change holds, expiry and withdrawals.

The server/browser and county refresh tooling use one shared field contract. Unknown values stay distinct from negative answers and zero. Hours reject missing time zones and overlapping intervals; capacity figures are bounded, service-specific and dated. Existing source listings and export permissions remain unchanged.

The compatible county operator runtime is installed and the feature is live. Candidate, target and public phases each passed 63 HTTP checks. Candidate and public browser checks covered care-field responses, viewer read-only behavior and mobile layout in Thurston, Lewis and Pierce. Actual James-account authorization confirms review access; editable forms and save/reload/withdraw behavior were exercised in the local database/browser tests. No synthetic clinic decisions, provider outreach, membership changes or database migration were performed.

Initial rural planning brief — September 28, 2026 UTC

The initial private Lewis County brief and reusable operator workbook are implemented. Generation used an actual owner account, existing county analytical export authority and publication-time source recheck. The report carries five measures with source periods and uncertainty, three unranked project concepts, six dated funding research entries and explicit evidence gaps.

Immutable workbook revisions bind the county/project scope and funding catalog, reject conflicting updates and preserve previous hashes. Criterion notes require dated evidence and never automatically establish program eligibility. Tests cover authorization/revocation, missing values, unsafe content, file collisions and desktop/mobile/print behavior.

This was a private operator release. Its original follow-on software is now provided by the shared rural planning release above. Provider field verification and real project evidence remain separate from software completion.

Lewis/Pierce personal workspaces · September 28, 2026 UTC

Application 8d63af9a is live on schema 60. James owns both personal county workspaces, with clinic/OSM mapping, review, 59 analytical measures and generic HTML evidence annexes. County sponsorship and complete-inventory claims are not established.

Both weekly county plans are enrolled with automatic activation and read-only review-journal synchronization. Each passed an actual prepare/compile/stage/promote cycle. Final candidate, target and public phases each passed 63 HTTP checks, followed by ten public browser checks covering profiles, map counts, annex downloads and mobile layout.

Operator-only correction 348bff07 fixed the candidate port probe for recently closed connections while preserving rejection of a live listener. It does not change the accepted browser image. All refresh/status timers were restored and the test account returned to viewer; James retained owner export access.

Backup 20260928T173215Z passed an isolated schema-60 restore in 4.41 seconds and off-host verification. Health/readiness passed at 17:34:06 UTC. Valid cached OSM snapshots were retained after upstream acquisition failures. Full-host recovery and external alert delivery remain separate work.

This documentation revision records the completed deployment. It does not deploy a new application image. Earlier release entries below describe their original versions.

U4 · Released September 26, 2026 Pacific

U4 added 58 tract measures and county-level community resilience, the Washington-scoped equal-weight overlap view, tract profiles, and four additional critical-facility layers. Existing U3a evidence and admitted annex exports remain available.

The production image was activated September 27 at 03:22:22 UTC. Owner/member public checks and the owner’s browser verification passed. Cleanup completed and automatic upgrades resumed after approval.

Application commit: fbd5c9d84a83f06ec00c9ddb707f15d6a6ae381e. Image digest: sha256:ba0ab5584816f804177d7bc81f061f19e63e8589527d83cc1c4b383c03d6dc78. Documentation changes made after this release are not part of that immutable image.

Documentation portal · Follow-up change

This portal adds audience-specific manuals, illustrated tutorials, search, a generated 59-measure dictionary, role and route references, a U4 OpenAPI contract, operational guidance and documentation validation.

The documentation portal is included in the U3b release package. Historical U4 test counts below describe U4 only; U3b has separate application, data, browser and deployment evidence.

U3b · Annex and worker release package

This version documents the U3b implementation. The operator release receipt records whether this package is active; a local preview or candidate container does not establish production activation.

U3b adds owner-author review labels, saved supplemental selections, up to five additional Thurston measures, optional same-county overlap, and separately attributed storm-history captures. Frozen snapshots feed PDF, Word and CSV exports with current source and registry checks. Draft edits invalidate prior review.

D6 admits 4,207 successor registry entries, including 3,597 M1 observations. D5 adds 54 annual county-designated and zone-allocated storm observations derived from the 234 reviewed export records. Storm narratives and demographic details are excluded. Missing impacts and unassessable FEMA values remain missing.

The deployment retains schema 59 and predecessor data versions. A production backup was restored into a separate database and checked before removal. All 8,528 new and retained analysis/download reads passed on the host database. These checks do not establish a scheduled backup policy or measured RPO/RTO.

Known product limits

• M1 covers five Washington counties. Neighbor values in the Thurston workspace are explore-only; separately admitted Lewis/Pierce workspaces have county-scoped access. The overlap UI is Washington-only in this release.
• The Thurston PDF/Word/CSV annex admits Thurston evidence and at most five selected additional measures. Lewis/Pierce have separate HTML evidence annexes for their admitted county evidence, also limited to five measures. A visible neighbor or national value does not grant export rights.
• Community resilience is county-only; null FEMA statuses are never numeric zero.
• Facility layers disclose incomplete inventories, linked listings and access/status limitations.
• The pilot password boundary lacks self-service recovery/enrollment and MFA. Optional identity code is not evidence of enterprise production deployment.
• The exact-count nonmember burst canary is sensitive to concurrent load and token refill; it passed unchanged in isolation.
• Daily database restore verification and off-host copies do not establish an achieved RPO/RTO or a tested whole-host recovery SLA.
• Some older repository handoffs describe earlier candidates or rehearsals. Prefer the released code, sealed receipts and this version’s explicit status labels.

Clinic and specialty-clinic mapping

Clinic mapping includes CMS/HRSA records and nine checked provider-directory sites, with separate OSM comparison. Distinct provider identities and published aliases are preserved. Cross-source candidates explain name, address, distance and specialty agreement without automatically merging records. Both clinic layers remain exploration only.

This release adds validated weekly source refresh, daily backup with isolated schema-59 restore verification, hourly off-host replication and 15-minute operational checks. See Operations for scheduling, monitoring and remaining recovery limits.

How to read versions

Each release identity pins code, image, data and controls. A documentation revision clarifies behavior; it does not silently change a method, permission, API contract or activation status.

For every subsequent release, update the support matrix, source vintages, API/method changes, screenshots and validation record. Keep breaking changes and migration/recovery requirements visible before users upgrade.

Reusable county onboarding

County onboarding now uses configurable Census boundary acquisition, OSM/HRSA and pinned CMS sources, polygon and freshness checks, cross-source review, immutable release bundles, and runtime county profiles. Supported counties use the same application image without frontend code edits. Real project membership and independently scoped source authority are required.

Generic M1 tract serving and a separately authorized printable HTML evidence annex are available through version-two contracts. This is planning evidence, not a completed HMP or Thurston PDF/Word workflow parity. Accepted analytical source packages are required; automated acquisition covers the supported facility adapters.

The county refresh timer prepares configured counties, holds uncertain changes and retains previous data. Automatic promotion requires an already browser-accepted county/image/profile plus fresh access and HTTP checks. County refresh can follow the verified managed clinic cohort, synchronize the private review journal, and retain a pinned OSM snapshot within its age limit after an acquisition failure. Explicitly pinned analytical bindings survive preparation and refresh. The administrator page /county-operations.html shows organization-scoped refresh and source status. Thurston, Lewis and Pierce have live workspaces. Lewis and Pierce are Soldier Data-operated workspaces owned by James, not county-sponsored deployments. Their clinic listings remain source observations; no county participation or complete-inventory claim is implied. See scripts/counties/README.md for configuration, review and activation commands.

Facility verification - September 28, 2026 UTC

Schema 60 and the authenticated facility-verification page are active. Authorized owners and analysts can record evidence-backed local corrections, verify source values, and withdraw decisions. Readers can inspect the journal. Local decisions remain separate from published map records and annex exports.

Migration, populated-journal recovery, isolated writer tests, and candidate/target/public checks passed. A schema-60-compatible prior application is retained for rollback without discarding journal rows. Automated checks do not establish real-world facility verification or human acceptance.

Automatic journal transfer and weekly refresh are enabled for the enrolled Lewis and Pierce personal workspaces; the site-group directory, reminder delivery and reverse history presentation remain future work. The review page supports explicit physical-site assignment, reassignment and removal with retained evidence and history. Operator expiry gates are deployed. The review page shows server-calculated verification age and applies expiry from the accepted county inventory. No production county review-expiry cadence has been adopted.