administrator/rov-autonomy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: flag recording_manager DIR-9/DIR-9a drift as open item

Browse Source
This commit is contained in:
Grant 2026-07-08 18:16:23 +02:00
parent d5c6baa598
commit 9a337d1eb1
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CLAUDE.md
View File

@ -365,6 +365,14 @@ entries; correct forward with a new dated entry if something needs revising.
lake on :9001) launched but had no respawn, so a boot-time race left it permanently lake on :9001) launched but had no respawn, so a boot-time race left it permanently
dead. Added respawn=True to its launch Node. W8 mode indicator built + validated live dead. Added respawn=True to its launch Node. W8 mode indicator built + validated live
(render+data). W1/W8 confirmed GREEN/AUV once bridge up. (render+data). W1/W8 confirmed GREEN/AUV once bridge up.
- 2026-07-08 — FLAGGED (open): recording_manager.py still implements superseded DIR-9
(continuous-from-boot recording), NOT the governing DIR-9a (ARM-bounded black-box:
AUV ARM-start/DISARM-stop, ROV operator manual + arm reminder). Design decision
exists only in handover + CLAUDE.md; code never updated. foxglove_mcap.launch.py
comments also still say DIR-9. Also: argonaut-stack.sh passes record:=${RECORD} but
rov_full.launch.py declares no such arg, so RECORD=false is silently ignored and
bags record regardless. Both deferred to a dedicated DIR-9a recorder-rework session
— do NOT wire RECORD into the current DIR-9 model.
--- ---