Overview

ICore (InitialCore) is the constitutional computing platform originated by Sir Collins (access1@tutamail.com). It is a layered architecture where every component answers six constitutional questions: What exists? Who acts? What relates? What constrains? What transforms? What verifies?

ICore is not an operating system — it is a constitutional computing platform. The distinction matters: ICore defines the principles and structure that govern computational sovereignty, not the implementation of a specific runtime.

Core Principles

• Sovereignty: No external dependencies, no cloud trust required
• Offline-First: Every PWA works without network connectivity
• Constitutional: Every layer is defined by formal axioms and primitives
• Verifiable: 50+ conformance tests across all domains
• Event-Driven: CustomEvent architecture for inter-component communication

Platform Domains

Quick Start

1. Install a PWA — Visit any domain and tap "Install" to add to your home screen
2. Run Conformance Tests — Each domain has a built-in conformance test suite
3. Create Artifacts — Use USDS to create, sign, and distribute constitutional packages
4. Verify — Use the Verifier to check trust chains and conformance claims

Constitutional Stack

The ICore constitutional stack is a layered architecture where each layer depends only on layers below it. Dependencies flow downward — never upward.

┌─────────────────────────────────────────────────┐
│  Layer 6.1  UCA (Adapters)        🔌           │
│  Layer 6    USR (Runtime)         ⚡           │
│  Layer 5.5  UWA + UCN            🧩🌐         │
│  Layer 5    Reference Systems                  │
│  Layer 4    UCE · UCM · UCL · UVS              │
│  Layer 3    Reference Sciences                 │
│  Layer 2    USC (Constitution Language)         │
│  Layer 1    USCP (Core Primitives)              │
│  Layer 0    ICore (Constitution)                │
└─────────────────────────────────────────────────┘

Layer 0 — ICore (Constitution)

The root of the entire platform. ICore defines the constitutional principles that all layers must uphold. It is the source of authority — everything traces to Layer 0.

Layer 1 — USCP (Core Primitives)

The six core primitives that answer the six constitutional questions:

Layer 2 — USC (Constitution Language)

The formal language for expressing constitutional rules. USC provides the syntax and semantics for writing axioms, constraints, and assertions.

Layer 3 — Reference Sciences

Mathematics, logic, information theory, and cryptography provide the theoretical foundation.

Layer 4 — UCE · UCM · UCL · UVS

Upper-level constructs: Universal Constitutional Execution (UCE), Universal Constitutional Models (UCM), Universal Constitutional Languages (UCL), and Universal Verification Sciences (UVS).

Layer 5 — Reference Systems

Communication, data, and computation systems that provide the substrate for constitutional operations.

Layer 5.5 — UWA + UCN

UWA (Universal Workspace Adapter) defines workspace components and their lifecycle. UCN (Universal Constitutional Networking) defines how constitutional nodes communicate and synchronize.

Layer 6 — USR + UCA

USR (Universal Sovereign Runtime) is the execution layer — identity, execution, constraints, isolation, attestation, and orchestration. UCA (Universal Constitutional Adapters) bridges constitutional boundaries to external systems.

USR — Universal Sovereign Runtime

Purpose: Execute constitutional operations under sovereign authority.

Live: usr.initialcore.net

Engines

• Identity Engine (C1) — declare(), register(), verify()
• Execution Engine (C2) — execute(), getHistory()
• Constraints Engine (C3) — enforce(), test()
• Isolation Engine (C4) — requestCapability(), revokeCapability(), checkCapability()
• Attestation Engine (C5) — attest(), verify(), verifyChain()
• Orchestration Engine (C6) — start(), suspend(), resume(), terminate()

Conformance Tests

USR-01 through USR-15 (15 tests, Critical/Major/Minor categories)

UWA — Universal Workspace Adapter

Purpose: Define workspace components and their lifecycle.

Live: uwa.initialcore.net

Engines

• Component Engine — create(), declare(), validate(), initialize(), start(), suspend(), resume(), terminate()
• Event Engine — emit(), consume()
• Execution Engine — execute()
• Composition Engine — addEdge(), getChildren(), validate()
• Workspace Runtime — createComponent(), executeEvent(), compose()

Conformance Tests

UWA-01 through UWA-10 (10 tests)

UCN — Universal Constitutional Networking

Purpose: Define how constitutional nodes communicate and synchronize.

Live: ucn.initialcore.net

Engines

• Node Engine — createNode(), extendNetwork(), activateNetwork(), revoke()
• Discovery Engine — advertise(), query()
• Communication Engine — createEvent(), verifyEvent()
• Sync Engine — initState(), createDelta(), applyDelta()
• Trust Engine — addAnchor(), assertTrust(), revokeTrust()
• Network Runtime — joinNetwork(), getStatus()

Conformance Tests

UCN-01 through UCN-13 (13 tests)

UCA — Universal Constitutional Adapters

Purpose: Bridge constitutional boundaries to external systems while maintaining sovereignty.

Live: uca.initialcore.net

Engines

• Adapter Engine — register(), unregister(), replace()
• Naming Engine — registerMapping(), resolve(), verify()
• Serialization Engine — serialize(), deserialize(), verifyRoundtrip()
• Execution Adapter — execute(), sandboxCheck()
• Storage Adapter — store(), retrieve(), verifyIntegrity()
• Communication Adapter — send(), verifySource()
• Boundary Runtime — getStatus()

Conformance Tests

UCA-01 through UCA-12 (12 tests)

USDS — Sovereign Distribution System

Purpose: Distribute constitutional software with verified authenticity, integrity, and provenance.

Live: usds.initialcore.net

Engines

• Package Engine — create(), extract()
• Signing Engine — sign(), verify()
• Distribution Engine — transfer(), track()
• Verification Engine — verify(), verifyChain()

Conformance Tests

ICS v0.2.0 — The ICore Conformance Suite validates internal consistency across all domains.

Test Summary

Weak vs Strong Claims

• Weak claim: All 57 tests pass (63% with v0.2.0 differentiating)
• Strong claim: 54/57 real validation tests pass (94.7% — engine differentiates)

API Reference

Full method documentation for all 28 engines across 5 domains.

→ View API Reference at api.initialcore.net