Decisions

Short records for the calls this rewrite makes. Each one is context, decision, consequences — what was true, what was chosen, and what the choice costs. They are written from the artifacts: the lane documents, the harness, the code, and issue #5, which is the source of truth. Where a record and the issue disagree, the issue wins.

These are records, not policy. A decision that changes gets a new record that supersedes the old one; the old one stays, because the reasoning is the point. Issue #5 §8's comment policy says the rest: a comment states a constraint the code cannot show, and "how we got here" prose belongs here or nowhere.

The calls issue #5 makes (§8)

	Decision
1	HTMX 4 owns the discrete state
2	allons is removed, and nothing replaces it
3	Cross-source merge moves from generate to enrich
4	The interchange document is Atlas's own schema
5	Maturity is per-feature, additive, unbounded and monotone-gated
6	The seam is driven by an inert scene description
7	One pure handler, everything OS-shaped behind hostenv
8	A stamp is a rebuild-cost promise, not a content promise

The calls execution made

Decisions taken while building the lanes, which issue #5 §10 does not record.

	Decision
9	generate ⊕ enrich is joined by an adapter in the CLI
10	An enriched build wins the fold by packing two policy revisions
11	One leveled event stream, and a lane of its own for it
12	The registry is scanned at launch and on import — never watched
13	/assets and /static are two different mounts
14	A boundary crossing is annotated in place, with a reason
15	A cell system is handed a Ground, not an application
16	A capture a reader cannot answer for is passed over, not refused
17	The desktop host follows the application's redirects
19	The desktop ships with an included Earth volume