daniel/danos
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

documenting things to research

Browse Source
This commit is contained in:
daniel
2026-07-03 21:40:59 +01:00
parent a6de418e42
commit d055de7141
3 changed files with 247 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/README.md
+8 -3
View File
@@ -42,9 +42,14 @@ rather than restate it. Roughly in the order things happen at runtime:
Start with the north star:
- **[vision.md](vision.md) — the vision.** danos is aiming to be a real-time
microkernel: minimal kernel, drivers/services isolated in user space, preemptive
scheduling with timing guarantees. The *why* that shapes everything below.
- **[vision.md](vision.md) — the vision.** danos is a **learning-by-doing**
microkernel: minimal kernel, drivers/services isolated in user space, chosen for
**resilience** (restartable components). Win condition: runs on the author's PC and
both Raspberry Pis, ideally with a GUI. Real-time is an option to explore, not a
requirement. The *why* that shapes everything below.
- **[resilience.md](resilience.md) — resilience.** A design note (not built yet) on
fault isolation + live restart — the reincarnation-server + capability model that
makes "if I break it, I can restart it" real. danos's core motivation.
Cutting across all of these: