Crimson Hexagonal Archive  /  navigation

The navigation architecture

The Crimson Hexagonal Archive uses four non-collapsible navigation layers. The Registry anchors records and provenance. The Central Navigation Map routes relations among them. The Fractal Navigation Map resolves depth, operator, scent, companion object and next path. The Space Ark governs runtime traversal. This site renders those layers as a public operating surface — it is where the navigation architecture becomes traversable, and it is not itself the navigation authority.

The order of operations

REGISTRY  stores. Does not route.
CENTRAL MAP  routes. Does not execute.
FRACTAL MAP  resolves entry depth and next traversal. Does not govern.
SPACE ARK  executes and governs. Does not anchor.

Each depends on the others and none replaces another. The Hexagon Interface Constitution holds that this surface is a renderer and operator over H_core, that topology organises but does not replace the texts, and that no map, dashboard or mode becomes the whole Archive.

Two temporal strata

Every node below is shown twice. The current projection is generated, dated and disposable. The historical specification is a ratified document and is not edited.

The four principal navigation documents describe the state of 16 March 2026 — 387 DOI-anchored records, 2,851 typed edges. The archive now holds 1,488 deposits. Those documents are not stale; they are evidence. Rewriting them to contain the present would destroy the record of what the architecture was when it was ratified, and would make the DOI-era loss undocumentable. So their functions are re-executed here instead, and nothing generated is called a new version.

Generated 2026-08-17 from hexagon_canonical.json · rooms · alexanarch · ∮ = 1