After repository inventory, add or merge instructions into the relevant AGENTS.md files while respecting existing repository guidance. Include the Cockpit Platform project identifier, overview/architecture/component read order, task scope and cross-repository contract coordination. Include concise authorized result reporting with commit/version and validation evidence. Acceptance: each affected Codex session can locate the same project context; instructions do not claim automatic Buildory access, repository locking or blanket authorization for unrelated changes. Do not duplicate evolving technical specifications across repositories.
.png)
01 - Architecture & Shared Agreements
Component responsibilities, integration contracts, simulator ownership and coordination across repositories. Separate verified implementation from proposals.
Knowledge (1)Tasks (1)
TASK LIST
1 task
Knowledge
1 item📝
Component boundaries and shared Codex working agreement
Proposed direction Evolve the existing Cockpit Session Launcher into Cockpit Manager. Provide one user-facing entry point while allowing radio, broker, camera and optional AI functions to retain suitable process boundaries. Do not start by rewriting all tools or forcing all runtime data through a new central transport. Reported boundaries Broker handles physical nodes and simulator translation. Session Launcher already embeds Sim Agent and manages MSFS preparation and FreeTrack. RadioBridge owns radio state, PTT, audio routing, radio protocol, simulator-radio adapter, T-Dongle gateway and device logic. Cockpit Manager only manages lifecycle and displays RadioBridge-reported readiness; it must not duplicate these responsibilities. Android, handheld and future fixed cockpit radios are peer Wi-Fi audio clients behind the T-Dongle and belong under RadioBridge, not Broker/nodes. WingRally Bridge handles flight delivery. SimBridge supports the AI Flight Instructor experiment. Cockpit Control is optional configuration/diagnostics, not a runtime prerequisite. Shared implementation rules to carry into repository AGENTS.md 1. Read project overview, architecture notes, affected component sections and assigned task before implementation. 2. Inspect current code and record affected repositories, intended scope and dependencies. 3. Make shared communication changes explicit: sender, receiver, schema/version, units and compatibility behavior. Do not silently change another component's contract. 4. Coordinate task ownership when multiple Codex sessions work concurrently. Buildory notes alone do not provide repository locking or automatic access. 5. When return of results to Buildory is authorized, record a concise result, relevant commit/version, tests and outstanding issues. Never mark proposals as implemented. 6. Keep credentials and machine-specific deployment configuration out of public project documentation. Proposals requiring code investigation Assess duplicated simulator connections, telemetry, reconnect logic, configuration and logging before choosing shared libraries or a single simulator gateway. Preserve simulator-neutral node behavior. Define ownership for conflicting commands, especially camera movement and loading a flight. Do not replay stale load-flight commands after reconnect. These are project coordination instructions, not evidence that AGENTS.md files or runtime contracts have already been changed. Handheld-radio review clarification (18 September 2026) The reported X-Plane 11 adapter does not establish XP12/Phenom support. Qualify that combination separately. Radio readiness requires simulator, gateway, required client and usable audio/PTT signals supplied by RadioBridge, not just process liveness. Multi-speaker unicast synchronization remains a RadioBridge concern.