Fimeg/SouveraineOS
Watch
1
0
Fork
You've already forked SouveraineOS
 0
Code Releases Activity
No description
198 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 dd5e242227 TASK-63: touch on the glass, and a display pipe on T8010 
Touch proven with real events, not a device node: three layers, the last
being runtime report activation gated to D11 so D10 went silent a second
after boot.

adp binds on 206200000.display-pipe with card1-DSI-1 — the first DRM
display pipe on this hardware; everyone else scans a dumb framebuffer.
Still unused because m1n1 re-enables /chosen/framebuffer and udev then
hands viewtop simpledrm.

Kernel patch kept as evidence; hoolock/ is not a repo.
2026-08-09 22:09:18 -04:00
blueline blueline: move wifi-bringup to Pixel3Arch rootfs-overlay 2026-08-01 13:16:45 -04:00
docs TASK-63: touch on the glass, and a display pipe on T8010 2026-08-09 22:09:18 -04:00
PAF TASK-63: touch on the glass, and a display pipe on T8010 2026-08-09 22:09:18 -04:00
tools tools: read CI outcomes from the API, and do it automatically 2026-07-28 17:38:44 -04:00
USB docs: reconcile USB, Waydroid, audio and charging 2026-08-07 14:52:28 -04:00
CLAUDE.md START-HERE: the page to open when something is broken 2026-08-02 19:13:40 -04:00
HANDOFF-2026-08-05-navigation.md compositor pushes the strip; float, gamma 2026-08-05 19:16:41 -04:00
START-HERE.md 55: sheet, split chooser, power menu; viewtop ships by pacman 2026-08-05 14:53:04 -04:00
STATE.md dump: fingerprint handoff, and the protocol is recovered 2026-08-09 10:01:51 -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, WAYDROID.md, ../USB/README.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.