Maintain a Personal Flight Logbook

Overview

User capability

Store and retrieve the authenticated pilot’s flight summaries

User

An AeroSim player

What the user can do

Store and retrieve the authenticated pilot’s flight summaries

Why the user benefits

The player receives one coherent, observable capability.

User need

The player needs AeroSim to store and retrieve the authenticated pilot’s flight summaries.

In scope

Store and retrieve the authenticated pilot’s flight summaries

• StatusProposed
• OwnerAeroSim Scope (proposed; not accepted)
• Parent EpicAEROSIM-EP-6
• Depends onAEROSIM-FT-24, AEROSIM-FT-30, AEROSIM-FT-43

Tasks

No Architecture-owned implementation task is currently defined for this Feature.

Acceptance outcomes

1. 01

   A governed completed flight creates one logbook entry for the authenticated pilot.

2. 02

   The same pilot can retrieve that entry after a later SSO session.

Functional requirements and measurable criteria

FR-0034

Maintain a Personal Flight Logbook

The system shall store and retrieve the authenticated pilot’s flight summaries.

Acceptance 01

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

Whenthe primary capability path is completed

ThenA governed completed flight creates one logbook entry for the authenticated pilot

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

Acceptance 02

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

Whenthe continuation or repeat path is completed

ThenThe same pilot can retrieve that entry after a later SSO session

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

Non-functional requirements

• NFR-0012 — Flight-result integrity and explainability

  Every displayed result identifies its session and governed source; unavailable values are explicit; recommendations identify their supporting result; cross-pilot result access is denied.

Risks

• Risk

  Representative browser or input configurations may expose an unmet outcome.

Original source and prototype evidence

• discord: Agreed eight-Epic portfolio and Feature decomposition.
• discord: Agreed eight-Epic portfolio and 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.