Watch
1
0
Fork
You've already forked SouveraineOS
0
SouveraineOS/docs/substrate/README.md
2026-08-13 17:46:49 -04:00

41 lines
1.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# The agent substrate — docs
Moved here 2026-07-26 from `~/Projects/souveraine/docs`, which is gitignored
(`.gitignore:64`, "kept on disk, never committed to any remote"). Nine files
had been force-added; the other 210 — including `THE_QUESTION.md`, which the
index calls the one thing to read — existed only on the laptop's disk, on a
volume at 100% with no snapshots. `FEDERATION_SKETCH.md` had already made this
move for the same reason and said why.
`souveraine` has a public branch; this repo does not. That is why the docs land
here rather than being un-ignored in place.
## What this covers
The consciousness runtime: memory, sensorium, felt state, the N+ passes,
federation transport, the TUI. It is a different subject from the rest of
`docs/`, which is the device — session authority, lock, power, sensors,
packaging, hardware.
The sensorium is the agent's whole field of sensing and action across tools and
surfaces. It is not a single screen or compositor.
Read in this order:
- `THE_QUESTION.md` — the orientation doc.
- `CONTEXT_CONSTITUTION.md` — Articles IIX.
- `DECISIONS.md` — the settled log, 60 seconds.
- `SENSORIUM_ARCHITECTURE.md`, `FELT_STATE_ARCHITECTURE.md`,
`ASTER_ARCHITECTURE.md`, `CONSCIOUSNESS_CYCLE.md` — the working drawings.
## What is stale in here
`tasks/INDEX.md` is stamped 2026-05-19 and describes May. Sixteen July files
under `tasks/` are device work — shell, lock, settings, power, packaging — and
belong in `../tasks/` folded into the numbered tasks that already cover them.
Several contradict what shipped: `sensor-driven-lockscreen.md` still has
`blueline-proximity-lock` blanking a locked screen, which stopped being true on
2026-07-25 and stopped existing on 07-26.
Nothing in here was corrected on the way in. It is committed as found, so the
history starts from what was actually on disk.