WP9a: flight-software groundwork (software-only; TRL unchanged; WP9 PIL stays reserved)

CMakeLists.txt

@@ -159,6 +159,16 @@ add_executable(test_flux tests/test_flux.cpp)
 target_link_libraries(test_flux PRIVATE adsc_core adsc_flags)
 add_test(NAME flux COMMAND test_flux)
 
+# WP9a flight-software groundwork probe (software-only; TRL stays 4
+# everywhere, WP9 PIL itself stays reserved -- docs/wp9_pil_plan.md):
+# allocation-count determinism + a generous ceiling, bit-identical final
+# state across two runs, and a CI-hardware-baseline wall-time sanity bound
+# for the combined control+estimation step. Everything prints to stdout only
+# (regenerate: ctest -R wp9_flightlike); no generated/ artifact is committed.
+add_executable(test_wp9_flightlike tests/test_wp9_flightlike.cpp)
+target_link_libraries(test_wp9_flightlike PRIVATE adsc_core adsc_flags)
+add_test(NAME wp9_flightlike COMMAND test_wp9_flightlike)
+
 # WP7a Visualization Pack test: Python 3 stdlib-only generator (spec v4.2 R9
 # tooling exception). Regenerates the SVGs from the committed CSVs and checks
 # well-formedness, caption provenance, no timestamps/stub markers, and byte

README.md

@@ -116,8 +116,10 @@ adsc-specification-v5.md   the binding spec (rules R1-R16, decisions D1-D13)
 
 WP1–WP8 ✅ · WP10 forensics ✅ · WP11 safety hardening ✅ · WP12 fidelity
 ladder ✅ · WP13 kit trade + EDT ✅ · WP14 cost ranges + FoM ✅ · **WP15
-proposal package ✅ (this release)** · WP9 processor-in-the-loop — **reserved,
-not started, the only path above TRL 4**. Detail:
+proposal package ✅ (this release)** · WP9a flight-software groundwork
+(software-only, TRL unchanged) ✅ · WP9 processor-in-the-loop — **reserved,
+not started, the only path above TRL 4** (WP9's pre-registered plan:
+[docs/wp9_pil_plan.md](docs/wp9_pil_plan.md)). Detail:
 [docs/roadmap.md](docs/roadmap.md).
 
 ## Limitations

docs/roadmap.md

@@ -58,6 +58,15 @@ deliverables).
 - **WP9 — Processor-in-the-loop / flight-software track** — **reserved, not
   started.** The only path above element TRL 4; see spec §9 and the
   discussion below.
+- **WP9a — Flight-software groundwork (software-only)** — done. Workstation-
+  only groundwork for the reserved WP9 track: a pre-registered plan freezing
+  WP9's future pass/fail criteria before any hardware exists, plus a
+  workstation probe (`tests/test_wp9_flightlike.cpp`, `ctest -R
+  wp9_flightlike`) checking allocation-count determinism against a generous
+  ceiling, bit-identical final state across two runs, and a CI-hardware
+  wall-time baseline print. Like WP10–WP15, this widens what preparing for
+  WP9 requires; it does not raise the TRL, and WP9 PIL itself is unaffected —
+  still reserved, not started. Detail: [wp9_pil_plan.md](wp9_pil_plan.md).
 - **WP10 — Phase 0: adoption, citations, forensics** — done. Spec v5 adopted;
   citation-fill; keep-out-violation forensics
   (`generated/wp10_violation_forensics.md`, the legacy-law archive superseded
@@ -121,6 +130,9 @@ Work package by work package, why the TRL does not move:
   economic argument — neither is a GNC maturity change.
 - **WP15** (this package) is a packaging/communication exercise — it changes
   how the evidence is presented, not what TRL the evidence supports.
+- **WP9a** (flight-software groundwork) is software-only preparation for the
+  reserved WP9 track — like WP10-WP15, it widens what a future PIL campaign
+  would need; it does not raise the TRL, and it is not WP9 itself.
 
 Reaching TRL 5 for the element requires real-time processor-in-the-loop
 execution on representative hardware — the WP9 track, reserved, not started,