Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
79 changes: 77 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,87 @@
## THE PROOF IS MATHEMATICAL
### TIME WILL TELL

---

## AIΩN Foundations

**A formal framework for deterministic, history-native computation.**

[![Paper I](https://img.shields.io/badge/Paper_I-Published-brightgreen)](https://zenodo.org/...) [![Paper II](https://img.shields.io/badge/Paper_II-Published-brightgreen)](https://zenodo.org/...) [![Paper III](https://img.shields.io/badge/Paper_III-Published-brightgreen)](https://zenodo.org/...) [![Paper IV](https://img.shields.io/badge/Paper_IV-Published-brightgreen)](https://zenodo.org/...) [![Paper V](https://img.shields.io/badge/Paper_V-Draft-yellow)]() [![Paper VI](https://img.shields.io/badge/Paper_VI-Draft-yellow)]()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Fix empty link targets for draft papers.

Lines with Papers V and VI have empty brackets ](), creating broken links that violate MD042. The link targets must be populated with actual Zenodo URLs or conditionally removed until publication.

🔎 Proposed fix
-[![Paper V](https://img.shields.io/badge/Paper_V-Draft-yellow)]() [![Paper VI](https://img.shields.io/badge/Paper_VI-Draft-yellow)]()
+[![Paper V](https://img.shields.io/badge/Paper_V-Draft-yellow)](https://zenodo.org/...) [![Paper VI](https://img.shields.io/badge/Paper_VI-Draft-yellow)](https://zenodo.org/...)

Or, if URLs are unavailable, remove the hyperlink wrapping:

-[![Paper V](https://img.shields.io/badge/Paper_V-Draft-yellow)]() [![Paper VI](https://img.shields.io/badge/Paper_VI-Draft-yellow)]()
+![Paper V](https://img.shields.io/badge/Paper_V-Draft-yellow) ![Paper VI](https://img.shields.io/badge/Paper_VI-Draft-yellow)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
[![Paper I](https://img.shields.io/badge/Paper_I-Published-brightgreen)](https://zenodo.org/...) [![Paper II](https://img.shields.io/badge/Paper_II-Published-brightgreen)](https://zenodo.org/...) [![Paper III](https://img.shields.io/badge/Paper_III-Published-brightgreen)](https://zenodo.org/...) [![Paper IV](https://img.shields.io/badge/Paper_IV-Published-brightgreen)](https://zenodo.org/...) [![Paper V](https://img.shields.io/badge/Paper_V-Draft-yellow)]() [![Paper VI](https://img.shields.io/badge/Paper_VI-Draft-yellow)]()
[![Paper I](https://img.shields.io/badge/Paper_I-Published-brightgreen)](https://zenodo.org/...) [![Paper II](https://img.shields.io/badge/Paper_II-Published-brightgreen)](https://zenodo.org/...) [![Paper III](https://img.shields.io/badge/Paper_III-Published-brightgreen)](https://zenodo.org/...) [![Paper IV](https://img.shields.io/badge/Paper_IV-Published-brightgreen)](https://zenodo.org/...) [![Paper V](https://img.shields.io/badge/Paper_V-Draft-yellow)](https://zenodo.org/...) [![Paper VI](https://img.shields.io/badge/Paper_VI-Draft-yellow)](https://zenodo.org/...)
Suggested change
[![Paper I](https://img.shields.io/badge/Paper_I-Published-brightgreen)](https://zenodo.org/...) [![Paper II](https://img.shields.io/badge/Paper_II-Published-brightgreen)](https://zenodo.org/...) [![Paper III](https://img.shields.io/badge/Paper_III-Published-brightgreen)](https://zenodo.org/...) [![Paper IV](https://img.shields.io/badge/Paper_IV-Published-brightgreen)](https://zenodo.org/...) [![Paper V](https://img.shields.io/badge/Paper_V-Draft-yellow)]() [![Paper VI](https://img.shields.io/badge/Paper_VI-Draft-yellow)]()
[![Paper I](https://img.shields.io/badge/Paper_I-Published-brightgreen)](https://zenodo.org/...) [![Paper II](https://img.shields.io/badge/Paper_II-Published-brightgreen)](https://zenodo.org/...) [![Paper III](https://img.shields.io/badge/Paper_III-Published-brightgreen)](https://zenodo.org/...) [![Paper IV](https://img.shields.io/badge/Paper_IV-Published-brightgreen)](https://zenodo.org/...) ![Paper V](https://img.shields.io/badge/Paper_V-Draft-yellow) ![Paper VI](https://img.shields.io/badge/Paper_VI-Draft-yellow)
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

13-13: No empty links

(MD042, no-empty-links)


13-13: No empty links

(MD042, no-empty-links)

🤖 Prompt for AI Agents
In README.md around line 13, the badges for Paper V and Paper VI contain empty
link targets `]()`, which causes broken links and MD042 failures; fix by either
replacing the empty parentheses with the correct Zenodo (or other) publication
URLs for Paper V and Paper VI, or remove the hyperlink wrapper entirely and
leave the plain badge text until the URLs are available (i.e., change `[![Paper
V](...)]()` to `[![Paper V](...)](https://zenodo.org/...)` or to `![Paper
V](...)` and do the same for Paper VI).


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

cat -n README.md | head -20

Repository: flyingrobots/aion

Length of output: 1384


Replace placeholder Zenodo URLs in badge links.

The badge links on line 13 reference https://zenodo.org/... as placeholders, leaving Papers I–IV inaccessible. Replace with actual Zenodo DOI URLs for each paper.

-[![Paper I](https://img.shields.io/badge/Paper_I-Published-brightgreen)](https://zenodo.org/...) [![Paper II](https://img.shields.io/badge/Paper_II-Published-brightgreen)](https://zenodo.org/...) [![Paper III](https://img.shields.io/badge/Paper_III-Published-brightgreen)](https://zenodo.org/...) [![Paper IV](https://img.shields.io/badge/Paper_IV-Published-brightgreen)](https://zenodo.org/...)
+[![Paper I](https://img.shields.io/badge/Paper_I-Published-brightgreen)](<ZENODO_URL_I>) [![Paper II](https://img.shields.io/badge/Paper_II-Published-brightgreen)](<ZENODO_URL_II>) [![Paper III](https://img.shields.io/badge/Paper_III-Published-brightgreen)](<ZENODO_URL_III>) [![Paper IV](https://img.shields.io/badge/Paper_IV-Published-brightgreen)](<ZENODO_URL_IV>)

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In README.md around line 14, the badge links use placeholder Zenodo URLs
(https://zenodo.org/...) so Papers I–IV are inaccessible; replace each
placeholder with the actual Zenodo DOI URL for the corresponding paper (use the
full DOI-based Zenodo link format, e.g., https://zenodo.org/record/<record-id>
or the DOI URL https://doi.org/<doi>), updating each badge href to point to the
correct paper and verify the visible badge image URLs remain unchanged.

---

## Overview

This repository collects the **AIΩN Foundations Series**, a sequence of papers that establish a mathematical and architectural foundation for deterministic computation. The series develops, from first principles, a framework in which history is the primary representational artefact and state is derived as a materialised view.

We address a class of problems endemic to contemporary software systems: irreproducible builds, nondeterministic concurrency failures, and the absence of verifiable provenance for automated transformations. Our approach demonstrates that these pathologies are not inevitable features of complex systems, but consequences of an architectural decision—storing snapshots rather than transformations—that can be revisited.

The series proceeds incrementally. Each paper assumes familiarity with its predecessors but remains self-contained in its contributions. Papers I–IV establish the theoretical substrate; Papers V–VI extend the framework to ethical considerations and system architecture.

---

## Papers

| # | Title | Status | Contribution |
|---|-------|--------|--------------|
| I | **WARP Graphs** | Published | Introduces recursive meta-graphs as the foundational substrate for causal, nested computation. |
| II | **Computational Holography** | Published | Establishes how local graph structure encodes and reconstructs global semantic content. |
| III | **Observer Geometry** | Published | Formalises multiple observer perspectives over a single causal structure. |
| IV | **Echo Engine** | Published | Presents a deterministic scheduling algorithm based on Double-Pushout graph rewriting. |
| V | **Ethics & Sovereignty** | Draft | Addresses provenance, accountability, and the rights of computational agents. |
| VI | **Architecture & Operating System** | Draft | Specifies JITOS, a causal operating system that instantiates the preceding theory. |

---

## Related Work

The following repositories implement or extend concepts from the Foundations Series:

| Repository | Description |
|------------|-------------|
| [echo-engine](https://github.com/...) | Reference implementation of the DPO rewrite scheduler (Paper IV). |
| [jitos](https://github.com/...) | Userland kernel daemon for the causal operating system (Paper VI). |
| [wesley](https://github.com/...) | GraphQL-to-PostgreSQL compiler with formal verification. |
| [nine-lives](https://github.com/...) | Fractal supervision model for asynchronous operations. |
| [gatos](https://github.com/...) | Git As The Operating Surface—Git as programmable computational substrate. |
Comment on lines +46 to +50
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

# First, check if README.md exists and read lines around 46-50
if [ -f "README.md" ]; then
  echo "=== README.md exists. Reading lines 40-55 ===" 
  sed -n '40,55p' README.md
else
  echo "README.md not found"
fi

Repository: flyingrobots/aion

Length of output: 813


🏁 Script executed:

# Search for each repository to see if they are real projects
for repo in "echo-engine" "jitos" "wesley" "nine-lives" "gatos"; do
  echo "=== Searching for: $repo ==="
  # Use ripgrep to search for any references in the repo itself
  rg "$repo" --type md --type txt -i 2>/dev/null | head -20
done

Repository: flyingrobots/aion

Length of output: 1176


🌐 Web query:

Search for "echo-engine github repository DPO rewrite scheduler"

💡 Result:

I searched for "echo-engine github repository DPO rewrite scheduler" and did not find a single repository matching that exact phrase. Relevant results I found:

  • Spinnaker "echo" (eventing / CRON scheduler) repository — contains scheduler/compensation (missed CRON) details. (github.com)
  • Labstack "echo" (Go web framework) documentation (rewrite middleware). (github.com)
  • A DPO (Direct Preference Optimization) reference implementation repository (unrelated to "echo-engine"). (github.com)

If you want, I can (a) broaden the search terms, (b) look for a specific organization/user's "echo-engine" repo, or (c) search code for occurrences of "DPO" or "rewrite scheduler" across GitHub. Which would you like?

Citations:


🌐 Web query:

Search for "jitos github userland kernel daemon causal operating system"

💡 Result:

I searched for "jitos github userland kernel daemon causal operating system" and found results in two areas — Jito (blockchain) projects on GitHub and several userland/kernel OS projects (library OS, unikernels, userland daemons). Key matches:

  • Jito (blockchain / Jito Labs) GitHub organization and SDKs (TypeScript, Python, JS RPC) — not an OS but related to Solana MEV tooling. [1][2][3]
  • JunctionOS — a library‑OS / userland-kernel‑bypass datacenter OS prototype (runs much OS functionality in userspace). [4]
  • Other userland/unikernel OS projects and related research (NodeOS, IncludeOS, DiOS, LibrettOS, Hermit). [5][6][7][8][9]

Sources:

  1. jito-labs organization & jito-ts / jito-js-rpc / jito-python repos. [https://github.com/jito-labs] [1]
  2. jito-js-rpc repo (Jito JSON‑RPC Typescript SDK). [https://github.com/jito-labs/jito-js-rpc] [2]
  3. jito‑ts (Jito Typescript SDK). [https://github.com/jito-labs/jito-ts] [3]
  4. JunctionOS (library OS / userland kernel‑bypass project). [https://github.com/JunctionOS/junction] [4]
  5. NodeOS (Node.js userspace OS). [https://github.com/NodeOS/NodeOS] [5]
  6. IncludeOS (unikernel). [https://en.wikipedia.org/wiki/IncludeOS] [6]
  7. DiOS (reproducible POSIX user‑mode kernel research). [https://arxiv.org/abs/1907.03356] [7]
  8. LibrettOS research paper (multiserver/library OS). [https://arxiv.org/abs/2002.08928] [8]
  9. Hermit OS (Rust unikernel project). [https://github.com/hermit-os] [9]

Would you like me to open any of these repos/papers and extract specific files or details?


🌐 Web query:

Search for "wesley github GraphQL PostgreSQL compiler"

💡 Result:

I searched for "wesley github GraphQL PostgreSQL compiler". I found a blog/dev post describing a project called "Wesley" that compiles an annotated GraphQL schema into PostgreSQL DDL, TypeScript types, migrations, tests, and RLS policies. [1]

I could not find an official GitHub repository for "Wesley" in the search results (no matching GitHub repo or org surfaced). If you want, I can (a) search GitHub specifically again with broader filters, (b) try to locate the author/website for the Wesley project, or (c search for alternative tools that compile GraphQL ↔ PostgreSQL (e.g., PostGraphile, Hasura, pg_graphql). Which would you prefer? [1][2][3]

Sources:

  • "What if GraphQL Was Your Database?" (DEV article describing Wesley). [1]
  • Postgres ↔ GraphQL projects (examples): Supabase pg_graphql. [2]
  • PostGraphile (Graphile) overview. [3]

🌐 Web query:

Search for "nine-lives github fractal supervision"

💡 Result:

I searched for "nine-lives github fractal supervision" but found no repository or project matching that exact phrase. Closely related results include general GitHub topic pages for fractals and supervision, and several fractal / fractal‑pretraining projects (examples below):

  • GitHub topic pages for weak‑supervision and fractal/fractal‑dimension. [1][2]
  • FractalNet and related fractal deep‑learning projects (FractalNet repos). [3]
  • "Improving Fractal Pre‑training" project and code. [4]

If you want, I can:

  • broaden the search (e.g., drop or change one of the terms),
  • search GitHub specifically for repositories named "nine-lives",
  • or look for academic/industry projects combining "fractal" with "weak supervision" or "supervision". Which would you prefer?

🌐 Web query:

Search for "gatos github Git As The Operating Surface"

💡 Result:

I searched — top results for "gatos github Git As The Operating Surface" show several unrelated "gato"/"gatos" GitHub projects, e.g.:

  • Gato (GitHub Attack Toolkit) — praetorian-inc/gato (GitHub Actions enumeration/attack tool). [1]
  • Gato (DeepMind model reimplementations) — several community repos (example: OrigamiDream/gato). [2]
  • Gato variants/forks (e.g., AdnaneKhan/gato-x). [3]

Do you want me to open any of these or continue searching for a specific item titled "Git As The Operating Surface"?

Sources:
[1] praetorian-inc/gato (GitHub).
[2] OrigamiDream/gato (GitHub).
[3] AdnaneKhan/gato-x (GitHub).


Remove or complete the Related Work table entries—no repositories found on GitHub.

The five repository links use placeholder URLs and—after investigation—none of the referenced projects (echo-engine, jitos, wesley, nine-lives, gatos) exist as public GitHub repositories. Either provide the actual repository URLs if these projects are published, or update each table entry to explicitly state the current status (e.g., "not yet published", "draft", "forthcoming"). The README already notes that "The AIΩN Runtime and JITOS software projects... are not part of this repository"; extend this clarity to all five entries so readers understand whether these are aspirational future works or simply external references yet to be shared.

🤖 Prompt for AI Agents
In README.md around lines 46 to 50, the Related Work table contains placeholder
GitHub URLs for echo-engine, jitos, wesley, nine-lives, and gatos that do not
exist; replace each placeholder link with either the actual repository URL if
the project is published, or update the table text for each entry to a clear
status label such as "not yet published", "draft", or "forthcoming" (and
optionally add a parenthetical note if the project is private or part of another
repo), ensuring the README explicitly states the current availability for each
project just like the existing note about AIΩN Runtime and JITOS.


---

## Central Thesis

We contend that the fundamental unit of computational storage should be the *transformation*, not the *state*. When transformations are first-class and immutable, deterministic replay, time-travel debugging, and structural provenance emerge as natural consequences rather than heroic engineering efforts.

The AIΩN Foundations Series develops the formal machinery required to make this inversion rigorous and the architectural patterns required to make it practical.

---

## Citation

```bibtex
@misc{ross2025aion,
author = {Ross, James},
title = {The {AIΩN} Foundations Series},
year = {2025},
publisher = {Zenodo},
note = {Papers I--VI}
}
```

## License

This repository contains only the CΩMPUTER manuscript, figures, compiled PDF, and documentation. These materials are © 2025 James Ross and licensed under Creative Commons Attribution 4.0 (CC BY 4.0); see LICENSE for details.
These materials are © 2025 James Ross and licensed under Creative Commons Attribution 4.0 (CC BY 4.0); see LICENSE for details.

The AIΩN Runtime and JITOS software projects referenced by the paper are not part of this repository. Those separate codebases are licensed under the Apache License, Version 2.0 (see their own repositories or Apache License 2.0).

### More on AIΩN

For updates, see the main [AIΩN](github.com/flyingrobots/aion) repository.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Fix malformed GitHub URL—missing protocol.

The link to the main AIΩN repository is missing the https:// protocol, resulting in github.com/flyingrobots/aion instead of a valid URL.

🔎 Proposed fix
-For updates, see the main [AIΩN](github.com/flyingrobots/aion) repository.
+For updates, see the main [AIΩN](https://github.com/flyingrobots/aion) repository.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
For updates, see the main [AIΩN](github.com/flyingrobots/aion) repository.
For updates, see the main [AIΩN](https://github.com/flyingrobots/aion) repository.
🤖 Prompt for AI Agents
In README.md around line 82 the GitHub link is malformed (missing protocol);
update the markdown link target to include the full URL (e.g. prepend
"https://") so it becomes a valid https://github.com/flyingrobots/aion link.


AIΩN Foundations Series © 2025 by James Ross is licensed under CC BY 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by/4.0/](https://creativecommons.org/licenses/by/4.0/)

_NOTE:_ If you do not wish to use MIND-UCAL, you may freely use all theory, math, and documentation under Apache 2.0 or CC BY 4.0, alone. No part of this repository requires adopting MIND-UCAL.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Introduce and fix emphasis style; clarify undefined MIND-UCAL reference.

Line 86 uses underscore emphasis _NOTE:_ instead of the project-standard asterisk (MD049). Additionally, MIND-UCAL is referenced without prior definition or context, creating a confusing reference to an undefined system or license variant. Either define the acronym or remove/clarify the reference.

🔎 Proposed fixes

Change underscore emphasis to asterisk and clarify MIND-UCAL:

-_NOTE:_ If you do not wish to use MIND-UCAL, you may freely use all theory, math, and documentation under Apache 2.0 or CC BY 4.0, alone. No part of this repository requires adopting MIND-UCAL.
+*NOTE:* If you do not wish to use MIND-UCAL, you may freely use all theory, math, and documentation under Apache 2.0 or CC BY 4.0, alone. No part of this repository requires adopting MIND-UCAL.

Then, provide a footnote or glossary entry defining MIND-UCAL, or if it is obsolete/unrelated, remove the reference entirely.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
_NOTE:_ If you do not wish to use MIND-UCAL, you may freely use all theory, math, and documentation under Apache 2.0 or CC BY 4.0, alone. No part of this repository requires adopting MIND-UCAL.
*NOTE:* If you do not wish to use MIND-UCAL, you may freely use all theory, math, and documentation under Apache 2.0 or CC BY 4.0, alone. No part of this repository requires adopting MIND-UCAL.
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

86-86: Emphasis style
Expected: asterisk; Actual: underscore

(MD049, emphasis-style)


86-86: Emphasis style
Expected: asterisk; Actual: underscore

(MD049, emphasis-style)

🤖 Prompt for AI Agents
In README.md around line 86, change the underscore emphasis `_NOTE:_` to the
project-standard asterisk emphasis `*NOTE:*` to satisfy MD049, and then either
add a short definition or parenthetical context for “MIND-UCAL” on first mention
(e.g., “MIND-UCAL (define what it is — project/tool/license)”) or remove the
term entirely if it is obsolete; if you add the definition, also create a
footnote or glossary entry later in the README and link to it so the acronym is
no longer undefined.


---

*Pronounced AYE-on, ryhmes with lion*
*Pronounced EYE-on, ryhmes with "lion"*
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix emphasis-as-heading and correct typo.

Line 90 uses emphasis syntax *...* where a proper heading or plain text is intended (MD036). Additionally, "ryhmes" is a typo; it should be "rhymes".

🔎 Proposed fix
-*Pronounced EYE-on, ryhmes with "lion"*
+Pronounced EYE-on, rhymes with "lion".

Alternatively, if a stylized closing line is desired, use a proper emphasis pattern without triggering the heading rule:

-*Pronounced EYE-on, ryhmes with "lion"*
+*Pronounced EYE-on, rhymes with "lion".*
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
*Pronounced EYE-on, ryhmes with "lion"*
Pronounced EYE-on, rhymes with "lion".
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

90-90: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🤖 Prompt for AI Agents
In README.md around line 90, the line currently uses emphasis asterisks which
are being interpreted as a heading and contains a typo ("ryhmes"); replace the
emphasis markup with either a proper Markdown heading or plain text (remove the
surrounding asterisks) and correct the typo to "rhymes" so the line reads e.g.
Pronounced EYE-on, rhymes with "lion".

Loading