Recovery 35.6.78 — Release Diagnostics & Upload Scope Repair: demonstrate consistent browser/server build status and clean deployment scope. Windows NTUSER/AppData files are not part of Vanguard V.E.M.
Recovery 35.6.60 — Military Installation Handoff Receipt & Carry-Forward Actions closes the operational-period turnover loop. Demonstrate Handed Off → Received / Acknowledged, then create/refresh carry-forward tasks for unresolved source coordination items and verify they appear in My Work with source IDs/versions, ownership, priority and due/review context preserved.
Recovery 35.6.59 — Military Installation Coordination Brief & Shift Handoff turns the installation Community Impact Dashboard into a saved briefing snapshot for operational-period turnover. Demonstrate source traceability, source-change freshness warnings, Draft → Validated → Handed Off status and the receiving shift/team handoff.
Recovery 35.6.58 — Military Installation Community Impact Dashboard & Coordination Picture converts permission-visible civil-coordination records into an installation-level briefing view of open workload, priorities, affected jurisdictions, ownership, deadlines and recent changes. Every dashboard item drills back to its source record; sensitive installation-security information remains excluded.
Recovery 35.6.57 — Military Installation Civil Coordination & Community Impact adds a permission-backed coordination board for non-sensitive adjacent-jurisdiction impacts, government/liaison handoffs, support requests, public-facing impacts, ownership and due/review tracking tied to the active installation AOI and incident. Sensitive installation security information is explicitly excluded.
Recovery 35.6.56 — Military Installation Operational Context & Readiness adds a dedicated installation workspace that confirms the active installation, map/source details, incident and position readiness, and direct launch paths into Intelligence, Response/ICS, ICS/IAP Readiness, dashboards, Operational Copilot, Operational Memory and Forms while retaining the same AOI and permissions context.
Recovery 35.6.55 — Military Installation Map ↔ AOI Bidirectional Selection makes the Military Installations GIS/COP layer interactive. Select an installation boundary to inspect source/details, zoom to the boundary, or make the installation the active AOI; the active installation is highlighted and labeled on the map.
Recovery 35.6.54 — Military Installation AOI / Map Layer Direct Selection makes Military Installation visible directly on the primary AOI page with State/Territory → County/Parish/Borough → Military Installation selection, manual fallback, structured installation coordinates, and automatic activation of the Military Installations GIS/COP boundary layer when an installation AOI is active.
35.6.53 — Runtime Build Normalization / Cache Integrity: Active runtime surfaces now use one normalized build identity, the Hybrid shell advances to a fresh v3 asset, and Release Coherence detects stale deployment tokens across PHP/JavaScript/HTML. Recovery 35.6.52 release verification and 35.6.51 Mission Packs/Military Installation capabilities remain cumulative.
Vanguard VEM
Vanguard VEM Solution Demonstration

Connected operations from preparedness through recovery.

Select an operating environment to see how Vanguard VEM connects situational awareness, organizations, assignments, workflows, reporting, coordination, accountability and recovery.

One connected operating context: AOI, incident, organization, role and permissions carry through the workflow so information does not have to be rebuilt at every step.
Current enhancement layer - Recovery 35.6.33: Professional Platform & Workflow Enhancement Phase 2 adds record following, comments and @mentions, direct record links, recoverable drafts, detailed version history, What Changed Since Last Visit, non-destructive workflow testing/version rollback, Briefing Mode, and freshness/confidence indicators. It also repairs Live Intelligence chart/workspace Open actions so a selected item opens its Readable Source Brief. Phase 1 capabilities remain cumulative. No modules are added and operational judgment fields are not silently populated.
Current intelligent-operations layer - Recovery 35.6.49: Operational Copilot adds incident/AOI-scoped governed synthesis, priority attention, structured operational questions, direct source-record links and review-required draft Command, Situation Report, Shift Handoff and Planning language. Human review, source verification, permissions and command authority remain controlling; Copilot does not modify operational records.
Current memory/AOI layer - Recovery 35.6.50: Operational Memory connects same-AOI prior incidents, AAR/corrective-action evidence, recurring gaps and decision/resource precedent while keeping historical evidence separate from current intelligence. The detailed AOI selector now includes Military Installation immediately after County/Parish, and installation AOIs carry through maps, Response, Intelligence, Guided Operations, Copilot and Operational Memory while retaining the user's preferred map view.
Current deployment-assurance layer - Recovery 35.6.53: Runtime build identity is normalized across active PHP/JavaScript/HTML surfaces, the Hybrid interface advances to v3 to defeat stale cached copies, and /runtime/release-coherence.php scans the deployment for older build tokens. The 35.6.52 live BUILD.txt verification and root /VEM_RELEASE_CHECK.html remain cumulative, along with 35.6.51 Mission Packs and Military Installation GIS/AOI support.

Operational Memory & Lessons

Connect current AOI work with permission-visible prior incidents, lessons, corrective actions and recurring operational gaps. Historical evidence stays clearly labeled and links back to its source record.

Recovery 35.6.71 — Decision Lifecycle & ICS Traceability

Significant operational decisions now carry the responsible ICS position/function and operational-period context, expected result, reconsideration triggers, review date, linked follow-up action when required, and later outcome/effectiveness review. Existing decisions can be reopened for review. Linked ICS 214 decision entries are updated when the existing linked record remains available rather than intentionally duplicated. ICS Position Workspaces link directly into the Structured Decision Log.

