Error in user YAML: (<unknown>): did not find expected key while parsing a block mapping at line 1 column 1
---
agent: "alpha_project_root"
component_type: "docs"
status: "alpha"
version: "v2.3"
updated: "2025-09-01"
owner: "Tim"
links:
roadmap: "./ALPHA_Software_Roadmap_v2.3.md"
code: "./alpha_ws/src"
readme: "./README.md"
docs: "./docs"
progress: "./docs/PROGRESS.md"
ui_parameters: "./docs/ui_parameters.md"
dependencies:
internal: ["alpha_utils","alpha_bringup","alpha_lidar_airy","alpha_mapping","alpha_observability","alpha_ui_api"]
external: ["isaac_ros_nvblox","isaac_ros_apriltag","ros2_tracing","linuxptp"]
provides:
topics_pub: []
topics_sub: []
services: []
actions: []
configs:
- "./alpha_configs"
runbooks:
start: |
# See per-component runbooks. This root doc indexes the project.
stop: |
# See per-component runbooks.
healthcheck: |
ros2 topic list
observability:
slo:
- {name: "cmd_latency_p95_ms", target: 60}
- {name: "map_latency_p95_ms", target: 90}
security:
sros2_policies: []
secrets: []
lifecycle:
states: ["INIT","RUNNING","DEGRADED","FAILED","SHUTDOWN"]
transitions: []
failure_modes: []
tests:
acceptance:
- {id: "NET-ADDR", description: "LiDAR IPs reachable; MSOP ports open", pass_criteria: "ping + netcat OK"}
ci_jobs:
- {id: "agents-validate", description: "Validate AGENTS front-matter schema"}
notes: >
Start here. Use docs/AGENTS_INDEX.md to navigate per-component docs.
UI parameter candidates for future UI work are being collected in docs/ui_parameters.md.
## Change & Decision Log
- 2025-08-30: Created trunk baseline and legacy branch/worktree. Scaffolding added for utils, bringup, LiDAR (C++), mapping skeleton, observability, mode manager, orchestrator; CI enabled; bringup launch added.
---
This file anchors the "chain of agents" documentation set. See docs/AGENTS_INDEX.md for the generated index of all components.
- Platform: Leo Rover v1.8 (RPi4/5, Ubuntu 22.04, ROS 2 Humble)
- Plan: add adapter under
alpha_ws/src/alpha_platforms/leo_rover/with launch/config to normalize topics/TF to/alpha/...contracts; wire intoalpha_bringupbehind a flag. - Networking: direct Ethernet Jetson↔RPi, aligned
RMW_IMPLEMENTATIONandROS_DOMAIN_ID; consider DDS discovery server if multicast is unreliable. - Time sync: chrony/PTP (Jetson master, RPi client).
- Tracking: see
docs/PROGRESS.mdand README (CI Policy v1.0). Architect prompt prepared; pending guidance.