Interactive explorations of how the Valeron robot system works. Each diagram is a self-contained playground — click around, explore subsystems, and build your mental model.
Living diagrams
Platform
Ecosystem Flow Slicer — 2026-05-11
Flowchart companion to
flows.html: master ecosystem map + 12 per-flow flowcharts (one per FLOWS.md row). Answers "which systems light up for this flow?" vs flows.html's sequence/timing view. Per-diagram Mermaid swap (no CSS-slice highlighting — pivoted from that approach after ELK layout proved uncooperative). Pan/zoom via svg-pan-zoom; copy-pasteable Claude review prompt per flow; keyboard shortcuts (1–9 jump, Esc master, 0 reset zoom). Inline drift notes: Flow 4 (ACL-160 enrollment_complete RSS→RGS), Flow 7 (no automated cloud→robot delivery; target ACL-202), Flow 10 (build-time, not runtime).
Valeron Ecosystem — 2026-04-28
ELK-laid-out Mermaid map of the full Valeron ecosystem reflecting current state as of 2026-04-28. Feature #7 (Gateway Extraction) Phase 6 Track A landed 2026-04-21; Nav Jetson hostname is now
v0-ace00-robot post-2026-04-22 reflash; shared schemas live as @valeron/gateway-contracts v0.2.0 inside robot-gateway-service/packages/contracts/ (the earlier "shared-gateway-protocols" name never became a real package). Janice is preserved as the persona; robot-supervisor-service is the canonical service identity. Pan/zoom, download-as-.mmd, contract catalog, and repo cards below the map.
Valeron Ecosystem — Post-Feature-#7 View (archived)
ELK-laid-out Mermaid map of the post-Feature-#7 projected shape, written 2026-04-19 before Phase 6 cutover landed. Snapshot pre-dates the 2026-04-22 Nav Jetson reflash + rename, so it carries
v0-ace00 hostnames and "Robot Jetson" subgraph labels. Also references shared-gateway-protocols which was later collapsed into the @valeron/gateway-contracts in-repo package. Superseded by 2026-04-28 view. Preserved for historical context.
Capture Architecture Playground
Interactive four-layer view of the capture pipeline: Phone → Ace Cloud → Robot Jetson (Janice) → Capture Jetson (robot-capture-service + Shot Tracker Pipeline). Six flow presets (Full System, Pairing, Enrollment, Shot Capture, Video Delivery, Session Upload) highlight the relevant edges and drive a numbered step shelf on the right. Color-coded by protocol (HTTP / WebSocket / Unix Socket / JWT / DB) and line style (solid / dashed / dotted). Click-to-comment generates a copyable prompt.
System Architecture
Layered view of the full Valeron platform — client interfaces (web-platform-app, mobile-golfer-app, mobile-field-app), cloud layer (Supabase with 8 edge functions, PostgreSQL+RLS, Auth+Storage), on-course hardware (Robot Jetson + Capture Jetson), and tools (Ferry, KYT, Jamal). Includes role hierarchy, connectivity model, and planned vs built status for all components.
Platform Ecosystem View (archived)
Comprehensive platform snapshot with eight tabs: North Star, end-to-end data flow (Mermaid), component status, program progress, schema map, role hierarchy, gotcha log, and the ACL-* backlog. Reflects the two-board architecture (Robot Jetson + Capture Jetson), ADR-014 canonical pairing, ADR-015 capture API separation, nine deployed edge functions, and Platform Infrastructure Readiness 59/59 complete. Superseded by the 2026-04-19 post-F#7 view.
Platform Ecosystem View (archived)
Original ecosystem snapshot from 2026-04-10. Superseded by 2026-04-12 version. Preserved for historical reference — captures the state at ACE-13 demo loop closure before the Platform Readiness consolidation.
Robot
Capture Jetson Architecture
Current vs proposed architecture of the Capture Jetson (golfer/dora pipeline). Shows why one monolithic service makes independent testing impossible, and how splitting into storage / hardware+pipeline / control-plane boundaries restores it. Includes live failure-mode presets (X5 unplugged, dora crash) so you can see the cascade.
ACE Binary Architecture
Full architecture of the ace C++ binary — sensor pipeline, shared memory, HAL drivers, nav2 modules, and HTTP debug API. How data flows from GPS/IMU to motor commands.
GNSS Navigator Decision Flow
Step-by-step decision tree of the GNSS navigation algorithm — waypoint selection, heading calculations, turn detection, speed control, and terminal rotation. Maps directly to nav2.yaml parameters.
Janice Process Flow
Full lifecycle of a Janice demo — four swim lanes (You, Janice event handlers, the always-running tick loop, Robot). Shows arm/disarm safety gate, empty boot, upload/stage/go/execute/complete phases. Click arrows for payload examples.
Janice Architecture Explorer
Component-level architecture of Janice Tooner — signal ingest, decision engine, command exec, server/UI, and configuration layers. Toggle layers and connection types, click components for feedback.
Jimmy's Janice Jumpstart Journal
Architecture briefing that takes an honest look at what Janice does today (12 responsibilities across 3 audiences with CPU estimates and breakage analysis), how it accreted there, and the proposed split into a shrinking Python Sequencer and a durable TypeScript
ace_gateway_api that mirrors robot-capture-service. Covers language policy alignment (ADR-017/018/021), UI offloading (kill PiP, rename Observer → Sequencer UI, move Field Control to direct nav-stack ws), and an interactive scenario builder with live CPU/LOC/service-count impact. Three concrete collaboration asks at the end.