Deployed
Site Specs.

Register follows the reader’s obligation, not the page’s location. A community site is Commons at its top level and Bedrock inside officials/. Both live under the same domain; the directory does not decide it.

Commons — the reader is a resident. They carry no duty, they are deciding whether to support, and they can walk away. The six-page community package.

Bedrock — the reader must authorize something and then defend it on the public record: council members, city managers, finance directors. This covers officials/ on every community site, and the fiscal and technical studies that sit outside the package — deployment-study, eir, and anything else built to be cited.

The evidence is already in the pages. The Anchorage officials briefing is headed “How this hits Anchorage’s balance sheet and income” and closes on “Authorize a Deployment Study.” The Economic Impact Report carries a Basis of Presentation section and an ILLUSTRATIVE marker on a 30-year figure. Those are accounting conventions, written for a reader who will be asked where the number came from.

Being a public record is the argument for Bedrock, not against it. The instinct runs the other way — these pages are shown in open council meetings, so they feel community-facing. But a public meeting does not change what the reader is doing: voting to commit public capital. Bedrock’s discipline — formal register, numbers that invite verification, the forward-looking disclaimer — is what protects an official when the document is scrutinised afterwards. Commons warmth applied to a fee structure and a liability transfer reads as marketing to a body with procurement obligations.

Migration cost is near zero. These pages already use blue and emerald, which are Bedrock’s own accents (--bedrock-blue-* #007FFF, --bedrock-data-dark #34D399). Routing them to Commons would be the disruptive option: Warm Paper #FAF7F2 is Commons-only under S-08, and a balance-sheet briefing does not belong on it.