The specification layer for robot hardware

Architon is a machine-checkable specification for your robot's electrical architecture. Instead of scattered spreadsheets and implicit assumptions, you define the stack as structured YAML and let the CLI enforce compatibility before you ever buy a part.

Machine-checkable specs Describe batteries, rails, MCUs, drivers, sensors and motors in a single structured spec that both humans and tools can reason about.

Single source of truth Use the same spec as the contract for design reviews, BOM discussions and integration work instead of diverging spreadsheets and notes.

CI and automation ready Emit INFO, WARN and ERROR findings with non-zero exit codes so hardware checks become part of your merge gates and release process.

Open Architon CLI on GitHub View README

Early alpha. Interfaces and outputs will change. Feedback welcome.

Where it fits in your flow

Before you draw schematics, capture the electrical architecture as YAML in version control.
Run architon check locally and in CI on every change to enforce voltage, current and logic-level assumptions.
Only when checks pass, freeze the spec and move on to CAD, firmware and integration work.

Roadmap preview

KiCad boilerplates and templates derived from specs so schematic structure mirrors hardware intent.
ROS2 workspace scaffolding tied to the same spec so topics and nodes stay consistent across the stack.
Normalized part data model so future adapters and tools reason over a consistent spec, not raw distributor feeds.
Constraint-aware assistive tooling for part selection and change impact analysis on top of deterministic checks.

Example check output

$ architon check examples/amr.yaml
! Voltage mismatch: 24V bus exceeds driver limit by 3.2V
! Logic level warning: IMU sensor requires 3.3V level shifting
! Current warning: Motor driver L298N not recommended for 12V at 1.8A continuous