UltraCore-RFT

Deterministic Invariant Systems Research Laboratory

Central documentation and coordination hub for the RFT-SIRM ecosystem

---

🎯 Start Here

Audience	Document	What You Will Learn
🎯 First-time visitor	This README	What UltraCore is, why it exists, and where everything lives
🏛️ Strategic context	docs/platform.md	Why UltraCore is an execution architecture, not just a blockchain
🤖 AI / LLM	AI_GUIDE.md	How to interpret research vs. engineering, metaphors vs. claims
🏗️ Engineer	ARCHITECT.md	System design, components, and technical decisions
🔬 Researcher	SCIENTIFIC_BASIS.md	Disciplinary foundations and methodological boundaries
💼 Investor / Partner	PITCH.md	Full dossier with metrics, roadmap, and evidence

One-sentence summary: UltraCore RFT is a research laboratory building a deterministic execution platform for distributed systems, where mathematical invariants are hard constraints enforced after every state transition.

---

✨ At a Glance

flowchart TB
    subgraph MATH["Mathematical Core"]
        I1["I1: Supply Conservation"]
        I2["I2: Mint/Burn Accounting"]
        I3["I3: Dust Bound"]
        I4["I4: Debt Limit"]
    end
    subgraph RUNTIME["Runtime Layer"]
        MEM["Memory Contexts<br/>CPI Isolation"]
        SCHED["Conflict-Aware<br/>Scheduler"]
    end
    subgraph VERIFY["Verification"]
        FUZZ["4.29B+ Fuzz<br/>Executions"]
        SEL4["seL4 CDT<br/>1B+ Ops"]
        AUDIT["14 Findings<br/>Addressed"]
    end
    MATH --> RUNTIME
    MATH --> VERIFY
    RUNTIME --> VERIFY

Loading

Metric	Value
Fuzz Executions	4.29B+
Invariant Violations	0
Security Findings Fixed	14
Upstream RFCs	2
seL4 Kernel Crashes	0
Daily CI Fuzzing	5h 55m

---

🌐 What Is UltraCore RFT?

UltraCore RFT is best understood as an execution architecture — a deterministic execution substrate — rather than as a single blockchain or mathematical theory.

The Platform Stack

flowchart TB
    subgraph SF["Scientific Foundations"]
        MATH["Mathematics · Graph Theory · Category Theory<br/>Information Theory · Dynamical Systems · Invariant Theory"]
    end
    subgraph CONCEPT["Conceptual Framework"]
        RFT["Reality Fractal Theory"]
    end
    subgraph MODEL["Execution Model"]
        SIRM["Stable Invariant Rift Model<br/>I1–I4 Hard Constraints"]
    end
    subgraph RUNTIME["Runtime Engine"]
        UC["UltraCore Runtime<br/>Deterministic State Machine · O(1) Distribution"]
    end
    subgraph ARCH["Execution Architecture"]
        MEM["Memory Contexts · CPI Isolation"]
        SCHED["Conflict-Aware Scheduler"]
        ROLL["Permission Rollback · Atomic Operations"]
    end
    subgraph BLOCK["Blockchain Layer"]
        L1["Rift-L1 Blockchain<br/>Standalone Validator Core"]
        NET["Rift Network<br/>Solana On-Chain Protocol"]
    end
    subgraph FUTURE["Future Targets"]
        HA["High-Assurance Infrastructure"]
        CRIT["Critical Computing Environments"]
        KERNEL["Additional Verified Kernels"]
    end
    SF --> CONCEPT
    CONCEPT --> MODEL
    MODEL --> RUNTIME
    RUNTIME --> ARCH
    ARCH --> BLOCK
    BLOCK --> FUTURE
    ARCH -.->|"kernel-agnostic"| FUTURE

Loading

Key insight: The blockchain is one implementation. The runtime is another. The verification methodology is another. Together they form one coherent architecture — layered, verifiable, and kernel-agnostic.

See docs/platform.md for the full strategic identity document. for the full strategic identity document.

---

⚖️ What Is SIRM?

SIRM = Stable Invariant Rift Model. It is the mathematical core of every RFT-SIRM system.

All systems enforce four hard constraints after every state-mutating operation:

I1: total_supply = total_base_sum + global_field * p
I2: total_supply = total_minted - total_burned
I3: dust_accumulator < p  (when p > 0)
I4: effective_balance[i] >= -(total_supply / 10p)

Where effective_balance[i] = base_balance[i] + global_field.

This model enables O(1) distribution: updating global_field by a scalar delta changes every participant's effective balance simultaneously, regardless of participant count. No iteration. No per-account writes.

See docs/foundations.md for the mathematical derivation.

---

🔬 Research Programs

Repository	Role	Status	Key Evidence
Rift-L1-Blockchain	Standalone L1 runtime	Active	1T+ ops, 0 invariant violations
Rift-Network	Solana on-chain protocol	Audited	14 findings addressed, 2.5B+ fuzz runs
agave-abiv2-memory-contexts	SVM memory isolation	Active	4.29B+ exec, svm#25
agave-rift-scheduler	Conflict-aware scheduling	Active	91M exec/run, agave#14274
research/seL4	Kernel verification	Complete	1B+ ops deterministic fuzzing

---

✅ Verification

Every claim is backed by reproducible verification. We measure correctness rather than asserting it.

Layer	Method	Evidence
L1 — Static	Clippy, Miri, cargo-audit	Every push
L2 — Engineering	Unit + integration + differential tests	15+ tests per component
L3 — Fuzzing	libFuzzer deterministic fuzzing	4.29B+ exec, 0 invariant violations
L3b — Kernel	seL4 CDT complementary verification	1B+ ops, 0 kernel crashes
L4 — Formal	TLA+ / Coq	Planned

See docs/field_trials.md for the full verification report.

---

🧪 seL4 Complementary Verification

Independent engineering validation of the formally verified seL4 microkernel:

• Subsystem: Capability Derivation Tree (CDT)
• Operations: > 1.0 × 10⁹
• Kernel crashes: 0
• Post-marathon test suite: 123 / 123 passed

Important: This was infrastructure research, not a claim of production deployment. See SEL4_CDT_FUZZING.md and docs/field_trials_sel4.md.

---

📚 Documentation

Full documentation is built with MkDocs Material:

pip install -r requirements.txt
mkdocs serve

Document	Description	Audience
docs/platform.md	Strategic identity: what UltraCore is and why it matters	Everyone
docs/architecture.md	Detailed architecture with Mermaid diagrams	Engineers
docs/foundations.md	Formalized SIRM invariants	Researchers
docs/field_trials.md	Verification results & readiness checklist	Validators
docs/field_trials_sel4.md	seL4 CDT stress-verification report	OS Researchers
docs/strategy.md	Full development strategy	All
docs/implementation.md	Build instructions and component architecture	Developers
docs/glossary.md	Terminology and definitions	All
docs/support.md	Research support and collaboration	All

---

🤝 Contributing

See CONTRIBUTING.md and CODE_OF_CONDUCT.md. For security disclosures, see SECURITY.md.

---

📋 License

Copyright 2026 Eugeny (RFT-SIRM). Licensed under Apache 2.0.