Skip to main content

AEROSIM-TS-5

Project task

Classify and present aircraft warnings and control feedback

Normal, warning, and invalid aircraft states are distinguishable through timely, prioritized control-response cues and warnings.

AEROSIM-TS-5Canonical ID TASK-0005
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application — aircraft-state classification and in-flight feedback
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Implement applications/web/src/flight/warnings/aircraft-warning-classifier.ts, applications/web/src/flight/warnings/flight-warning-presenter.tsx, applications/web/test/flight/flight-warnings.browser.spec.ts. Consume only the inputs listed in this contract, publish only its listed outputs, enforce every failure boundary before commit, and prove the listed exclusions remain unchanged through the verification steps.

Implementation contract

Implementation artifacts

  • applications/web/src/flight/warnings/aircraft-warning-classifier.ts
  • applications/web/src/flight/warnings/flight-warning-presenter.tsx
  • applications/web/test/flight/flight-warnings.browser.spec.ts

Inputs

  • FlightInstrumentModel from TASK-0004 with attemptId, sourceStep, validity, and unrounded aircraft/control values required by rules.
  • Versioned WarningRuleSet containing explicit normal, warning, and invalid predicates, severity, priority, and configured presentation/latency limit.

Outputs

  • WarningSet { attemptId, sourceStep, ruleSetVersion, highestSeverity, orderedWarnings } produced by pure classification.
  • Rendered control-response cues and warning state ordered by severity then stable rule ID; invalid source data produces INVALID rather than NORMAL.

Failure boundaries

  • Reject a model with stale attempt, regressing sourceStep, or rule-set version mismatch; do not merge warnings from different steps or versions.
  • If predicates overlap, apply declared priority deterministically and record all matched rule IDs; never publish contradictory NORMAL and WARNING/INVALID states.
  • Fail when any classification-to-render sample exceeds the configured limit or sustained heavy-scene execution exceeds configured browser resource limits.

Excluded scope

  • Changing aircraft dynamics, control ownership, or authoritative instrument values.
  • Camera selection, pause/resume, completion, retry, and restart behavior.

Verification steps

  • Run applications/web/test/flight/flight-warnings.browser.spec.ts over boundary-value fixtures for every rule and assert normal, warning, and invalid classifications plus deterministic priority ordering.
  • Feed step transitions and sustained bounded heavy-scene traces; assert no stale/contradictory warning, correct sourceStep, configured latency, and configured browser-resource limits.
  • Inject invalid source models, stale attempts/steps, overlapping predicates, and mismatched rule versions; assert INVALID or rejection as specified and no flight-core writes.

Traceability

Dependencies

UI/UX applicability

non_visual

This Task owns technical or behavioral acceptance and does not claim direct visual conformance to the approved UI/UX package.

Acceptance evidence

Verified delivery: application PR #143 reviewed head fbd2702e595b483b8199ab96cba3e7e5a8ae63d2 merged as b1694ae08712d3de56e53bdf273c7973a6f55dca. Versioned pure classification consumes immutable unrounded instrument measurements; deterministically orders INVALID and WARNING findings by severity, priority, and stable rule ID; suppresses contradictory NORMAL publication; rejects invalid, stale-attempt, regressing-step, mismatched-version, over-latency, and over-resource inputs; and renders prioritized control feedback without flight-core writes. Focused warning and instrument suites pass 5/5 each; canonical web suites pass 1,175/1,175; integration passes 137/137; formatting, lint, typecheck, build, production audit, exact-head CI jobs 4107-4113, integration runs 4115-4116, and immutable image publication run 4117 passed. The pre-existing TASK-0057 integration fixture now creates and cleans its own TASK-0020 baseline deterministically. Release completion verified on product 1.0.0.0 at GitOps revision 5d3712d89dfbf7dacd993348e55f497d126c7bf9 with Argo Synced/Healthy, exact image digests, authenticated API/database access, and three-world configured-flight acceptance.

Current evidence boundary

No current implementation, acceptance, release, or deployment evidence is claimed for this planned Task. Any prior implementation may be used only as prototype and discovery evidence.