Skip to main content

AEROSIM-TS-68

Project task

Verify canonical progress durability and pilot isolation

Reviewed evidence demonstrates pilot-owned persistence and later retrieval of identical canonical progress, including failure integrity, version validation, and denial of cross-pilot access.

AEROSIM-TS-68Canonical ID TASK-0068
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Pilot Data Store, API Service, and Web Application — progress test suites
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Add migration, service, API, integration, and browser tests for flight and lesson checkpoints, later-session retrieval, deterministic latest-state selection, duplicate retry idempotency, stale or malformed versions, interrupted transactions, logout cleanup, two-pilot isolation, and persisted-data integrity. Concrete artifacts are prisma/schema.prisma and tests/integration/progress-isolation.test.ts; ownership is limited to the listed artifacts and their focused verification.

Implementation contract

Implementation artifacts

  • prisma/schema.prisma
  • prisma/migrations/verify-canonical-progress-durability-and-pilot-isolati/migration.sql
  • tests/integration/progress-isolation.test.ts

Inputs

  • Flight and lesson checkpoint fixtures with supported, stale, malformed, and duplicate versions
  • Two authenticated pilot fixtures and later-session retrieval sequences
  • Transaction interruption and persisted-record integrity probes

Outputs

  • Reviewed evidence demonstrates pilot-owned persistence and later retrieval of identical canonical progress, including failure integrity, version validation, and denial of cross-pilot access.

Failure boundaries

  • Fail if the retrieved canonical state differs from the final committed checkpoint or duplicate retries alter deterministic latest-state selection
  • Fail if interrupted writes leave partial data, logout retains pilot progress in active state, or either pilot can read or change the other’s progress

Excluded scope

  • Long-duration telemetry retention and replay fidelity
  • Release verification for activity types outside the governed progress contract

Verification steps

  • Run tests/integration/progress-isolation.test.ts against the exact implementation revision and retain the complete passing result.
  • Exercise the positive contract with flight and lesson checkpoint fixtures with supported, stale, malformed, and duplicate versions, then assert: Reviewed evidence demonstrates pilot-owned persistence and later retrieval of identical canonical progress, including failure integrity, version validation, and denial of cross-pilot access.
  • Exercise every negative boundary: Fail if the retrieved canonical state differs from the final committed checkpoint or duplicate retries alter deterministic latest-state selection; Fail if interrupted writes leave partial data, logout retains pilot progress in active state, or either pilot can read or change the other’s progress

Traceability

Requirements

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 #122 merged reviewed head 94a07d864f84bad4f6a82f3f8dadfa1723303027 as 9fc1b286c7c220a7fdb696fd20905eecb2e0b00a; six focused real-PostgreSQL tests prove flight and lesson checkpoint durability, exact later-session retrieval, canonical latest-state ordering, duplicate retry idempotency, stale/malformed/version rejection, interrupted-transaction rollback, logout cleanup, and two-pilot isolation; full local validation, 120 world-interaction runs, production audit, exact-head CI run 4201, integration/publication run 4202, and integration validation run 4203 passed. 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.