ATL-E · the map version and recent changes
A focused company on the Atlas map shows its map version, its latest map changes, and which version a rehearsal would produce. Nothing is saved.
1 Oct 2026 · branch ui-atl-e-part2-version-rail · captured against propflow-stage · at 13d4b1c1d36+local
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · The test company, focused on the map: the version pill and the rail
Opening the test company (found at runtime by its name) and switching to the map shows map v<N> beside the company's name and its latest map changes under it, newest first.
Why this is right
One lazy read through ?type=mapChanges on the Atlas detail route, for the focused company only, through the same projection GET /api/map-changes uses. The rail is read-only; its heading links to the company's Recent map changes page, where Undo lives behind its own gate.
Asserted in the captured DOM — Recent changes · map v · v1 —
2 · A rehearsal on the test building: the version it would produce
Clicking #3 on a test building shows the rehearsal, and the panel now says map vN → vN+1 · not saved.
Asserted in the captured DOM — What-if: a rehearsal, nothing is written · a design-model count · · not saved
What the two critique rounds changed
Round 1: the heading "Recent changes" sat beside a "Recent map changes" link, two near-twin labels, and a change no person made read "(—, Sep 25 …)". The heading is now the link, and a script's change shows its time alone. Round 2 read clean. The rows' text is each writer's own one-line summary.