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, and ordinary Node 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 and monthly Node additions, removals, promotions, demotions, moves, and archival decisions 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.
Monthly reviews use six canonical change classifications for Nodes. 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.
Archived Reference
Archived Reference is not a seventh Node-status 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 Node-status counts, Archived References separately, Branch changes including confirmed zero change, and a topology summary covering Layers, Branches, active Nodes, and reserved empty Branches.
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 Structure Changes
Branch changes are recorded separately from Node status because Branches are expandable structural paths rather than active units of evidence. Material changes may be classified as Branch Added, Branch Deepened, Branch Split, Branch Merged, Branch Renamed, or Branch Reorganized. When none occurs, the review records No Change, the maintained 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.