Architecture Decision Records¶
Every decision that shapes the stack is recorded here as an ADR (04-engineering-standards.md). States run Proposed → Accepted → Superseded or Deprecated; an accepted ADR changes only by a new ADR superseding it.
| ADR | Title | Status | Date |
|---|---|---|---|
| 0001 | Gazebo Harmonic as the physics and sensor engine | Accepted | 2026-10-14 |
| 0002 | ROS 2 Jazzy is the primary interface; ROS 1 is supported through a bridge | Accepted | 2026-10-14 |
| 0003 | A browser-based cockpit built with Three.js, speaking the Foxglove WebSocket protocol | Accepted | 2026-10-14 |
| 0004 | One container per vehicle, built from the vehicle's own repository | Accepted | 2026-10-14 |
| 0005 | Scenarios are declarative YAML validated by a versioned schema | Accepted | 2026-10-14 |
| 0006 | Simulated time by default, with a real-time-locked mode | Accepted | 2026-10-14 |
| 0007 | Three explicit fidelity tiers: SIL, emulated target, HIL | Accepted | 2026-10-14 |
| 0008 | Single public monorepo on GitHub under the Apache-2.0 licence | Accepted | 2026-10-14 |
| 0009 | Python for orchestration, C++ for Gazebo plugins, TypeScript for the cockpit | Accepted | 2026-10-14 |
New decisions start from 0000-adr-template.md on a branch
adr/<nnnn>-<slug>, reviewed in their own pull request
(05-working-model.md).