Documentation
The full map.
Arc Router's documentation lives beside the code it describes, so it moves when the code moves. Every link opens the current file on GitHub.
Start here
Four documents that between them explain what the project is, how it decides, and how it is laid out.
The routing decision
The heart of it: who votes, how the votes are weighted, how the router learns from what comes back, and how it proves it improved.
Architecture and transport
How requests reach the router, how they are translated, and where execution is isolated.
Cost and telemetry
Counting tokens honestly, reconciling them with what providers report, and logging the result.
Security
Provider credentials sit in this process. These documents cover how they are held and what is hardened around them.
The GUI
Design language, motion, and the specification behind each screen of the desktop application. The GUI runs its own design system — near-black and Dark Green — deliberately distinct from this site's.
Benchmark data
What syncs into coderouterbench.db, what it verifies, and what has not been restored yet.
Architecture decisions
Numbered records of decisions that were hard enough to be worth writing down, with the reasoning that produced them.