Watch
1
0
Fork
You've already forked SouveraineOS
0
No description
  • 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 d10479710d tasks: 52 atmosphere, and narrow the haptics question to one a hand can answer
52 maps the fifteen-technique attention vocabulary onto what viewtop can
actually do. Two are already landed — expose IS negative space, pose IS
gravity wells — and compile_custom_pixel_shader + PixelShaderElement are
already in our smithay, so #1/#6/#9/#11/#12/#13/#14 need no new machinery.

The load-bearing note is ordering: build the attention model and one
global clock before any individual effect, or fifteen animators fight
over the same surfaces and it is §1's blind actors in the render path.
That failure already happened this week in the panel. Attention decisions
go in forensic.jsonl in the same change, so the atmosphere is
imperceptible in the moment and legible afterward — the standard every
other authority here is held to.

45: the PMIC haptics path accepts and plays an FF effect and the CS40L20
is absent from this kernel, so the five-minute check is now one question
only a hand can answer.
2026-08-02 18:04:26 -04:00
blueline blueline: move wifi-bringup to Pixel3Arch rootfs-overlay 2026-08-01 13:16:45 -04:00
docs tasks: 52 atmosphere, and narrow the haptics question to one a hand can answer 2026-08-02 18:04:26 -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

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), §1011 (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 (P1P7 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.