Recovery 35.6.70 — Decision Rationale, ICS Personnel Photos & Military AOI Resilience

Operational decisions now capture the decision/outcome separately from the reason or rationale and supporting inputs, with an optional default-on linked ICS 214 activity entry. Response staffing displays the existing optional personnel photo in the ICS assignment table, ICS Structure / Staffing chart, position workspace and chain-of-command view when available. Military Installation AOI and GIS/COP add last-known-good server/browser cache paths in addition to live Census access and browser-direct fallback.

Recovery 35.6.69 — Military Installation AOI Data Availability Repair

Military Installation selection is repaired. Vanguard now queries the current U.S. Census TIGERweb Military Installations layer with valid 2025 fields, uses POST-based server requests to avoid oversized geometry URLs, and automatically falls back to a browser-direct Census request when the hosting server cannot reach TIGERweb. A Retry Census Data control is available on AOI Selection. The existing Military Installations GIS/COP layer remains synchronized with the selected installation.

Recovery 35.6.67 — Readiness Risk Register & Governance Review Board

Military Installation readiness governance now includes a leadership risk register, retained governance decision history, review-board dispositions, restoration ownership and due dates, and portfolio views for open exposure, pending or active exceptions, expiring risk acceptances, due reviews and restored controls. Review-board actions do not silently change the authoritative assurance or exception state.

Recovery 35.6.66 — Readiness Assurance Governance

Military Installation readiness assurance now includes leadership escalation and temporary exception governance for non-current controls, with accountable ownership, authorized decisions, compensating controls, expiration and review dates. Approved exceptions remain temporary risk acceptance and do not make a control Current / Assured.

Selected suite

Operational needs addressed

    Example operational scenario

    Connected operational workflow

    How the workflow connects

    Explore the operating environment

    Designed for
    Operational separationTraining and practice can remain separate from live operational records.
    Example information
    Explore SandboxExplore ProgramProgram Overview
    Build 20260823-recovery35-6-78-release-diagnostics-upload-scope-repair. The Solution Demonstration presents Vanguard VEM capabilities without creating operational records.

    New in Recovery 35.6.63: demonstrate the improvement loop after a failed closure check: Continuous Improvement finding → owner/due date → corrective action → Ready to Verify → effectiveness evidence → source re-resolution.

    New in Recovery 35.6.62: demonstrate the full accountability loop through closure verification: resolved coordination source → verification evidence → Verified Effective, or reopen → Continuous Improvement.

    New in Recovery 35.6.61: demonstrate the full turnover loop: handoff → receipt → carry forward → task completion → explicit source reconciliation.

    New in Recovery 35.6.64: demonstrate the full learning loop after a corrective action is verified effective: recurrence review → improvement-plan target → implementation owner/deadline → Ready to Validate → readiness evidence → Institutionalized.

    Recovery 35.6.68 — Governance Action Register

    Military Installation readiness governance now carries Review Board follow-up actions into a dedicated action register with owner, due/checkpoint, progress, dependency, evidence-backed completion, retained action history, My Work routing, and printable/exportable board follow-up packets. Completing an action does not silently restore assurance, approve an exception, or close the Review Board item.

    Military Installation Readiness Assurance & Evidence Register

    Institutionalized lessons now enter a sustainment-assurance lifecycle. Authorized users can assign evidence ownership, identify the readiness-control/version reference, record validation evidence and results, set the next review date, and route due or failed revalidation back into My Work. The register remains limited to non-sensitive civil/community coordination readiness information.

    Recovery 35.6.75 — Client Account Lifecycle & Renewal Decision History

    Developer-only commercial administration now preserves a chronological client lifecycle record for activations, pilots, renewals, changed terms, exceptions, suspensions, closures and reopenings. Material entries retain the decision or change, the reason/rationale, authorization, linked subscription, status effect and follow-up. Corrections supersede rather than delete prior entries, while commercial account status remains separate from emergency operational access.

    Recovery 35.6.74 — Client Renewal Cadence & Account Health

    Developer-only subscription administration now adds calendar-based renewal notices at 3 months, 2 months, 1 month and 1 week before the recorded subscription end date. The Renewal Center tracks the responsible renewal owner, dedicated renewal contact, next follow-up, reminder history, current account health, CSV export, host-email delivery with draft fallback, and a CLI scheduler for daily automated checks. Commercial renewal status never silently changes emergency operational access.

    Recovery 35.6.73 — Client Entitlement & Deployment Control

    Internal Developer administration now connects client purchase history to structured suite/module entitlements, authorized seats, implementation stage, deployment environments, build/version references and seat-utilization review. Commercial entitlement records remain separate from operational CRM and do not automatically suspend emergency access.

    Recovery 35.6.72 — Client & Subscription Administration

    Internal Developer administration now includes a protected Client & Subscription Registry for purchase history, subscription periods, renewal tracking and client contacts. Commercial terms remain separated from operational CRM and are not exposed to customer administrators.

    Recovery 35.6.77 — Usability 9 Wave 2

    Demonstrate the new universal Workflow bar on an operational page: Go Back/Home, AOI and incident readiness, My Work, resume-last-workspace guidance, unsaved-change protection, required-field focus and clear prerequisite messaging. Wave 1 zero-dead-end feedback remains cumulative.