The first local-preview attempt on port 8093 was discarded because that port was already owned by an unrelated legacy site. A second preview on a confirmed-free port served the actual root-directory source and rendered the intended light editorial atlas composition: the high-contrast virtualmase atlas mark, asymmetric directory metadata rail, original SVG property atlas, clear property-question route cards, explicit operating boundary, and expanded operating footer.
The root directory is a route map, not a content or canonical consolidation layer. Visible copy distinguishes AI Mastery learning, ARM reference, public practice, and participation source. It marks the root directory source as awaiting owner-approved publication and the portal hostname as owner-gated.
| Check | Result |
|---|---|
| Required files, favicon and social fallbacks, manifest, metadata, JSON-LD, footer routes, property boundaries, and prohibited runtime patterns | Passed with node scripts/validate-static.mjs |
| Accessible menu behavior and no visitor storage | Passed with node scripts/test-site-js.mjs |
| 48×48 atlas favicon readability | Checked; the cobalt atlas route and rust reference point remain recognizable without tiny text. |
The source is published to the special virtualmase/virtualmase.github.io user-site repository at commit f8f80ba. GitHub Pages is enabled from main and reports status built at https://virtualmase.github.io/. The public root now renders the directory title, atlas mark, property routes, independent-property boundary, and accessible primary navigation, replacing the prior account-root 404.
The first release carried a stale source-ready status line because the production build completed during the release check. That wording is corrected in the follow-up source update before final release verification. No custom domain, DNS, analytics, Search Console, Vercel, or cross-domain canonical change occurred.
The corrected production page was verified with a cache-bypassing URL after GitHub Pages again reported status built. It now visibly identifies the root directory as published from the source-controlled GitHub Pages route. The account-root 404 recovery and status correction are both complete.
The root directory was checked locally after a two-utility bridge was added. The bridge separates the Action Boundary Brief reader task (before an intended action) from the AI Change Record reader task (after a material change), while the original four-property atlas remains an orientation model rather than a claim that the utilities share one property role. The new routes are visible, task-labelled, and rendered with the existing light editorial atlas system.
The candidate passes the expanded static validator. GitHub Pages completed a successful build from commit 32ff2cc, and the root was verified through a cache-bypassing production request. The live page now contains the two task-labelled utility routes while preserving the separate four-property atlas and its independent authority boundary.
The directory was reviewed locally after the Earthward Foundry route was added as a distinct physical-work field-guide bridge. The new section visibly states that Earthward does not belong to the ARM reference atlas and does not make a public-product, certification, or customer-outcome claim. It links only to the intended independent GitHub Pages project-site URL and preserves the existing atlas as a four-property orientation surface.
The candidate passed node scripts/validate-static.mjs and node scripts/test-site-js.mjs. It remains a local source candidate until the Earthward public property and its reciprocal directory route are released together.
The directory route was released from immutable root source commit a21725c397954f1811f851add7e9fcdd423b5f4e. GitHub Pages again reports built from main and / (root). A cache-bypassing browser review confirmed the visible Earthward / 01 field-guide bridge, its reader task (one facility, one part family, one reviewable evidence loop), and its explicit statement that Earthward is not part of the ARM reference atlas and makes no public-product, certification, or customer-outcome claim.
The published bridge points to the distinct live project site at https://virtualmase.github.io/earthward-foundry/; it does not add a cross-domain canonical, redirect, analytics tag, custom-domain/DNS change, or any claim about the protected pilot services.