Architecture decision records

Each record states the decision and the reasoning behind it, so a reviewer can disagree with the reasoning rather than guess at it. These are the decisions the code embodies today; several are cited by number from the source.

#	Decision	Status
0001	USDC on Stellar is the hub’s unit of account	Accepted
0002	The Stellar hub is enforced by the route planner	Accepted
0003	The 32-byte reference rides MEMO_HASH; reconciliation is a join, not an index	Accepted
0004	A compensating saga rather than two-phase commit	Accepted
0005	The confidential lane waits for Stellar confidential tokens	Accepted
0006	Anchors are the fiat spokes, reached over the SEPs	Accepted
0007	The issuer is part of the asset’s identity; unverified issuers stay unset	Accepted
0008	Fees, reserves and funding are booked from what the chain shows	Accepted
0009	Customers hold the keys; Corridor signs through their KMS or MPC	Accepted
0010	USDC, USDT, PYUSD, MGUSD and EURC are each first-class	Accepted
0011	A customer starts read-only; moving money is the second step	Accepted
0012	The ledger keeps Stellar’s seven decimal places	Accepted
0013	Ramp and the Hub are two front doors on one core	Accepted
0014	Receive CCTP, do not burn	Accepted

Corridor’s earlier prototype settled on Tempo and reached its payout rails through bespoke provider APIs. Numbers are kept where the decision survived the move to Stellar (0002, 0004, 0008, 0009, 0010, 0011); 0001, 0003 and 0005 are the same question answered differently on Stellar, and 0006, 0007 and 0012 are decisions the hub itself forced.