Introduce Persistent Data Management

Overview

User capability

Establish PostgreSQL and Prisma for governed persistent records

User

The AeroSim delivery team

What the user can do

Establish PostgreSQL and Prisma for governed persistent records

Why the user benefits

The capability becomes an explicit, testable project boundary.

User need

The delivery team needs the AeroSim solution to establish PostgreSQL and Prisma for governed persistent records.

In scope

Establish PostgreSQL and Prisma for governed persistent records

• StatusProposed
• OwnerAeroSim Scope (proposed; not accepted)
• Parent EpicAEROSIM-EP-1
• Depends onAEROSIM-FT-42

Tasks

AEROSIM-TS-17Planning status: Done

Define the pilot-owned Prisma schema

A minimal Prisma schema defines governed pilot identity linkage and one representative pilot-owned transactional record.

• ComponentPilot Data Store — Prisma schema
• Depends onAEROSIM-TS-16
• RequirementsFR-0050, NFR-0007

AEROSIM-TS-18Planning status: Done

Create reproducible PostgreSQL migrations

All committed Prisma migrations apply successfully to a clean PostgreSQL database and reproduce the expected schema.

• ComponentPilot Data Store — Prisma migrations
• Depends onAEROSIM-TS-17
• RequirementsFR-0050, NFR-0007

AEROSIM-TS-19Planning status: Done

Implement the pilot-scoped Prisma transaction adapter

The API can perform one governed transactional write and read while enforcing authenticated pilot ownership.

• ComponentAPI Service — Prisma data adapter
• Depends onAEROSIM-TS-18
• RequirementsFR-0050, NFR-0007

AEROSIM-TS-20Planning status: Done

Verify transactional persistence and pilot isolation

Real PostgreSQL integration tests prove committed transactions survive reads, failed transactions roll back, duplicate commands do not overwrite data, and one pilot cannot read another pilot’s records.

• ComponentAPI Service and Pilot Data Store — persistence integration tests
• Depends onAEROSIM-TS-19
• RequirementsFR-0050, NFR-0007

Acceptance outcomes

1. 01

   A clean PostgreSQL database can apply all committed Prisma migrations reproducibly.

2. 02

   Integration tests verify one governed transactional write and read without leaking data across pilots.

Functional requirements and measurable criteria

FR-0050

Introduce Persistent Data Management

The system shall establish PostgreSQL and Prisma for governed persistent records.

Acceptance 01

GivenAEROSIM-FT-43 is exercised within its governed scope under supported conditions

Whenthe primary capability path is completed

ThenA clean PostgreSQL database can apply all committed Prisma migrations reproducibly

EvidenceFuture reviewed automated and browser evidence must verify this exact outcome against the current requirement.

Acceptance 02

GivenAEROSIM-FT-43 is exercised within its governed scope under supported conditions

Whenthe continuation or repeat path is completed

ThenIntegration tests verify one governed transactional write and read without leaking data across pilots

EvidenceFuture reviewed automated and browser evidence must verify this exact outcome against the current requirement.

Non-functional requirements

• NFR-0007 — Engineering reproducibility and supply-chain integrity

  Repeated validation from the same immutable inputs produces equivalent artifacts and rejects unlicensed, untraceable, invalid, or over-budget inputs.

Risks

• Risk

  Partial introduction could leave an ungoverned or duplicated technical boundary.

Original source and prototype evidence

• discord: Engineering Features grounded in the selected AeroSim technology stack.
• discord: Engineering Feature decomposition continuation.
• discord: RootAtSkic directed publication of the agreed Scope update.

Prototype and discovery boundary

Existing implementation is discovery evidence only; it establishes no current approval, acceptance, or release state.