Skip to main content

Release 1 Option A decision-ready draft

This package prepares the exact Architecture inputs requested under Giedrius K's Option A planning instruction (Discord message). It does not record Scope approval, Architecture approval, version allocation, implementation approval, Kanban admission, UAT, promotion approval, or release acceptance.

Prepared package​

The machine-readable decision draft contains:

  • exact solution inputs for the 31 unchanged Release 1 Features;
  • a narrowed AEROSIM-FT-33 boundary limited to authenticated free-flight completion/checkpoint and resumable-state persistence;
  • explicit deferral of AEROSIM-FT-44 and FR-0051 from the active flight path, with NFR-0007 reallocation still requiring an Architecture decision;
  • proposed-only AEROSIM-FT-56, FR-0062, NFR-0015, NFR-0016, and TASK-0168–TASK-0170 identities;
  • exact C4 impact, interfaces, flows, dependencies, risks, target-version proposal, implementation conditions, and unresolved conditions for every active Option A Feature.

All existing Features retain exact canonical requirement and Task mappings. Completed Tasks remain implementation evidence only and do not approve their parent Feature or requirement.

Decisions still required​

  1. Scope owner: approve or return the exact Option A Feature disposition.
  2. Architecture owner: after Scope approval, accept the exact requirement disposition, confirm solution completeness, finalize the 1.0.0 allocation, and grant exact-item implementation approval.
  3. Allocator and control owners: resolve the FT-56 policy, RTO/RPO, SLO, capacity, observability, and incident-response inputs before its proposed identities become canonical.
  4. Kanban owner: admit exact implementation-approved Tasks independently.
  5. UAT and Releases: retain candidate, authenticated UAT, promotion authorization, production verification, reconciliation, and human acceptance as later independent gates.

Fail-closed boundary​

  • Flight authority remains browser-local.
  • Web catalogues remain bundled.
  • Keycloak remains the identity boundary.
  • The active browser path does not use Socket.IO, and no production command forwarder is established.
  • NetworkPolicy reachability is not represented as PostgreSQL transport encryption.
  • No rejected 1.0.0.2 / chart 1.0.0+build.3 evidence can be reused.