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
13 changes: 10 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,13 @@

**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)]()
[![Paper I](https://img.shields.io/badge/Paper_I-Published-brightgreen)](https://doi.org/10.5281/zenodo.17908005)
[![Paper II](https://img.shields.io/badge/Paper_II-Published-brightgreen)](https://doi.org/10.5281/zenodo.17934512)
[![Paper III](https://img.shields.io/badge/Paper_III-Published-brightgreen)](https://doi.org/10.5281/zenodo.17963669)
Comment on lines +13 to +15
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

Remove trailing spaces from badge lines.

Lines 13–15 and 18 have trailing whitespace at the end of the line, which violates the markdown linting rule MD009. Trailing spaces should be removed.

🔎 Proposed fix
-[![Paper I](https://img.shields.io/badge/Paper_I-Published-brightgreen)](https://doi.org/10.5281/zenodo.17908005) 
+[![Paper I](https://img.shields.io/badge/Paper_I-Published-brightgreen)](https://doi.org/10.5281/zenodo.17908005)
-[![Paper II](https://img.shields.io/badge/Paper_II-Published-brightgreen)](https://doi.org/10.5281/zenodo.17934512) 
+[![Paper II](https://img.shields.io/badge/Paper_II-Published-brightgreen)](https://doi.org/10.5281/zenodo.17934512)
-[![Paper III](https://img.shields.io/badge/Paper_III-Published-brightgreen)](https://doi.org/10.5281/zenodo.17963669) 
+[![Paper III](https://img.shields.io/badge/Paper_III-Published-brightgreen)](https://doi.org/10.5281/zenodo.17963669)
-[![Paper VI](https://img.shields.io/badge/Paper_V-Draft-yellow)]() 
+[![Paper VI](https://img.shields.io/badge/Paper_V-Draft-yellow)]()

Also applies to: 18-18

🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

13-13: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)


14-14: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)


15-15: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)

🤖 Prompt for AI Agents
In README.md around lines 13–15 and line 18, the badge lines contain trailing
whitespace which violates MD009; remove the trailing spaces at the end of each
affected line (13, 14, 15, and 18) so the lines end immediately after the
closing parenthesis, then save the file to ensure no other trailing spaces
remain (run a linter or trim-whitespace tool if desired).

[![Paper IV](https://img.shields.io/badge/Paper_IV-Published-brightgreen)](https://doi.org/10.5281/zenodo.18038297)
[![Paper V](https://img.shields.io/badge/Paper_IV-Published-brightgreen)](https://doi.org/10.5281/zenodo.18146884)
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 badge label mismatch on Paper V.

Line 17 has a critical labeling error: the badge label reads Paper_IV but should be Paper_V to match the paper number. This is confusing and inconsistent.

🔎 Proposed fix
-[![Paper V](https://img.shields.io/badge/Paper_IV-Published-brightgreen)](https://doi.org/10.5281/zenodo.18146884)
+[![Paper V](https://img.shields.io/badge/Paper_V-Published-brightgreen)](https://doi.org/10.5281/zenodo.18146884)
📝 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 V](https://img.shields.io/badge/Paper_IV-Published-brightgreen)](https://doi.org/10.5281/zenodo.18146884)
[![Paper V](https://img.shields.io/badge/Paper_V-Published-brightgreen)](https://doi.org/10.5281/zenodo.18146884)
🤖 Prompt for AI Agents
In README.md around line 17, the badge label text incorrectly reads "Paper_IV"
while the link/title refers to Paper V; update the badge label to "Paper_V" so
the visible label matches the paper number (e.g., change the badge alt/text
segment to Paper_V) and verify the surrounding markdown remains intact.

[![Paper VI](https://img.shields.io/badge/Paper_V-Draft-yellow)]()
[![Paper VII](https://img.shields.io/badge/Paper_VI-Draft-yellow)]()
Comment on lines +18 to +19
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:

# Check the README.md file, especially around lines 18-19
head -30 README.md | cat -n

Repository: flyingrobots/aion

Length of output: 1579


🏁 Script executed:

# Also check if there are any other references to these papers or DOI links
rg -i "paper|doi|zenodo" README.md

Repository: flyingrobots/aion

Length of output: 4259


🏁 Script executed:

# Check the exact lines 18-19 with context
sed -n '15,25p' README.md | cat -n

Repository: flyingrobots/aion

Length of output: 823


Fix broken badge labels AND remove empty links for draft papers.

Lines 18–19 have empty href links [](), which are non-functional. More critically, lines 17–19 have mismatched badge labels: Paper V's badge says "Paper_IV", Paper VI's badge says "Paper_V", and Paper VII's badge says "Paper_VI".

For Papers VI–VII (marked Draft and lacking DOI assignments), either remove the empty link syntax entirely or populate with valid Zenodo DOIs once available. Fix all badge label text to match their actual paper numbers.

🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

18-18: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)


18-18: No empty links

(MD042, no-empty-links)


19-19: No empty links

(MD042, no-empty-links)

🤖 Prompt for AI Agents
In README.md around lines 17 to 19, the badge links are empty and the badge
labels are mismatched; fix the badge label text so each badge matches its actual
paper number (Paper V, Paper VI, Paper VII) and remove the empty link syntax for
draft papers (or replace with valid Zenodo DOI links when available) so badges
either render without an empty href or point to the correct DOI; update the
three lines so labels read the correct paper numbers and ensure no "[]()" empty
links remain for drafts.


---

Expand Down Expand Up @@ -44,8 +50,9 @@ The **AIΩN Foundations Series** develops the formal machinery and architectural
| II | **Canonical State Evolution and Deterministic Worldlines** | Published | Paper II equips WARP graphs with a deterministic concurrent operational semantics—based on double-pushout rewriting in an adhesive category of typed open graphs—proving that any scheduler-admissible batch of rewrites commits to the same successor state regardless of internal serialisation order, thereby grounding replay and provenance in a single tick-confluent execution model. |
| III | **Computational Holography & Provenance Payloads** | Published | Paper III formalises computational holography—proving that a deterministic WARP worldline's entire interior derivation is uniquely recoverable from a compact boundary encoding (initial state plus ordered tick patches), then develops practical machinery for slicing, branching, and multi-tick compression via wormholes. |
| IV | **Rulial Distance & Observer Geometry** | Published | Paper IV formalises observer geometry—modelling observers as resource-bounded functors from rewriting histories to trace spaces, introducing a rulial distance that measures the MDL-regularised cost of translating between descriptions, and grounding the Chronos–Kairos–Aion time triad—thereby providing a computable notion of frame separation that clarifies abstraction, auditability, and explainability trade-offs. |
| V | **Ethics & Sovereignty** | Draft | Addresses provenance, accountability, computational agency, and fork/termination responsibility. _COMING SOON_ |
| VI | **Architecture & Operating System** | Draft | Specifies JITOS, a causal operating system defining the execution model, observer interface, and kernel semantics implied by the theory. _COMING SOON_ |
| V | **Emergent Dynamics from Deterministic Rewrite Systems** | Published | By equipping deterministic rewrite histories with a local action functional, this paper establishes that quantum interference, unitary evolution, and the thermodynamic arrow of time emerge naturally as artifacts of observer-induced coarse-graining rather than as intrinsic physical postulates. |
| VI | **Ethics & Sovereignty** | Draft | Addresses provenance, accountability, computational agency, and fork/termination responsibility. _COMING SOON_ |
| VII | **Architecture & Operating System** | Draft | Specifies JITOS, a causal operating system defining the execution model, observer interface, and kernel semantics implied by the theory. _COMING SOON_ |
Comment on lines +54 to +55
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

Standardize emphasis markers to asterisks, not underscores.

Lines 54–55 use underscore delimiters for emphasis (_COMING SOON_) but the markdown linting rule MD049 requires asterisks (*COMING SOON*) for consistency.

🔎 Proposed fix
-| VI | **Ethics & Sovereignty** | Draft | Addresses provenance, accountability, computational agency, and fork/termination responsibility. _COMING SOON_ |
+| VI | **Ethics & Sovereignty** | Draft | Addresses provenance, accountability, computational agency, and fork/termination responsibility. *COMING SOON* |
-| VII | **Architecture & Operating System** | Draft | Specifies JITOS, a causal operating system defining the execution model, observer interface, and kernel semantics implied by the theory. _COMING SOON_ |
+| VII | **Architecture & Operating System** | Draft | Specifies JITOS, a causal operating system defining the execution model, observer interface, and kernel semantics implied by the theory. *COMING SOON* |
📝 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
| VI | **Ethics & Sovereignty** | Draft | Addresses provenance, accountability, computational agency, and fork/termination responsibility. _COMING SOON_ |
| VII | **Architecture & Operating System** | Draft | Specifies JITOS, a causal operating system defining the execution model, observer interface, and kernel semantics implied by the theory. _COMING SOON_ |
| VI | **Ethics & Sovereignty** | Draft | Addresses provenance, accountability, computational agency, and fork/termination responsibility. *COMING SOON* |
| VII | **Architecture & Operating System** | Draft | Specifies JITOS, a causal operating system defining the execution model, observer interface, and kernel semantics implied by the theory. *COMING SOON* |
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

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

(MD049, emphasis-style)


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

(MD049, emphasis-style)


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

(MD049, emphasis-style)


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

(MD049, emphasis-style)

🤖 Prompt for AI Agents
In README.md around lines 54 to 55, the emphasis markers use underscores
(`_COMING SOON_`) which violates MD049; replace each underscore-delimited
emphasis with asterisk-delimited emphasis (`*COMING SOON*`) so both occurrences
on those lines use asterisks for consistent Markdown emphasis.


---

Expand Down