00 - Start Here & Current Baseline

Purpose Provide one place to prepare and oversee a home cockpit session from a Samsung tablet or a mobile phone, including the phone used to operate WingRally. Target profiles: DA62 in Microsoft Flight Simulator 2024 and Phenom 300 in X-Plane 12. The integrated XP12/Phenom profile is not yet qualified: its catalogue/mappings are missing or unverified. User-requested outcome Select the simulator/aircraft, start the required supporting tools, then either wait for a route from WingRally or choose an airport and runway or ramp. After loading the flight/route, complete aircraft preparation in cold and dark and show when the cockpit is ready. Evidence and status The current-state records now include cockpit Codex's completed static audit of source, configuration, deployment files and contracts, supplied by the user on 18 September 2026. See knowledge item 117 for the full integration map, versions, ports, commits and limitations. No live simulator run or rebuild was performed in that audit; it has not been independently repeated in this chat. Target behavior and suggested implementation are explicitly labelled; no software implementation has been completed here. Reported normal operation MSFS: open Cockpit Session Launcher before MSFS, press Start session, optionally start RadioBridge, then any selected AI-ATC, WingRally or instructor functions. X-Plane: start the broker on the simulator PC and start X-Plane 12. The existing launcher is still MSFS-oriented. The earlier inventory also listed RadioBridge and AI-ATC, but the subsequent handheld-radio Codex review found only an X-Plane 11 adapter; RadioBridge and its dependent AI-ATC path are not yet qualified for XP12/Phenom. Keep these capabilities unqualified until tested. DA62/MSFS is the first RadioBridge integration candidate. This baseline already replaces many manual starts; evolve it incrementally. Read order for contributors Read this entry, Architecture & Shared Agreements, the component section and the exact assigned task. Inspect current repository code before changing it. Keep completed work, current limitations, proposals and open questions distinct. Documentation All project content is English for potential future publication. Use configurable host/path roles in shared documentation; installation-specific IP addresses, absolute paths and credentials belong in local configuration. Buildory is the shared project record; Git remains authoritative for code and version-specific interface specifications. Existing component projects remain separate and should be referenced rather than duplicated. Next milestone Checkpoint the relevant uncommitted working trees, then add a configuration-driven read-only profile/preflight layer to the existing launcher. Keep the integrated XP12/Phenom profile blocked with a clear explanation until its catalogue and mappings are proven. Do not add automatic bridge startup until usable readiness contracts exist. Task 201 closes only the static inventory; task 212 retains live end-to-end validation.