Runtime Version 3.0
Canonical purpose:
To ensure that every new Civilisation Atlas regional chronology inherits the same temporal architecture, evidence discipline, graph structure, CivOS analysis, portability framework and machine-readable safeguards.
Applies to:
- all new Coverage Objects;
- future revisions of Coverage Objects 01–14;
- regional, civilisational, thematic and planetary chronologies;
- human-readable pages;
- machine-readable
.txt,.jsonlor equivalent canonical objects; - AI retrieval, CAT scanning, simulation and CivilisationOS analysis.
1. What the regional chronology is
A Civilisation Atlas chronology is not merely a history article.
It is simultaneously:
A CHRONOLOGYA TEMPORAL COORDINATEA KNOWLEDGE GRAPHA DEPENDENCY MAPA FUNCTION–HOST MAPA CAT-SCAN OBJECTA CIVOS OBSERVATION SURFACEA PORTABILITY TEST BEDA FUTURE SIMULATION INPUT
Its purpose is not to prove that one region possesses a single continuous civilisation.
Its purpose is to reconstruct:
ENTITIESEVENTSPROCESSESFUNCTIONSHOSTSRELATIONSHIPSFLOWSDEPENDENCIESLINEAGESSTATE CHANGESEVIDENCEUNCERTAINTIES
across changing times, peoples, states, languages, institutions and environments.
2. Foundational rule
Every chronology must preserve the distinction:
PLACE CONTINUITY≠POPULATION CONTINUITY≠LANGUAGE CONTINUITY≠POLITICAL CONTINUITY≠RELIGIOUS CONTINUITY≠MEDIA CONTINUITY≠CIVILISATIONAL FUNCTIONAL CONTINUITY
A shared geography does not prove one continuous civilisation.
A shared name does not prove one continuous entity.
A later state does not automatically inherit every identity, claim or institution associated with an earlier polity occupying related territory.
3. Universal Atlas primitives
Every chronology must be capable of representing the following primitives:
ENTITYTIMESPACESTATEEVENTPROCESSRELATIONSHIPPART / WHOLEFLOWLINEAGEDEPENDENCYFUNCTIONHOSTCARRIERRESIDUEEVIDENCEUNCERTAINTY
UNKNOWN is a valid first-class value.
Missing information must not be filled by narrative assumption.
UNKNOWN≠NONENOT ATTESTED≠DID NOT EXISTNO EDGE≠PERMISSION TO INVENT AN EDGE
4. Canonical distinctions
The following distinctions must never be silently merged.
4.1 Function, host, implementation and outcome
FUNCTION≠HOST≠IMPLEMENTATION≠OUTCOME
Example:
FUNCTION:preserve collective memoryHOSTS:oral specialistcourtmanuscriptarchivemuseumdatabaseAIIMPLEMENTATIONS:genealogyepicinscriptionschool curriculumcataloguedigital modelOUTCOME:depends on host incentives,control geometry,legitimacy,access and feedback
4.2 Civilisation and state
CIVILISATION≠STATE
A civilisation may operate through:
POLITIESCITIESDIASPORASPORTSRELIGIOUS NETWORKSMERCHANT NETWORKSLANGUAGE SYSTEMSSCHOOLSCRAFT SYSTEMSMOBILE COMMUNITIESDIGITAL NETWORKS
A state may collapse while many civilisational functions survive.
4.3 Archive and capability
ARCHIVE≠CAPABILITYINFORMATION≠EXECUTIONDESCRIPTION≠REPRODUCTION
A book describing steel production does not itself provide:
oreenergyfurnacestoolsoperatorsmaintenancesupply chainsquality controlteaching
5. Canonical axes
The following axes must remain separate.
5.1 Capability Stage
Capability Stage measures the broad operating capability of a system.
FOUNDATION 0Adaptive human worlds without large-scalesettlement-surplus administrative systems.STAGE 1Settlement, surplus, persistent production,local specialisation and expanded coordination.STAGE 2Administrative, recorded and institutional systems.STAGE 3Industrial, infrastructural and mass-institution systems.STAGE 4Planetary network civilisation.STAGE 5Regenerative, self-observing, self-correcting civilisation.
Stage 5 is not where CivilisationOS begins.
CivOS-like operating functions appear much earlier.
Stage 5 is the threshold at which civilisation can reliably:
observe itselfmodel itselfdiagnose itselfrepair itselfchange its own operating architecturewithout destroying its BaseFloor
Do not add multi-world expansion as Stage 6–8.
Multi-world distribution belongs on a separate axis.
5.2 Civilisation Lifecycle
Lifecycle measures direction and condition, not capability.
TAKEOFFCLIMBCRUISEDRIFTDESCENTREPAIRRELAUNCHCOLLAPSE
A Stage 4 civilisation may be in descent.
A Stage 1 system may be climbing.
Capability and lifecycle must never be treated as one ladder.
5.3 Module Reproduction Lifecycle
This axis applies to a bounded module such as:
languagereligious institutioncraft systemadministrative procedurelegal traditionmerchant networkmemory system
Use:
MRL0 — SUBSTRATEMRL1 — FORMATIONMRL2 — CONSOLIDATIONMRL3 — EXPANSIONMRL4 — HIGH REPRODUCTIONMRL5 — STRESSMRL6 — FISSIONMRL7 — RECOMPOSITIONMRL8 — DORMANT ARCHIVEMRL9 — LIVING RENEWAL
DORMANT_ARCHIVE means that active execution has greatly weakened or stopped, but sufficient residue remains for later reconstruction or renewal.
5.4 Capability Reach
Capability Reach measures how widely a function operates.
CR0 — LATENTCR1 — LOCALCR2 — INTERLOCAL / NETWORKEDCR3 — REGIONALCR4 — TRANSREGIONAL / MACROSYSTEMCR5 — PLANETARY
Do not call this Capability Stage.
5.5 Survivable Range
Survivable Range measures the environments across which the system can operate.
SR0 — SITE-BOUNDSR1 — LOCAL ECOSYSTEMSR2 — ECOREGIONALSR3 — MULTI-ECOZONESR4 — TRANSREGIONALSR5 — PLANETARYSR6 — OFFWORLD EXTENSIONSR7 — MULTI-HABITAT REDUNDANCY
5.6 World Distribution
World Distribution measures spatial distribution across worlds.
WD0 — SINGLE-WORLDWD1 — EXTRA-WORLD OUTPOSTWD2 — MULTI-WORLD DEPENDENTWD3 — AUTONOMOUS DAUGHTERWD4 — DISTRIBUTED INTERPLANETARY NETWORK
A Mars outpost may be WD1 while remaining completely dependent on Earth.
World Distribution must not be mistaken for capability or independence.
5.7 Dependency Closure
Dependency Closure measures how much of the operating stack can be maintained locally.
DC0 — EXTERNALLY SUSTAINEDDC1 — PARTIAL BASEFLOOR CLOSUREDC2 — CORE SERVICES LOCALISEDDC3 — INDUSTRIAL MAINTENANCE LOCALISEDDC4 — MULTI-DOMAIN FUNCTIONAL CLOSUREDC5 — REGENERATIVE AUTONOMY
This is the preferred replacement for ambiguous “habitat independence” ladders.
5.8 Time Zoom
Always use TZ, never a bare Z.
TZ0 — PLANETARY / GEOLOGICAL DEEP TIMETZ1 — BIOLOGICAL / HOMININ DEEP TIMETZ2 — LONG PREHISTORYTZ3 — SETTLEMENT AND EARLY COMPLEXITYTZ4 — HISTORICAL CENTURY-SCALETZ5 — EARLY MODERN / DECADALTZ6 — MODERN / ANNUALTZ7 — LIVE HIGH-RESOLUTION EVENT STATE
5.9 Entity Zoom
Always use EZ, never a bare Z.
EZ0 — PHYSICAL SUBSTRATEEZ1 — ECOLOGICAL / BIOLOGICAL SYSTEMEZ2 — PERSON / AGENTEZ3 — HOUSEHOLD / COMMUNITYEZ4 — INSTITUTION / ORGANISATIONEZ5 — SETTLEMENT / POLITYEZ6 — REGIONAL CIVILISATIONAL SYSTEMEZ7 — PLANETARY SYSTEMEZ8 — MULTI-WORLD SYSTEM
6. Time architecture
Every record must separate temporal shape from temporal certainty.
Do not use one field such as DATE_STATUS for both.
Use:
TEMPORAL_FORM:POINTCLOSED_INTERVALOPEN_INTERVALRECURRINGUNKNOWN
and:
BOUNDARY_CERTAINTY:EXACTAPPROXIMATEESTIMATEDCONTESTEDUNKNOWN
Example:
TIME:2022–2024TEMPORAL_FORM:CLOSED_INTERVALBOUNDARY_CERTAINTY:EXACT
The date of an event must be distinguished from the date a source was published.
EVENT_DATE≠SOURCE_PUBLICATION_DATE
7. World-band addressing
Every record must contain appropriate World Master Clock addressing.
For a continuing process, do not attach only the starting band.
Use:
WORLD_BAND_STARTWORLD_BAND_ENDWORLD_BANDS_ACTIVE[]ANCHOR_BAND
Example:
PROCESS:2011 onwardWORLD_BAND_START:W060WORLD_BAND_END:OPENWORLD_BANDS_ACTIVE:W060–W068ANCHOR_BAND:W060
This allows cross-sectional CAT scans to retrieve processes that remain active after their starting period.
8. Canonical chronology record
Every protected record should support the following structure.
RECORD { RECORD_ID TITLE SUMMARY TEMPORAL_FORM TIME_START TIME_END BOUNDARY_CERTAINTY WORLD_BAND_START WORLD_BAND_END WORLD_BANDS_ACTIVE[] ANCHOR_BAND TIME_ZOOM ENTITY_ZOOM LOCATIONS[] ENTITIES[] RECORD_TYPE: EVENT PROCESS STATE TRANSITION ASSERTION CURRENT_COORDINATE FUNCTIONS[] HOSTS[] CARRIERS[] FLOWS[] DEPENDENCIES[] LINEAGES[] RELATIONSHIPS[] CONTROL_GEOMETRY[] BASEFLOOR_EFFECTS[] CAPABILITY_STAGE LIFECYCLE_PHASE MODULE_REPRODUCTION_LIFECYCLE CAPABILITY_REACH SURVIVABLE_RANGE WORLD_DISTRIBUTION DEPENDENCY_CLOSURE MOTION_VECTOR EVIDENCE_TYPES[] CLAIM_STATUS CONFIDENCE UNCERTAINTIES[] SOURCE_KEYS[] GRAPH_SEEDS[]}
Fields may be null when unsupported.
They must not be fabricated merely to complete the schema.
9. Current-state and live-tail discipline
Near the present cut-off, each claim must be typed.
Use:
OBSERVEDOFFICIAL_RECORDATTRIBUTED_STATEMENTASSESSEDALLEGEDDENIEDDISPUTEDLEGAL_INTERPRETATIONANNOUNCEDPLANNEDCONDITIONALFORECASTUNVERIFIABLEINCOMPLETE
Examples:
A policy announcement≠implemented capabilityA planned delivery≠completed transferAn inaccessible stockpile≠destroyed stockpileA government claim≠independent verification
The live coordinate must use:
TZ7CURRENT WORLD BANDEXPLICIT CUT-OFF DATE
10. Evidence typing
Do not reuse archaeological evidence labels for modern events.
Evidence types may include:
ARCHAEOLOGICALEPIGRAPHICTEXTUALORALLINGUISTICGENETICENVIRONMENTALGEOLOGICALDEMOGRAPHICADMINISTRATIVELEGALOFFICIALECONOMICPHOTOGRAPHICSATELLITEDIGITALMILITARYSCIENTIFICJOURNALISTICMULTI_SOURCE
Evidence status must remain distinct from relationship type.
11. Source registry
Every source key must resolve to a complete source object.
SOURCE { SOURCE_ID FULL_TITLE AUTHOR_OR_INSTITUTION YEAR PUBLICATION_OR_PUBLISHER SOURCE_TYPE DOI ISBN STABLE_URI ACCESS_DATE CLAIMS_SUPPORTED[] NOTES}
Use:
ONE SOURCE OBJECT→ MANY RECORD EDGES
Do not create repeated source keys for the same work.
12. Relationship architecture
Do not use one relationship-grade ladder that mixes relationship type and evidence resolution.
Use:
RELATION_ASSERTION { SOURCE_ENTITY TARGET_ENTITY RELATION_TYPE DIRECTION TIME ATTESTATION_STATUS EVIDENCE_STATUS CONFIDENCE}
Possible relation types include:
COMPARABLE_TOPART_OFDESCENDED_FROMINFLUENCED_BYCO_PRESENT_WITHREACHABLE_FROMCONNECTED_BY_FLOWINTERACTS_WITHHOSTSCARRIESDEPENDS_ONREPLACESRECOMBINES_WITH
Possible attestation statuses include:
HYPOTHETICALINFERREDCOLLECTIVELY_ATTESTEDINDIVIDUALLY_ATTESTEDDIRECTLY_DOCUMENTED
COMPARABLE_TOdoes not implyINFLUENCED_BYREACHABLE_FROMdoes not implyINTERACTS_WITH
13. Temporal Identity Firewall
Every chronology must protect against names travelling incorrectly through time.
TEMPORAL_IDENTITY_FIREWALL { LABEL REQUESTED_TIME ENTITY_TYPE GEOGRAPHIC_SCOPE EVIDENCE_CLASS PERIOD_CORRECT_OBJECT}
Examples:
ANCIENT POLITY≠RELIGIOUS LITERARY IDENTITY≠MODERN STATEGEOGRAPHIC TERM≠ADMINISTRATIVE PROVINCE≠MODERN PEOPLE≠LEGAL TERRITORY
This firewall is mandatory where labels are politically, religiously or historically overloaded.
14. Adaptive Zoom and temporal aliasing
The Atlas must not assume that one zoom reveals every phenomenon.
Use multiple resolutions:
EVENT ZOOMWhat happened?AGENT ZOOMWho acted?INSTITUTION ZOOMWhich organisation carried it?FUNCTION ZOOMWhat civilisational function was performed?HOST ZOOMWhat carried that function?DEPENDENCY ZOOMWhat did it rely upon?CENTURY ZOOMDid the function survive the host?MILLENNIAL ZOOMDid the function repeatedly migrate?
Civilisational Temporal Aliasing occurs when the sampling interval hides the actual process.
SAMPLE ONE LIFETIME→ SEE ONE HOSTSAMPLE REGIME CHANGES→ SEE SEPARATE SYSTEMSTRACK THE FUNCTION→ SEE HOST MIGRATION
15. Function–Host architecture
Every chronology should attempt to identify persistent functions beneath changing implementations.
Common civilisational functions include:
MEMORYCOORDINATIONLEGITIMACYRESOURCE ALLOCATIONEDUCATIONREPRODUCTION OF KNOWLEDGEEXCHANGESECURITYLAWHEALTHINFRASTRUCTURESENSINGREPAIRDECISIONCOMMUNICATION
Hosts may include:
PERSONFAMILYCOMMUNITYCOURTOFFICEINSTITUTIONGUILDRELIGIOUS COMMUNITYDIASPORATEXTOBJECTRITUALPLACEARCHIVESTATECOMPANYPLATFORMCOMPUTERAIROBOTIC SYSTEM
16. Host Migration
Host Migration must become a first-class record.
HOST_MIGRATION { FUNCTION SOURCE_HOST TARGET_HOST MIGRATION_DRIVER CARRIER PATH PORTABLE_RESIDUE MINIMUM_HOST_REQUIREMENTS FUNCTION_PRESERVED FUNCTION_LOST PHENOTYPE_CHANGE CONTROL_CHANGE LEGITIMACY_CHANGE SOURCE_HOST_DAMAGE CONFIDENCE}
Common migration drivers include:
CAPACITY SATURATIONSPEEDSCALEHOST DESTRUCTIONPOLITICAL FRACTUREREPRESSIONMIGRATIONENVIRONMENTAL CHANGETECHNOLOGICAL CHANGEECONOMIC CHANGESURVIVAL
Two major classes must be distinguished:
CAPACITY MIGRATIONOld host cannot process sufficient load.SURVIVAL MIGRATIONOld host disappears or becomes hostile.
17. Motion Vector
Every major transformation may use:
MOTION_VECTOR { START_STATE DRIVER CARRIER PATH END_STATE COST RESISTANCE RESIDUE CONFIDENCE}
RESIDUE identifies what survives strongly enough to seed another implementation.
18. Module Seed and Civilisation Seed
These terms must never be merged.
Module Seed
MODULE_SEED=smallest transferable packagecapable of reproducingone bounded civilisational function
It may contain:
knowledgetrained peopleobjectsprocedureslegitimacy rulesteaching methodminimum host conditions
Examples:
merchant credit systemscribal procedurereligious missioncraft schoolconstitutional officelanguage curriculum
Civilisation Seed
CIVILISATION_SEED=CIVILISATION KERNEL+PHYSICAL BOOTSTRAP PACKAGE
It must support enough closure across:
airwaterfoodenergyshelterhealthsecuritymaterialsindustrymanufacturinglogisticsknowledgeeducationcomputingcommunicationgovernanceecologyrepair
A collection of books or datasets is not a Civilisation Seed.
19. Portability ladder
Use the following ladder.
P0 — DATA PORTABILITYRaw records can be transferred.P1 — KNOWLEDGE-PACKET PORTABILITYTyped knowledge can be correctly retrieved by a new host.P2 — PROCEDURAL PORTABILITYA procedure can be taught and executed elsewhere.P3 — MODULE PORTABILITYA bounded civilisational function can reproduce on a new host.P4 — MULTI-MODULE FUNCTIONAL PORTABILITYSeveral dependent modules can operate together.P5 — KERNEL PORTABILITYGenerative operating logic can rebuild a broad stack.P6 — REGENERATIVE CIVILISATIONAL PORTABILITYA new host can maintain, repair and reproduce a viable civilisation.
Every portability test must state which level it has actually demonstrated.
Do not label P1 knowledge retrieval as full Portable Civilisation.
20. Fission namespaces
Do not use “fission” as one undifferentiated term.
Use:
ENTITY_DECOMPOSITIONAn ambiguous label is separated into correctly typed objects.POLITY_FISSIONA political unit divides.DYNASTIC_FISSIONA ruling lineage divides.TERRITORIAL_FISSIONJurisdiction separates spatially.POPULATION_FISSIONCommunities disperse.MODULE_FISSIONCivilisational functions split across hosts.INSTITUTIONAL_FISSIONAn institution produces successor institutions.DATA_FISSIONObjects, records and authority become separated.SENSOR_FISSIONDifferent observers retain incompatible partial views.CIVILISATIONAL_FISSIONA parent civilisation produces a viable,self-maintaining daughter civilisation.
21. Legacy Stack
New civilisational systems frequently layer over older ones.
LEGACY_STACK { CURRENT_LAYER PREVIOUS_LAYERS[] RETAINED_FUNCTIONS[] SUPPRESSED_FUNCTIONS[] RECLASSIFIED_FUNCTIONS[] COMPATIBILITY_RELATIONSHIPS[] FAILURE_POINTS[]}
Typical pattern:
MODERN STATE────────────────COLONIAL ADMINISTRATION────────────────OLDER POLITICAL OFFICES────────────────KINSHIP / CUSTOMARY AUTHORITY────────────────ECOLOGICAL SETTLEMENT LOGIC
Civilisational change is usually layered, not a clean OS replacement.
22. Stage Nesting
Multiple capability regimes may coexist within the same region and time.
STAGE_NESTING=multiple capability-stage functionscoexisting inside onecivilisational space-time
Examples:
Stage 4 digital system+Stage 3 industrial enclave+Stage 2 bureaucracy+Stage 1 food system+Foundation 0 ecological dependence
Never assign a whole region one stage when important subsystems differ.
23. Capability Enclave
CAPABILITY_ENCLAVE=high-capability subsystemembedded insidea lower-capability orweaker-BaseFloor environment
Examples may include:
industrial minedata centreportfinancial districtmilitary complexresearch laboratory
A capability enclave does not automatically upgrade its surrounding civilisation.
24. BaseFloor
Every chronology must evaluate at least two BaseFloor layers.
Natural BaseFloor
habitable environmentairwaterfoodbiological healthclimateecological support
Civilisational BaseFloor
sheltersecurityenergyhealthknowledge continuitysocial stabilityinfrastructuregovernance
Constructed Dependency Floor
electricitytelecommunicationscomputingsemiconductorslogisticsindustrial supply chainsdigital networks
Upper capability remains dependent on lower floors.
25. Flow and control architecture
Political maps are insufficient.
Every chronology should ask:
WHO CONTROLS THE VALVES?
Use:
FLOW_VALVE { FLOW VALVE CONTROLLER USERS DEPENDENCIES BENEFICIARIES EXTERNALISED_COSTS FAILURE_EFFECT}
Control geometry may include:
POINTLINESURFACENETWORKSTACK
A narrow line or node may have planetary consequences.
GEOGRAPHIC CONTROL SCALE≠CONSEQUENCE SCALE
26. Selective Flow Amplification
Infrastructure does not amplify “civilisation” uniformly.
It amplifies selected flows.
SELECTIVE_FLOW_AMPLIFICATION { INFRASTRUCTURE AMPLIFIED_FLOW SUPPRESSED_OR_DAMAGED_FLOWS[] BENEFICIARIES[] COST_BEARERS[] LONG_TERM_DEPENDENCIES[]}
Examples:
mine → port railwaydam → industrial electricityport → container throughputplatform → data flow
while other local flows may weaken.
27. Distributed and asynchronous civilisation
Some civilisations operate through network nodes rather than one territorial centre.
A distributed civilisational field may consist of:
NODESROUTESCARRIERSPROTOCOLSMEMORYTRUSTPERIODIC EXCHANGE
Pulse-Synchronised Network
PULSE_SYNCHRONISED_NETWORK=nodes operate locallybetween predictablereconnection windows
It requires:
local autonomystored stateshared protocolstrusted carriersscheduled exchangeeventual synchronisation
This is relevant to maritime worlds and future delayed multi-world communication.
28. Protocol Language
PROTOCOL_LANGUAGE=portable linguistic interfacethat enables coordinationacross distinct communities,institutions and host systems
A protocol language may migrate through:
tradereligionadministrationeducationbroadcastingdigital systemsAI
29. Translation Layer
Transferred modules rarely execute identically in new hosts.
TRANSLATION_LAYER { INCOMING_MODULE SOURCE_CONTEXT TARGET_CONTEXT LOCAL_LANGUAGE LOCAL_ECOLOGY LOCAL_INSTITUTIONS COMPATIBILITY_CHANGES LOST_CONTEXT NEW_PHENOTYPE}
The preferred principle is:
TRANSLATION WITHOUT DISSOLUTION
The receiving system adapts external input without merely becoming a copy of the source.
30. Civilisational Gateway
A gateway converts between systems.
CIVILISATIONAL_GATEWAY { SYSTEM_A SYSTEM_B TRANSLATION_FUNCTIONS[] VERIFICATION_FUNCTIONS[] STORAGE_FUNCTIONS[] CREDIT_FUNCTIONS[] PERMISSION_FUNCTIONS[] TRANSFER_FUNCTIONS[]}
Possible gateways include:
portscaravan terminimerchant diasporastranslation schoolscourtsuniversitiespayment systemsdigital platformsAI interfaces
31. Host-Conditioned Expression
The same module may produce different outcomes under different hosts.
MODULE+HOST INCENTIVES+CONTROL GEOMETRY+LEGITIMACY+FEEDBACK=OBSERVED PHENOTYPE
Use:
HOST_CONDITIONED_EXPRESSION { MODULE HOST INCENTIVES CONTROL LEGITIMACY FEEDBACK RESULTING_PHENOTYPE}
Host migration is therefore not merely:
same functionbut faster
It may preserve capability while changing politics, accountability, access and failure modes.
32. Orphaned Portability
ORPHANED_PORTABILITY=portable module scaleswhile the community,habitat or institutionthat generates it declines
Possible pattern:
language expandswhile local varieties disappearheritage brand expandswhile residents are displacedtourism expandswhile living craft weakensAI model preserves surface procedurewhile tacit human repair knowledge disappears
Every portability analysis should test for source-host damage.
33. Sensor Damage
Archive destruction, censorship, internet shutdown and inspector exclusion belong to one higher-order class.
SENSOR_HOST_FAILURE ↓OBSERVABILITY FALLS ↓MODEL ERROR RISES ↓CONTROL QUALITY FALLS ↓SYSTEM RISK RISES
Use:
SENSOR_DAMAGE { SENSOR_HOST DAMAGE_TYPE LOST_OBSERVATIONS[] MODEL_EFFECT DECISION_EFFECT ESCALATION_RISK RECOVERY_REQUIREMENTS[]}
34. Information Host Amplification
INFORMATION PRESSURE+EXTERNAL MEMORY HOST→GREATER COORDINATION CAPACITY→GREATER SYSTEM SCALE→GREATER INFORMATION PRESSURE
This may appear in:
writingarchivesprintingbureaucracycomputingnetworkssearchAI
The solution to one information bottleneck can generate the next complexity layer.
35. Media Succession
MEDIA HOST DECLINE≠FUNCTIONAL DEATH
Track how functions migrate across:
oral memoryinscriptionmanuscriptprintbroadcastdatabaseinternetAI
The medium may disappear while administration, teaching, memory or legal interpretation continues elsewhere.
36. Standardisation Paradox
STANDARDISATION→ LOWER COORDINATION COST→ LARGER SYSTEM→ STRONGER ENFORCEMENT→ POSSIBLE LOCAL INFORMATION LOSS→ BRITTLENESS OR RESISTANCE
Standardisation may increase central operating resolution while decreasing peripheral or local resolution.
Test this for:
languagescriptcoinagelawmeasurementcurriculumsoftwaredata formats
37. Identity Compression
HIGH-DIMENSIONAL PAST ↓SIMPLIFIED IDENTITY CLAIM ↓POLITICAL MOBILISATION ↓SELECTIVE EVIDENCE ↓STRONGER SIMPLIFICATION
Compression can make knowledge portable.
It can also erase multiplicity and uncertainty.
The Atlas must distinguish:
GOOD COMPRESSIONpreserves necessary distinctionsBAD COMPRESSIONremoves relationships required for truth
38. Evidence Saturation
EVIDENCE VOLUME>VERIFICATION AND INTEGRATION CAPACITY→LOWER EFFECTIVE KNOWLEDGE
More data does not automatically produce more understanding.
High-volume evidence requires:
provenancetypingtemporal addressingsource resolutionrelationship disciplineuncertainty
39. Temporary Host Crystallisation
TEMPORARY RESPONSE+LONG DURATION+REPRODUCTION+INSTITUTIONAL EMBEDDING→PERSISTENT CIVILISATIONAL MODULE
A camp, emergency authority, temporary settlement or wartime institution may become a durable host if it develops:
familiesschoolsmarketsmemoryidentityinfrastructuregovernance
40. Substrate Path Memory
Physical geography and inherited infrastructure can repeatedly channel later systems.
PHYSICAL CONFIGURATION+PAST INFRASTRUCTURE+ACCUMULATED STRATEGIC VALUE→RECURRING FUTURE USE
Possible examples:
passesportsriver valleysstraitssacred centresroadscanalsrail corridors
The substrate “remembers” structurally through affordances and path dependence.
41. Latent Substrate Activation
PHYSICAL FEATURE+NEW CAPABILITY+NEW DEMAND=NEW CIVILISATIONAL RESOURCE
A material is not automatically a civilisational resource merely because it exists.
PHYSICAL AVAILABILITY≠CIVILISATIONAL RESOURCE
The system must be capable of:
perceivingvaluingextractingprocessingroutingmaintaining
it.
42. Lineage Braid
Civilisational lineage is often a braid rather than a ladder.
Do not force:
A→ B→ C
when evidence supports:
A
↙ ↘
B C
↘ ↙
D
↙ ↘
E F
Track:
parallel centrescompetitionborrowingmigrationshared craftroute changespolitical recombination
43. Multi-Clock Transition
Political, linguistic, religious, demographic and media transitions do not occur at one speed.
POLITICAL CONQUEST≠LANGUAGE CHANGE≠RELIGIOUS CHANGE≠MEDIA CHANGE≠POPULATION CHANGE≠INSTITUTIONAL CHANGE
Every major transition should identify which clocks changed and which remained continuous.
44. Phase Frequency, Reproduction Frequency and Agent Flux
These are separate variables.
State-Transition Frequency
STF=number of meaningful operating-state changeswithin a selected interval
Reproduction Frequency
RF=how frequently a modulesuccessfully reproduces or regenerates
Agent Flux
AGENT_FLUX=capacity for people,institutions or machinesto enter,learn,replace failed operators,preserve functionand transfer capability
Low Agent Flux may reveal hidden single-point failure.
45. Civilisational Shear
Civilisational Shear occurs when subsystem clocks move at incompatible rates.
FAST:marketselectionsattacksplatformsinformationSLOW:aquifersreefshousingarchivestrainingtrustinstitutional repair
SPEED_MISMATCH→REPAIR LAG→ACCUMULATED FRACTURE
46. Education Gate
A capability becomes civilisational only when a new generation can:
recognise its purposeunderstand its dependenciesperform itmaintain itrepair itteach ittransfer itrecognise when not to use it
ONE PERSON CAN PERFORM IT≠CIVILISATION POSSESSES IT
Every major portability test should include an Education Gate assessment.
47. Wormholes with Cost
Civilisation may import a capability without repeating the complete history that produced it.
CIVILISATIONAL WORMHOLE=transferred capabilitythat shortens development time
Every wormhole must record:
lost contexthidden dependencyhost mismatchinstitutional displacementcontrol changeside effects
48. CAT-scan architecture
Every mature regional chronology should provide:
LONGITUDINAL SCANWhat changes through time?CROSS-SECTIONAL SCANWhat coexists in one World band?RELATIONSHIP SCANWho is linked to whom?DEPENDENCY SCANWhat requires what?FLOW SCANWhat moves?LINEAGE SCANWhat descends, branches or recombines?HOST SCANWhat carries the function?CONTROL SCANWho controls points, lines, surfaces,networks and stacks?EVIDENCE SCANHow is the claim known?REVERSE HYDRA SCANThrough which unrepaired dependencycan the problem regenerate?
49. Genome and phenotype
Use:
CIVILISATIONAL GENOME=persistent generative relationshipPHENOTYPE=historical expression underspecific host and environment
Example:
GENOME:long-distance exchange requires brokeragePHENOTYPES:caravan intermediaryport merchantrail junctionpayment networkdigital API
Do not confuse recurring architecture with identical historical forms.
50. Pressure Field
Every major system should identify pressure vectors such as:
ecologicaldemographiceconomicmilitarypoliticalreligioustechnologicalinformationalinstitutionalexternal
Pressure creates a possibility field.
It does not mechanically determine one outcome.
STRUCTURE→ POSSIBILITY SPACE→ PRESSURE→ CONTINGENT ACTION→ SELECTION→ PERSISTENCE→ EMERGENCE→ NEW STRUCTURE
51. Ouroboros
Every chronology should identify feedback loops where an adaptation creates the next pressure.
RESOURCE→ ADVANTAGE→ MORE INVESTMENT→ MORE DEPENDENCE→ MORE RESOURCE DEMAND
Examples may involve:
cattleprestige goodsminesdamsbureaucracywritingdataplatform users
The implementation changes.
The loop architecture may persist.
52. Reverse Hydra
A visible problem may return through unrepaired dependencies.
VISIBLE HEAD REMOVED+ROOT DEPENDENCIES REMAIN=PROBLEM REGENERATES
Each Reverse Hydra test should identify:
visible symptomremoved componentremaining dependenciesreplacement pathwayregrowth mechanismrepair requirements
53. Counterfactual sensitivity versus simulation
Do not label a one-line “what if” as a completed simulation.
Use:
LEVEL 1VARIABLE REMOVAL QUESTIONLEVEL 2SENSITIVITY HYPOTHESISLEVEL 3DEPENDENCY RECALCULATIONLEVEL 4BRANCHING SIMULATIONLEVEL 5OUTCOME COMPARISON+UNCERTAINTY CONE
Only Levels 4–5 should be called full simulation.
54. Required article structure
Every new regional chronology should use the following order.
0. RELEASE MANIFEST1. PURPOSE AND SCOPE2. GEOGRAPHIC AND TEMPORAL BOUNDARIES3. CATEGORY AND IDENTITY FIREWALL4. CANONICAL AXES AND REGISTRIES5. EVIDENCE AND SOURCE POLICY6. MASTER CHRONOLOGY7. LONGITUDINAL SYSTEM TRACKS8. GRAPH NODES, EDGES AND CONNECTORS9. WORLD-BAND CROSS-SECTIONS10. CAT-SCAN TRAVERSALS11. GENOME AND PHENOTYPE12. PRESSURE FIELDS13. OUROBOROS LOOPS14. REVERSE HYDRA TESTS15. FUNCTION–HOST ARCHITECTURE16. HOST MIGRATION17. LEGACY STACKS18. STAGE NESTING AND CAPABILITY ENCLAVES19. FLOW VALVES AND CONTROL GEOMETRY20. MODULE SEEDS21. PORTABILITY TESTS22. FISSION TESTS23. EDUCATION GATE24. AGENT FLUX AND PHASE FREQUENCY25. COUNTERFACTUAL SENSITIVITY26. REPAIR TESTS27. LIVE CIVILISATION COORDINATE28. UNCERTAINTY REGISTER29. SOURCE REGISTER30. MACHINE ASSERTION TESTS31. KNOWN LIMITS32. VERSION CHANGELOG
Not every section must be equally long.
Unsupported sections may state:
NO DEFENSIBLE RESULT YET
rather than inventing content.
55. Release manifest
Every article should begin with a machine-readable release block.
CIVILISATION_ATLAS_OBJECT { OBJECT_ID COVERAGE_NUMBER TITLE REGION VERSION CUT_OFF_DATE STATUS INHERITS: CIVATLAS.SCAFFOLD.001 CIVATLAS.SCAFFOLD.002 CIVATLAS.SCAFFOLD.003 CIVATLAS.SCAFFOLD.004 CIVATLAS.REGIONAL.RUNTIME.V3.0 RECORD_COUNT GRAPH_SEED_COUNT SYSTEM_TRACK_COUNT NODE_COUNT CONNECTOR_COUNT CAT_SCAN_COUNT OUROBOROS_COUNT HOST_MIGRATION_COUNT PORTABILITY_TEST_COUNT FISSION_TEST_COUNT UNCERTAINTY_RULING_COUNT SOURCE_COUNT MACHINE_TEST_COUNT}
56. Inheritance rules
Every future object must inherit these rules:
DO NOT silently redefine Capability Stage.DO NOT merge Capability Stage with Lifecycle.DO NOT use bare H, Z, C or L codeswhen multiple registries exist.DO NOT call module portabilitywhole-civilisation portability.DO NOT call entity decompositioncivilisational fission.DO NOT call a sensitivity questiona completed simulation.DO NOT back-project modern identities.DO NOT convert absence of evidenceinto evidence of absence.DO NOT convert comparisoninto contact or descent.DO NOT convert a source publication dateinto an event date.DO NOT treat an announcementas implemented capability.DO NOT treat one expertas a reproduced civilisational capability.DO NOT fabricate fieldsto make the schema look complete.
57. Machine validation gates
Before publication, every object should pass the following gates.
Chronology Gate
World bands correctTime zoom correctEntity zoom correctPoint and interval dates separatedEvent date separated from source dateOpen processes active in later bands
Evidence Gate
Modern events not labelled archaeologicalClaims typed correctlyUncertainty preservedPrimary and secondary evidence distinguished
Identity Gate
Ancient labels not merged with modern statesArchaeological culture not treated as ethnicityReligion not treated as nationalityGeography not treated as legal sovereignty
Axis Gate
Capability Stage separateLifecycle separateModule lifecycle separateReach separateSurvivable range separateWorld distribution separateDependency closure separate
Portability Gate
Portability level statedCarrier statedMinimum host statedEducation Gate testedFailure mode statedSource-host damage tested
Host Migration Gate
Function identifiedSource host identifiedTarget host identifiedCarrier identifiedResidue identifiedPreserved and lost functions distinguishedPhenotype and control changes recorded
Source Gate
All source keys resolvableNo duplicate source objectsStable locators suppliedClaims linked to sources
Publication Gate
Reader HTML publishedCanonical machine file publishedVersion declaredSHA-256 suppliedChangelog supplied
58. Publishing architecture
Each object should eventually publish three linked artefacts.
REGION.html=human-readable projectionREGION.CANONICAL.Vx.x.txtorREGION.CANONICAL.Vx.x.jsonl=machine source of truthREGION.CANONICAL.Vx.x.sha256=integrity verification
The HTML page must not be treated as the only canonical machine file.
59. Status of the discoveries
The following are now strong recurring candidate CivOS primitives:
FUNCTION ≠ HOSTFUNCTIONS CAN MIGRATEHOST CHANGE CAN CHANGE PHENOTYPEPOLITICAL COLLAPSE≠TOTAL FUNCTIONAL DEATHMODULES CAN FISSION AND RELAUNCHCIVILISATION HAS LEGACY STACKSMULTIPLE CAPABILITY STAGES CAN COEXISTHIGH CAPABILITY CAN EXIST AS AN ENCLAVEFLOW CONTROL≠TERRITORIAL CONTROLCIVILISATIONAL LINEAGES ARE OFTEN BRAIDEDPORTABILITY APPEARS MODULE-BY-MODULECIVILISATION CAN OPERATETHROUGH DISTRIBUTED NETWORKSCONTINUOUS CONNECTIONIS NOT ALWAYS REQUIREDLANGUAGE CAN FUNCTIONAS A CIVILISATIONAL PROTOCOLCOMPRESSION CAN PRESERVEOR DESTROY RELATIONAL TRUTHSENSOR FAILURE DAMAGESCIVILISATIONAL SELF-CORRECTIONINFORMATION HOSTS EXPAND CAPACITYAND CREATE NEW COMPLEXITYSUCCESSFUL SOLUTIONSCAN BECOME FUTURE LOCK-IN
These are not yet universal laws.
Each new chronology should attempt to:
CONFIRMREFINECONTRADICTLIMITOR REJECT
them.
History retains veto power over the theory.
60. The deeper architecture now emerging
The accumulated regional work suggests the following provisional stack:
L0 — PLANETARY SUBSTRATEgeologyclimateenergyecologyL1 — BIOLOGICAL LIFEorganismsadaptationreproductionL2 — HUMAN SOCIAL SYSTEMlanguagekinshipculturecooperationmemoryL3 — CIVILISATIONAL FUNCTIONSfoodwaterlawexchangeknowledgegovernanceinfrastructurecoordinationL4 — HOST ARCHITECTUREhumansinstitutionstextsobjectsplacesmachinesnetworksAIL5 — CIVILISATIONOSpersistent operating relationshipsfeedbackallocationcontrolrepairreplacementreproductionL6 — CIVILISATION ATLASobservabilitytimespacerelationshipsdependencieslineageevidenceL7 — META-CIVOSdiagnosissimulationrepairself-correctionoperating-system modificationL8 — CIVILISATION KERNELcompressed generative architectureL9 — PORTABLE CIVILISATIONkernel+host+physical bootstrapL10 — CIVILISATIONAL FISSIONMany₁→ One interoperable inheritance→ Many₂ descendant civilisations
The regional chronologies are therefore not merely supporting articles.
They are the empirical observation layer through which this architecture must be tested.
CANONICAL CLOSING RULE
Every new chronology must attempt to answer:
WHAT EXISTED?WHEN DID IT EXIST?WHERE DID IT OPERATE?WHAT FUNCTION DID IT PERFORM?WHAT HOST CARRIED IT?WHAT DID IT DEPEND UPON?WHAT MOVED?WHAT PERSISTED?WHAT CHANGED HOST?WHAT WAS LOST?WHAT WAS RECOMBINED?WHAT COULD BE REPRODUCED?WHAT COULD NOT?WHAT DOES THE EVIDENCE SUPPORT?WHAT REMAINS UNKNOWN?
The Atlas must not compress history until it becomes simple.
It must compress history until it becomes:
PORTABLEQUERYABLERELATIONALEVIDENCE-BEARINGUNCERTAINTY-PRESERVINGAND STILL TRUE