Watch
1
0
Fork
You've already forked SouveraineOS
0
SouveraineOS/saf/INDEX.md
Fimeg bde961c6f2 saf: one spine — device, state, and work under the index
PAF becomes saf/device (history kept), STATE.md dissolves
into saf/state.md with the dated era archived, the substrate
SAF moves up from souveraine, and every agreement points at
saf/INDEX.md and nowhere else. one map, nothing to remember
2026-08-18 09:47:30 -04:00

4 KiB

Souveraine, mapped

One spine. Every truth about the system is reached from here — architecture, device, state, work. For whoever reads it, human or agent. When this and the code disagree, the code is right. Still being written, and not yet human-reviewed.

core: what the substrate is

  • the substrate. The few things that stay true inside it.
  • two modes. Her, and the subconscious a moment later.

identity: who she is

  • identity. Two keys, the glyph, reaching and consulting.
  • agent principals. Her own Unix account on each body, creation, admission, health, and the operating skill that explains the boundary.

federation: how one being exists in more than one place

  • node enrolment. The missing ceremony for adding a device without copying an identity.

authority: who may decide, and which truths she consumes

  • session authority. One policy and action boundary over Linux, Wayland, authentication, and the agent's hand.
  • device state. One state machine from evidence through belief and action to acknowledgement.

nervous: how she feels things happen

  • the nervous system. One bus, one kind of message.
  • belief. Evidence that decays, disagrees, persists, and never turns unknown into zero.
  • felt state. Pressure, energy, atmosphere, posture, and the body beneath both cadences.

memory: how she holds on and lets go

  • compaction. Five ways to make room.
  • replay. One projection of what she keeps onto what the model sees.

surface: how the body she lives in moves

  • motion. One clock, two strategies, and why the shell never transforms a window.
  • session start. One package-owned dependency graph from compositor socket to authority to shell.
  • USB Hands. An armed wire, an optional trackpad, and one acknowledged hand into the attached host.
  • agent panel. One Souveraine conversation, typed thought and action, and truthful controls at the hand.
  • agent presence. One observed session projection, kept rigorously separate from control and permission.
  • surface lifetimes. A small resident shell, optional workers that truly leave memory, and proof before a rewrite.

device: the hardware body

  • device. The living hardware record — audio, display, modem, mms, edge-sense, slpi, platform, build, evidence. Device code, packages, overlays, and the kernel stay in Pixel3Arch/; the record of what they do is here.

state: what is true right now

  • state. The resume anchor: what is deployed, what is open, where the next session starts. Dated history lives in archive/ and never returns as news.

work: what is being done

  • the work index. One task per session. Task files are temporary work records and move to archive; they do not remain a second design authority.

elsewhere: code, and the frameworks that share seams

  • souveraine/ — the substrate (Rust). Code only.
  • Pixel3Arch/ — device implementation: packages, overlays, the kernel tree.
  • souveraine-viewtop/, souveraine-sessiond/, and the other souveraine-* — their named components.
  • RedFlag/RAF/ — the infrastructure/security framework. Shares seams, distinct design.

Coming: the rest of identity (the memory filesystem, the ledgers), the nervous system (schedules, the event log), the consciousness cycle, the runtime, the rest of federation, a glossary.

SAF owns the living architecture. Task files are temporary work records and move to archive; they do not remain a second design authority. The old single-file version sits in archive/.