Decisions

12 records11 proposed

Architecture decision records

Each ADR is a Markdown file in docs/adr/. Argue in the GitHub thread, then change the file.

ADR	Decision	Pillars	PRD sections	Status	Discuss
0001	Rename PACE to SPACE	SPAC	§3.2 · §3.4	Accepted	threads
0002	Zonal architecture	PC	§6.1 · §3.3 · §9.2 · Eco-5	Proposed	threads
0003	Physical link chosen by criticality, not bandwidth	SAC	§3.3 item 2 · E-02 · H-07	Proposed	threads
0004	Two power domains, logic independent of actuation	PA	§3.3 item 1 · E-01 · H-11 · §14 #4	Proposed	threads
0005	Stop sequence across node and bus bar	PAC	§3.3 item 4 · F-04 · F-10 · E-08	Proposed	threads
0006	Keep a hardwired e-stop loop alongside the network	PC	E-08 · S-02 · §16	Proposed	threads
0007	Wire protocol on 10BASE-T1S segments	SC	§3.3 item 2 · §11.2 · Q3	Proposed	threads
0008	Time-synchronised timestamps in the telemetry schema	SC	§4.2 non-goals · E-03	Proposed	threads
0009	Node role from topology, identity from the MCU	C	§3.3 item 7 · E-04	Proposed	threads
0010	MCU and PHY platform for new nodes	SAC	H-07 · §15.3	Proposed	threads
0011	Single-pair connectors and harness standard	PC	H-13 · §4.2	Proposed	threads
0012	Zone switch silicon, build or buy	C	§3.2 PACE Hub	Proposed	threads

How a decision moves

An ADR starts as proposed with a recommendation and a list of questions. Discussion happens in a GitHub issue titled with the ADR number. When the team agrees, someone edits the file: status becomes accepted (or rejected), the questions get answers, and the PRD sections it names get updated in the same pull request.