AI Kernel 000
The master loader, registry, runtime contract and amendment authority for the Civilisation Atlas AI Kernel. This page sits above the two large Full Stack pages so they can remain stable source volumes while routing, statuses, schemas and future corrections are managed here.
The two Full Stack pages are now treated as stable source volumes. Future operational changes should be written into this wrapper unless a genuine conceptual defect requires a new extension.
The two oversized pages become read-only source volumes
Load a source volume only when its concepts are required. Do not assume that a reference to a kernel ID proves that the corresponding kernel has been published. Resolve the exact ID inside the declared volume.
AI Kernel Full Stack — Volume I
Primary source for the Civilisation Atlas definition, complex adaptive system model, capability, continuity, layers, stages, inheritance, memory, dependencies, correction and the original AI reading spine.
- Declared search range:
CA-AI-KERNEL-001toCA-AI-KERNEL-014 - Resolution method: exact in-document
article_idor exact heading match - Absent ID status:
unresolved, never silently inferred
Zoom, Memory and Wormhole Stack — Volume II
Primary source for cross-zoom path compression, educational and institutional wormholes, doorway and corridor logic, borrowed capability, retention, return, dependency, extraction, regeneration and the extended diagnostic schema.
- Declared search range:
CA-AI-KERNEL-015toCA-AI-KERNEL-024 - Known entry point:
CA-AI-KERNEL-015 - Resolution method: exact in-document
article_idor exact heading match
A record saying that Kernel 015 depends on Kernel 008, or that Kernels 016–024 use Kernel 015, establishes a relationship claim. It does not by itself prove that every referenced article is present, published or canonical.
Every ID is resolved by exact evidence
This closes the Kernel 008 and 016–024 ambiguity without requiring the large pages to be rebuilt. The resolver identifies the correct source volume, searches for the exact ID and returns a truthful status.
| Requested ID | Source volume | Required test | Permitted status | Forbidden behaviour |
|---|---|---|---|---|
CA-AI-KERNEL-001–014 |
Volume I | Exact article_id, heading or compact-kernel match |
published or unresolved | Do not assume every number exists because the range was declared. |
CA-AI-KERNEL-015–024 |
Volume II | Exact article_id, heading or compact-kernel match |
published or unresolved | Do not treat used_by as a publication registry. |
CA-AI-KERNEL-025+ |
Extension registry | Exact canonical URL or amendment record | registered, planned or unresolved | Do not invent a title, order, URL or dependency. |
kernel_resolution:
input:
- requested_kernel_id
procedure:
- parse_numeric_suffix
- select_declared_source_volume
- search_for_exact_article_id
- search_for_exact_canonical_heading
- verify_version_and_status
- apply_kernel_000_amendments
- return_resolution_record
valid_results:
published:
condition: exact_record_found
registered:
condition: exact_extension_registry_record_found
planned:
condition: explicit_planned_record_found
unresolved:
condition: no_exact_record_found
mandatory_rule:
- references_do_not_prove_publication
- numbering_gaps_do_not_prove_deletion
- unresolved_items_must_not_be_inventedHow conflicts and future edits are decided
Apply Kernel 000 first.Load the current registry, precedence rules, patches, output contract and confidence requirements.
Load the relevant source volume.Use the source volume for the detailed concept, definition, law, example or machine-readable record.
Apply scoped amendments.A later active patch may supersede a named field, relationship, status, route or definition only within its declared scope.
Load extensions and cases.Control Tower, OS, crosswalk and case pages add application and evidence but do not silently replace the kernel.
Return conflicts visibly.When two active sources cannot be reconciled, state the conflict, lower confidence and escalate rather than choosing invisibly.
canonical_precedence:
1: CA-AI-KERNEL-000.active_amendments
2: CA-AI-KERNEL-000.runtime_contract
3: exact_kernel_record_in_source_volume
4: canonical_control_tower_or_os_extension
5: verified_case_or_sensor_record
6: provisional_ai_inference
conflict_rule:
metadata_routing_status_schema:
winner: kernel_000_or_later_active_amendment
concept_definition:
winner: exact_source_kernel
exception: amendment_explicitly_sets_supersedes_definition
live_fact:
winner: newest_verified_evidence
requirements:
- date
- source
- confidence
- review_status
unresolved_conflict:
action:
- preserve_both_claims
- state_uncertainty
- abstain_from_false_canonicalisation
- escalate_for_human_reviewDo not load the entire civilisation warehouse for every question
Select the narrowest profile that can answer the question safely. Expand only when a missing dependency, cross-zoom effect or uncertainty requires a larger field.
Minimum definition
Define the object without invoking the entire operating architecture.
- Kernel 000
- Volume I: minimum definition and adaptive-system model
- Root definition page
The execution sequence for every Civilisation Atlas reading
The runtime is deliberately ordered. AI must locate the object before judging its condition, expose its dependencies before proposing repair and distinguish evidence from inference at every stage.
Receive the question.Preserve the user’s object, time horizon, location, scale and requested outcome.
Select the load profile.Choose the smallest safe source stack and record why it was selected.
Resolve the object boundary.Identify whether the object is a person, family, institution, place, species, artefact, network, event, system or civilisation.
Locate it.Assign identity, time, place, zoom and depth before assigning capability or failure.
Read the civilisational coordinate.Assess capability stage, lifecycle phase, runtime phase, habitat independence and motion vector.
Expose the carrying floors.Map BaseFloor conditions, organs, infrastructure, memory, dependencies, buffers and bottlenecks.
Read information and wormholes.Identify source resolution, doorway, corridor, leverage, ceiling, internalisation, retention, exits and return.
Read control geometry.Locate sensing, decision authority, feedback, correction, incentives, accountability and ownership.
Diagnose state.Separate stable operation, drift, fracture, extraction, collapse, repair and regeneration.
Expand dependencies only as needed.Follow lower floors until reaching the minimum viable explanatory floor, then stop.
Generate routes.Provide upstream, downstream, historical, diagnostic, practical, repair and verification routes.
Return evidence and confidence.Distinguish sourced fact, framework classification, inference, uncertainty and matters requiring human escalation.
One envelope for every object, from a learner to a planet
Domain-specific modules may add fields, but they must not remove the shared Civilisation Atlas spine.
civilisation_atlas_output:
runtime_record:
wrapper_id: CA-AI-KERNEL-000
wrapper_version: 1.0
selected_profile:
loaded_sources:
applied_amendments:
analysis_timestamp:
object:
object_id:
canonical_name:
aliases:
object_class:
boundary:
included_components:
excluded_components:
location:
time:
place:
zoom:
ztime:
depth:
observer_position:
coordinate:
capability_stage:
lifecycle_phase:
runtime_phase:
habitat_independence:
motion_vector:
carrying_system:
BaseFloor:
active_organs:
infrastructure:
essential_flows:
memory_sources:
information_quality:
dependencies:
buffers:
bottlenecks:
wormhole_reading:
doorway:
gateway_conditions:
corridor:
payload:
leverage:
ceiling:
exit_topology:
capability_internal:
capability_borrowed:
retention:
return_path:
extraction_risk:
regeneration_potential:
control_geometry:
sensors:
decision_authority:
actuators:
feedback_loops:
incentives:
accountability:
ownership:
correction_capacity:
condition:
current_state:
principal_pressure:
fractures:
failure_propagation:
risks:
protected_invariant:
binding_constraint:
repair:
repair_order:
responsible_owner:
immediate_action:
medium_route:
long_route:
verification:
return_to_origin:
next_corridors:
epistemic_record:
sourced_facts:
framework_classifications:
inferences:
missing_evidence:
conflicts:
confidence:
abstentions:
human_escalations:
last_reviewed:
next_routes:
upstream:
downstream:
inward:
outward:
historical:
diagnostic:
practical:
repair:
verification:Future edits occur here as scoped patches
A patch must identify its target, exact scope, old rule, replacement rule, reason, evidence, effective date and rollback condition. It must never silently rewrite the historical record.
| Patch ID | Status | Target | Canonical effect |
|---|---|---|---|
CA-AI-PATCH-0001 |
active | Kernel authority | Kernel 000 is the canonical loader, registry, runtime and patch-precedence layer. |
CA-AI-PATCH-0002 |
active | Source-volume maintenance | Volumes I and II are stable conceptual sources and need not be rebuilt for operational changes. |
CA-AI-PATCH-0003 |
active | Kernel ID status | Every ID is resolved by exact evidence; references, ranges and dependency lists do not prove publication. |
CA-AI-PATCH-0004 |
active | Kernel 008 and 016–024 ambiguity | If an exact record is absent, status is unresolved; no title or function may be invented. |
CA-AI-PATCH-0005 |
active | Universal output | All major analyses must use the shared output envelope or explicitly state why a compact answer omits fields. |
CA-AI-PATCH-0006 |
active | Definition precedence | Concept definitions remain with their exact source kernel unless a patch explicitly supersedes that definition. |
CA-AI-PATCH-0007 |
active | Future maintenance | New routing, metadata, schemas, statuses and correction rules are appended here rather than inserted across both source volumes. |
Canonical patch record
amendment:
patch_id: CA-AI-PATCH-0008
version: 1.0
status: proposed
effective_date:
review_date:
target:
article_id:
field:
relationship:
source_url:
scope:
applies_to:
does_not_apply_to:
change:
previous_rule:
replacement_rule:
supersedes_definition: false
reason:
evidence:
consequences:
migration_instruction:
rollback_condition:
authority:
proposed_by:
approved_by:
confidence:
notes:Generate a correct AI loader instruction
This console does not call an external AI service. It constructs the canonical instruction that can be copied into an AI workflow, article-production runtime or editorial process.
Where every major function now points
Kernel 000 is the entry point. These routes supply the detailed definition, operating logic, stages, evidence, runtime, repair and specialist depth.
What the runtime must never flatten
Do not confuse access with mastery
Entry into a school, institution, network, technology or market does not prove traversal, internalisation, portability or resilience.
Do not confuse speed with direction
Path compression may accelerate capability, dependency, extraction or destruction. The exit and return path must be inspected.
Do not erase the lower floor
Upper-stage operation remains dependent on bodies, ecology, food, water, energy, care, language, infrastructure and institutional maintenance.
Do not flatten Zoom and depth
A close event and a civilisational pattern may both be true. Knowledge resolution is separate from the scale at which the object is observed.
Do not turn framework into fact
Separate externally sourced evidence from Civilisation Atlas classifications, interpretations and provisional AI inferences.
Do not erase dignity or agency
System-scale analysis must return to lived consequence, human choice, non-human life, stewardship and responsibility.
AI must lower confidence or abstain when the object boundary is unclear, evidence is missing, referenced kernels cannot be resolved, sources materially conflict, live conditions are stale or a classification would falsely convert a provisional reading into canonical truth.
The kernel is frozen until a case reveals a genuine failure
Run these cases after any major amendment. A failure means the wrapper or an extension needs repair. It does not automatically justify rewriting the source volumes.
Test 1 — Individual learner
Test 2 — Family
Test 3 — Institution
Test 4 — Country
Test 5 — Famine
Test 6 — Financial crisis
Test 7 — Historical collapse
Test 8 — Animal or plant species
Test 9 — Artificial intelligence
Test 10 — Future habitat
New concepts enter the core only when several materially different cases fail for the same structural reason. A single interesting example belongs first in a case, crosswalk or extension.
Small recurring checks instead of repeated full rewrites
On publication
Verify both source URLs, page title, Kernel 000 JSON manifest, copy controls and runtime console.
Monthly
Check broken canonical routes, newly published kernel IDs and unresolved registry items.
Quarterly
Run the conformance tests, review active patches and confirm that extensions have not drifted into competing definitions.
Annually
Issue a new wrapper version, archive superseded patches and publish a concise migration note.