Canonical Releases
This release history records changes to the AI Civilization Map’s architecture, Method, structural semantics, provenance model, and governance rules. Routine Branch growth, article publication, Structural Node Changes, and non-structural Knowledge Changes remain in the monthly reviews and do not automatically create a new Map version.
Click a version to expand or collapse it. Only the latest canonical release is opened by default.
Layer Semantics, Branch Hierarchy, and Node-Governance Clarification
›
Clarified that Layer numbers are canonical identifiers rather than a causal, temporal, or vertical sequence; defined Layers 1–8 as interdependent structural domains and Layer 9 as the human social system of consequence, participation, and feedback; and formalized the Layer → Branch Path → Node hierarchy, terminal-Branch placement, publication-to-Node admission rule, and Branch Structure Change record.
Architecture impact: No change to the names, order, or number of the nine canonical Layers. The AI Civilization Map Method remains v1.0.
Interpretive note: v1.2 defines the current evidence-grounded architecture; it does not establish nine Layers as a permanent ceiling.
Method, Provenance, Governance, and Versioning Release
›
Formally named the AI Civilization Map Method; established persistent identifiers for Hi K Robot, the Map, and the Method; clarified the canonical roles of the Map, governance standards, and Activity Log; and introduced public release rules.
Canonical nine-Layer terminology in effect by v1.1:
- Layer 1: Energy & Physical Infrastructure — Foundation
- Layer 2: Semiconductors, Compute & Packaging — Machine Substrate
- Layer 3: Fiber, Networks & Distributed Intelligence — Coordination Fabric
- Layer 4: Models, Agents & Machine Cognition — Cognitive Layer
- Layer 5: Robotics, Automation & Physical Intelligence — Embodied Systems
- Layer 6: Space & Orbital Infrastructure — Orbital Frontier
- Layer 7: Capital, Institutions & Operating Layers — Institutional Systems
- Layer 8: Geopolitics, Sovereignty & Constraints — Boundary Conditions
- Layer 9: Labor, Income & Human Participation — Social Layer
Terminology provenance: Compared with the first preserved v1.0 public-era snapshot, the outer conceptual label for Layer 6 had changed from Expanded Frontier to Orbital Frontier, and Layer 7 from Decision Systems to Institutional Systems. The underlying formal Layer names did not change.
Architecture impact: No change to the nine canonical Layers. These terminology refinements did not add, remove, merge, split, or materially redefine a Layer; v1.1 formalized how the existing Map is applied, identified, governed, and revised.
Initial Canonical Nine-Layer Architecture
›
Established K Robot Lab as the public entry point for the AI Civilization Map and defined the initial canonical nine-layer architecture used to connect infrastructure, technology, industry, institutions, capital, geopolitics, and society.
Historical role: This release is the provenance anchor for the original public map architecture. Later releases extend or revise it without rewriting this date.
Version policy: The Layer count is evidence-derived rather than permanently fixed at nine. Major versions are reserved for adding, removing, merging, splitting, or materially redefining civilization-scale structural Layers. A future architecture could therefore contain six structural Layers plus one human social Layer, or ten or fifteen structural Layers plus one human social Layer, if reality supports that configuration. The human social system remains conceptually distinct even if its numeric Layer identifier changes. Routine Branch growth, monthly Structural Node Changes, and non-structural Knowledge Changes remain within v1.2.
Activity Log and AI Civilization Map Method
The map is never finished. Reality is its editor.
The AI Civilization Map Method is architecture-adaptive: it governs how events enter analysis across the Map’s current canonical Layer architecture rather than imposing a permanent Layer count. Under v1.2 that means the current nine-Layer system. Publication does not automatically create a Node; a Node is added only when it clarifies a durable structural relationship, is supported by measurable technologies, infrastructure, institutions, companies, industrial capacity, policy, costs, or real-world output, and can be assigned to a canonical Primary Map Layer and terminal Primary Map Branch. A Node may be removed, archived, promoted, demoted, or moved when new evidence changes its role in the system. Its underlying knowledge may also be materially Updated without changing the Node’s canonical structural position or topology.
Structural Node Changes
Monthly reviews retain six canonical Structural Node Change classifications. Confirmed zero counts are recorded explicitly rather than omitted:
Added
Removed
Archived
Promoted
Demoted
Moved
AddedA new Node enters the active Map after sufficient evidence establishes a durable structural relationship, a canonical Primary Map Layer, and a terminal Primary Map Branch.
RemovedA Node leaves the active Map because the original structural judgment is no longer valid, useful, distinct, or sufficiently supported. Its prior admission and removal reason remain preserved in the Activity Log.
ArchivedA Node leaves the active Map but retains historical structural value. Its Node identity and prior Branch Path remain preserved as part of the Map’s development history.
PromotedAn existing Node gains greater systemic importance, becomes a stronger bottleneck or control point, or expands from a supporting role into a more central position.
DemotedAn existing Node remains valid but moves to a less central position because its scarcity, influence, explanatory value, or systemic importance has declined.
MovedAn existing Node is reassigned to another Layer or Branch because new evidence provides a more accurate canonical position; movement does not by itself imply promotion or demotion.
Knowledge Change
Knowledge Change is recorded separately from Structural Node Changes because it describes a material change in what an existing active Node knows or represents without changing where that Node sits in the canonical Map.
Updated
UpdatedAn existing active Node remains in the same canonical Primary Map Layer and terminal Primary Map Branch and does not qualify as Added, Removed, Archived, Promoted, Demoted, or Moved, but its underlying evidence, scope, definition, or analytical content has been materially revised. Editorial, formatting, SEO, metadata, source-formatting, or other cosmetic changes alone do not qualify.
Canonical Node Content Rule: An active Node article represents the latest internally consistent structural interpretation supported by current evidence. A qualifying update should be integrated into the article’s existing reasoning, definitions, and conclusions so the page remains a coherent current-state representation; superseded claims should be revised or removed rather than left as competing historical patches.
Historical Change Record Rule: The Node article preserves the current canonical understanding; this Activity Log preserves the material revision history. Each Updated record should identify the update date, what materially changed, why it changed, the evidence or scope added or revised, and whether structural status, canonical placement, or Map topology changed. Article metadata may show the current Last Updated date, while the Activity Log preserves the sequence of material updates.
Classification boundary: Updated is not a seventh Structural Node Change classification and does not by itself alter Layer, Branch, active-Node, or reserved-Branch topology counts. If new evidence changes a Node’s structural status, canonical placement, or systemic importance enough to qualify as a Structural Node Change, that structural classification takes precedence and the event is not double-counted as Updated.
Archived Reference
Archived Reference is neither a Structural Node Change nor a Knowledge Change classification. It identifies research, a method application, or historical interpretive material preserved for reference even though it is not and need not have been an active Map Node. An Archived Node, by contrast, is a formerly active Node preserved for historical structural value.
Monthly Review Provenance
Each canonical monthly review uses a persistent MR-YYYY-MM identifier and an exact Review Cutoff date. It records all six Structural Node Change counts; beginning with MR-2026-09, it also records the separate Updated Knowledge Change count, including an explicit zero state when none occurred. Archived References remain separate. Canonical Branch changes include confirmed zero change, and the topology summary covers Layers, Canonical Branches, active Nodes, and Reserved Empty Branches. Observational Branches are recorded separately as an observation-state count and are excluded from canonical topology totals until formally admitted.
Effective review rule: Updated was introduced on September 7, 2026 and is first applied in MR-2026-09. MR-2026-07 and MR-2026-08 retain the governance schema in effect when those reviews were recorded and are not retroactively normalized.
Baseline rule: A Node already present in the reference topology at the beginning of a review interval is part of the baseline state and must not be counted as Added in that review. The first canonical review, MR-2026-07, therefore uses an Initial Baseline Reconciliation against the t0 topology fixed July 17, 2026; the v1.0 public release date remains July 15, 2026. Only changes occurring after t0 are counted as July deltas.
Branch States and Observation Governance
Canonical BranchA durable, repeatable structural category admitted to canonical topology and included in the Canonical Branch count.
Reserved Empty BranchA Canonical Branch whose structural category is established but currently has zero qualifying active Nodes. It remains included in the Canonical Branch count.
Observational BranchA provisional event-observation path outside canonical topology. It tracks a possible structural category while evidence develops and does not increase the Canonical Branch count.
Opened / ClosedObservation-state actions for an Observational Branch. Opened begins provisional tracking; Closed ends tracking when the pattern does not persist. Neither action changes canonical topology.
Canonicalization rule: An Observational Branch becomes a canonical Branch only when subsequent real-world evidence demonstrates a durable, repeatable structural function. At that point it is recorded as Branch Added. If an observational Branch is closed before canonicalization, it is not recorded as Branch Removed because it was never part of canonical topology. Node admission remains a separate evidence threshold.
Branch Structure Changes
Canonical Branch changes are recorded separately from Node status because Branches are expandable structural paths rather than active units of evidence. Material canonical changes may be classified as Branch Added, Branch Removed, Branch Deepened, Branch Split, Branch Merged, Branch Renamed, or Branch Reorganized. Opening or closing an Observational Branch is recorded separately under Branch Observation State and does not change canonical Branch totals. When no canonical change occurs, the review records No Change, the maintained Canonical Branch count, and explicit +0 / −0 change so structural continuity is machine-readable rather than inferred from silence.
Movement rule: Inserting a new intermediate Branch around an existing Node does not by itself count as a Node move. A Node is classified as Moved only when its canonical Primary Map Layer or terminal Primary Map Branch changes.
The active AI Civilization Map always represents the current working model. Its present nine-layer form is a stable v1.2 working architecture, not a permanent taxonomic limit or a bottom-to-top pipeline. The Layer → Branch Path → Node hierarchy describes classification within Layers; cross-layer relationships may run in multiple directions. This Activity Log preserves the path by which Branches, Nodes, relationships, and—only when reality requires it—the canonical Layer architecture change.
Full admission, revision, and removal standards are documented in the K Robot Lab Writing and Map-Governance Standards.