Architecture decision records
Every significant decision is written down with its context, the alternatives considered and its consequences. Records are append-only: a decision that changes gets a new record that supersedes the old one.
| # | Decision | Status |
|---|---|---|
| 0001 | Multi-repository topology, one package per repository | Accepted |
| 0002 | TypeScript engines shipped as source packages; Rust/WASM where it pays off | Accepted |
| 0003 | .falcad: canonical JSON, integer nanometres, UUID v4 identity |
Accepted |
| 0004 | Validated, serialized transactions instead of last-writer-wins for design data | Accepted |
| 0005 | MongoDB for the hosted service | Accepted |
| 0006 | One renderer for web and desktop; Electron security model | Accepted |
| 0007 | In-house validated MNA solver plus an ngspice adapter | Accepted |
| 0008 | Yosys and nextpnr through WebAssembly (YoWASP) | Accepted |
| 0009 | Identifiers: GUID v4 from the OS CSPRNG, never sequential | Accepted |
| 0010 | Small static documentation generator instead of VitePress 1.x | Accepted |