Hunter Storm Operations (HASOPS) Manual

Hunter Storm Operations Dashboard (HASOPS Dashboard)

The Hunter Storm Operations Dashboard is the operational interface for HASOPS.

It provides a consolidated view of observations, telemetry, system responses, operational activity, and selected measurements generated through Hunter Storm operations.

This is the instrument panel, not the archive.

Current Operations

The dashboard may display:

active and recent operations;
operational status;
system responses;
geographic observations;
availability and accessibility;
discoverability and indexing;
traffic and referral observations;
cross-platform conditions;
longitudinal measurements;
anomalies and notable changes;
operational timelines;
links to supporting records and analysis.

The information displayed here may change as operations continue.

Telemetry

Telemetry represents observations generated through operational activity. Depending on the operation, telemetry may include:

System

What system, platform, environment, or condition is being observed.

Time

When the observation occurred.

Location

Where the observation was made or what geographic environment was involved.

Response

What the system did.

Condition

What was available, unavailable, altered, restricted, indexed, surfaced, or otherwise observed.

Change

How the condition differs from an earlier observation.

Provenance

How the observation was obtained and what supporting record exists.

Dashboard ≠ Evidence Repository

The dashboard presents operational information.

It does not replace the underlying record.

Where an observation requires permanent preservation, evidentiary documentation, or formal records management, the relevant material is maintained through the Hunter Storm Records Management System (HSRMS).

The dashboard is the view.

The record is elsewhere.

Operational Applications

HASOPS may include multiple purpose-built applications.

These applications can support specific operational requirements without requiring every function to be incorporated into one dashboard.

Examples may include:

geographic observation;
system availability monitoring;
discoverability and indexing analysis;
cross-platform comparison;
longitudinal telemetry;
operational anomaly tracking;
response monitoring;
specialized analytical tools.

Additional applications may be introduced as operational requirements develop.

Reading the Dashboard

Dashboard information should be interpreted according to its provenance and measurement conditions.

A displayed observation is not automatically an explanation.

A correlation is not automatically causation.

A change in telemetry does not by itself establish why the change occurred.

Where interpretation is required, the underlying analysis and supporting records should be consulted.

The dashboard shows what has been observed.

The associated analysis addresses what the observations may mean.

Live Systems, Changing Conditions

Operational telemetry is inherently time-dependent.

Platforms change.

Systems change.

Policies change.

Algorithms change.

Access conditions change.

The dashboard therefore represents an operational view of a changing environment rather than a permanent description of the world.

Historical observations remain important precisely because they establish what was observed under particular conditions at a particular time.

Operational Record

Where available, dashboard observations may link to their associated operational records, analyses, or evidence within the Hunter Storm ecosystem.

This creates a chain from:

Operation → Observation → Telemetry → Analysis → Record

The dashboard provides the operational view across that chain.

The Operations Layer

The dashboard is one component of HASOPS.

Additional dashboards and applications may be added as the operational system develops.

Observe the system.
Measure the response.
Preserve the record.

Hunter Storm