Update paper titles and links in README#13
Conversation
Signed-off-by: James Ross <james@flyingrobots.dev>
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings. WalkthroughREADME.md documentation updated to replace Zenodo badge links with explicit DOI references for Papers I–IV and V–VI. Paper statuses revised: Paper V transitions from Draft to Published status with title restructuring. Papers VI and VII entries repositioned and updated with new titles and Draft status designations. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
📜 Review details
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (1)
README.md
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
README.md
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)
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)
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)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: build-holography
| [](https://doi.org/10.5281/zenodo.17908005) | ||
| [](https://doi.org/10.5281/zenodo.17934512) | ||
| [](https://doi.org/10.5281/zenodo.17963669) |
There was a problem hiding this comment.
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
-[](https://doi.org/10.5281/zenodo.17908005)
+[](https://doi.org/10.5281/zenodo.17908005)
-[](https://doi.org/10.5281/zenodo.17934512)
+[](https://doi.org/10.5281/zenodo.17934512)
-[](https://doi.org/10.5281/zenodo.17963669)
+[](https://doi.org/10.5281/zenodo.17963669)
-[]()
+[]()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).
| [](https://doi.org/10.5281/zenodo.17934512) | ||
| [](https://doi.org/10.5281/zenodo.17963669) | ||
| [](https://doi.org/10.5281/zenodo.18038297) | ||
| [](https://doi.org/10.5281/zenodo.18146884) |
There was a problem hiding this comment.
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
-[](https://doi.org/10.5281/zenodo.18146884)
+[](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.
| [](https://doi.org/10.5281/zenodo.18146884) | |
| [](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.
| []() | ||
| []() |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Check the README.md file, especially around lines 18-19
head -30 README.md | cat -nRepository: 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.mdRepository: flyingrobots/aion
Length of output: 4259
🏁 Script executed:
# Check the exact lines 18-19 with context
sed -n '15,25p' README.md | cat -nRepository: 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.
| | 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_ | |
There was a problem hiding this comment.
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.
| | 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.
1 participant
No description provided.