AirfieldpathOrlando Sanford International

7.2 · The platform · Components

MissionSight

MissionSight gets mission data in from any platform, and lets each product decide what to do with it. A drone,

23:05

Picture: Frame at 189 seconds of the film airfieldpath-missionsight.mp4, the brightest of 24 sampled.
Clip: Excerpt of the film airfieldpath-missionsight.mp4, 188 to 192 seconds. No sound.

Film · Films · Further films

MissionSight

The mission-data and vision engine the products share, from the plan to the flight to the check, then through the Fleet World where the Conductor, the Spectrograph and the cloud are taken apart.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Film
Status
not linked
Airport layer
not linked
Airport area
not linked
System
not linked
Sensor type
not linked

Open the detail

Level 2 of 3 This component, complete on its own. Its files, sources and tests are the detail below. Open the detail

Repository
missionsight

MissionSight gets mission data in from any platform, and lets each product decide what to do with it. A drone, a phone, a fixed camera or a weather sensor captures; MissionSight receives every capture as known, indexed, trusted data (what flew, on which mission and pass, with which instruments, in which conditions). Products in the stable (SprayPath, Municipath, Airfieldpath, the Viking Platform, Field Twin) register what they want seen, and get observations, findings and evidence back.

Status, 2026-11-05: phase 0, the foundation. The model, the contracts, the first definitions and the pure judgment code are written and tested. The api, the Setup Studio, the Tender, the workers and the infrastructure are laid out and not yet built. Every folder that is empty says so in this file, not with placeholder code.

What is here

PathWhat it holdsState
docs/model.mdThe information model: 41 entities in eight groups, seven observation kinds, the flowwritten
docs/acceptance/walters-pre-inspection.mdThe acceptance test: the day-before roof deck inspection flight at a Walters Cypress 2written
docs/consistency.mdHow MissionSight follows SprayPath, the Viking Platform, Municipath and Airfieldpathwritten
docs/backbone.mdThe twin pattern, schedule, validation and versioning, sensor to Kinesis, events, LDS, support, cloud, SOC 2, what StellarView supplies, and the supporting filmswritten
docs/rudiments/Five rudiment plans in StellarView's form; each waits for its Studio screenwritten
staging/e1-missionsight/requirements.mdRequirement ids REQ-MS-###, each with phase, screen, class, acceptance, evidencewritten
contracts/definitions/JSON Schema (2020-12) for every definition a product registerswritten
contracts/events/JSON Schema for every event on the Kinesis data streamwritten
definitions/Definitions as data, one folder per product and use: the Walters inspection, the SFB nightly lightswritten
packages/cores/Pure judgment: observation against expectation, coverage against planbuilt, tested
tools/definitions/Validates every definition against its schema and checks every reference resolvesbuilt, tested
tools/writing/The house writing check, vendored from StellarView (see its SOURCE)vendored
apps/api, apps/web, apps/tenderNestJS api, the Setup Studio, the station agentnot yet built
workers/Python reads and learning workersnot yet built
infra/terraform, scripts/deploy/fleet.shAWS on the Fleet, the SprayPath waynot yet built

Run the checks

Everything runs in containers; nothing is installed on the host.

make build        # the workspace image (node 22)
make validate     # every definition against its schema, every reference resolved
make test-unit    # packages/cores and tools/definitions
make typecheck    # tsc over the workspaces