Fimeg/SouveraineOS
Watch
1
0
Fork
You've already forked SouveraineOS
 0
Code Releases Activity
No description
152 commits 1 branch 0 tags 2.4 MiB
  • Python 86.4%
  • C 8.4%
  • Shell 5.2%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Fimeg b2ce5d7cb0 lock-dpms: waking is the machine's, and the compositor must not do it itself 
The panel had no way back: apply_gesture answers a tap on a dark panel
with Restore, which is brightness, and there was no unblank in the action
table. Invisible while hyprland bound the keys straight to the toggle;
under viewtop it became a phone that could sleep and never wake.

Records the wake loop too, because building it wrong is the obvious move:
viewtop waking directly worked, then sessiond resolved the same press,
found the panel lit, and blanked it again. One press woke the phone and
put it back to sleep. Plus why dt2w is a wake and not a button, and the
deploy order that has to hold between the two halves.
2026-08-02 17:37:51 -04:00
blueline blueline: move wifi-bringup to Pixel3Arch rootfs-overlay 2026-08-01 13:16:45 -04:00
docs lock-dpms: waking is the machine's, and the compositor must not do it itself 2026-08-02 17:37:51 -04:00
PAF PAF: bring the blueline architecture framework into SouveraineOS 2026-07-24 11:04:07 -04:00
tools tools: read CI outcomes from the API, and do it automatically 2026-07-28 17:38:44 -04:00
CLAUDE.md CLAUDE.md: the umbrella repo had none 2026-07-30 19:13:34 -04:00
STATE.md TASK-43: touch served; next lane is KMS on device 2026-08-02 08:56:05 -04:00

docs/README.md

SouveraineOS — docs

Two subjects live here, and the split is real:

  • this directory — the device. Session authority, lock, power, sensors, shell, packaging, hardware.
  • substrate/ — the agent. Consciousness, memory, sensorium, felt state, federation transport, TUI. Rescued 2026-07-26 out of a gitignored directory on a full disk; read its README before trusting anything in it.

The device — read in this order

Why. SESSION-AUTHORITY-DOCTRINE.md — §13 first (who owns the device), then §4 (never hold state the protocol owns), §9 (sensors are evidence), §10–11 (one authority).

What is built. DEVICE-STATE-MACHINE.md — the unified machine: the audit that found each bug, the evidence model, the error contract, prior art, source health, and the trail.

What is true of the hardware. LOCK-DPMS-LESSONS.md — ordering, the FTS controller, suspend, with receipts.

Contracts and status. SESSION-TRUST-ARCHITECTURE.md (the contract), TRUST-BOUNDARY-MATRIX.md (what is actually gated), SECURITY-AUDIT.md (P1–P7 and the threat register), souveraine-components/ (the authority binaries and their audit ladder).

Designs of record. STORAGE-ENCRYPTION.md, FEDERATION.md, session-authority-boot-order.md.

The shell and its apps. FIRST-CLASS-APPS.md (the nine requirements), SHELL-ECOSYSTEM.md (layer registry, manifests, guarded methods — the substrate doctrine §13's chaining needs), SETTINGS-AUTHORITY.md, AUDIO-PRIVACY.md, INTERFACE-ARCHITECTURE.md (intent), HOW-IT-WORKS.md (current wiring), REFERENCE-EXTRACTION.md (what to steal from whom), SETTINGS-APP-PLAN.md.

Work. tasks/README.md is the index. Single-session units, numbered. Fewer files, not more — a finding goes in the doc that owns the subject.

archive/ is superseded material kept as evidence. It is not authoritative and it is not deleted.

The rule that governs all of it

Where a doc and the code disagree, the code is right — fix one or the other in the same change, and never leave a third story.