Watch
1
0
Fork
You've already forked SouveraineOS
0
Commit graph SouveraineOS/docs/tasks/25-one-repo-all-packages.md
Author SHA1 Message Date
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
Fimeg
4934f80e30 distribution: admit the blueline kernel packages 2026-08-13 14:31:19 -04:00
Fimeg
d8820da557 distribution: add ViewTop to the laptop body
Record update delivery as a per-body offer and local candidate activation after a live shell push killed an active conversation.
2026-08-11 14:40:08 -04:00
Fimeg
6cc89ef25c docs: checkpoint device and system state 2026-08-10 17:00:23 -04:00
Fimeg
ee68f5b47b mark package stranding resolved (TASK-25)
Pixel3Arch packages.yml now publishes all 14 device packages; pacman -Sl
souveraine-aarch64 is the manifest. Update TASK-25 status/acceptance +
record the four cross-build shapes and the committed-junk CI trap. DUMP
for the session. STATE.md last-updated 2026-07-30.
2026-07-30 13:57:00 -04:00
Fimeg
e08ec7a0d9 docs: state machine audit 2026-07-26; retire TASK-26 references
DEVICE-STATE-MACHINE §0: the audit, in the doc rather than a new task file.
Lock shadow copy found and fixed (doctrine §4). Two open: proximity has no
debounce and thrashed 69 transitions in 40min (§9.5 already specifies the fix),
and forensic.jsonl sits on tmpfs — RAM, wiped on reboot, unbounded.

TASK-26 was never written and no longer needs to be: the proximity second
authority is resolved, packaging is TASK-27. Dangling refs in STATE.md,
TASK-25 and TASK-27 now say that instead of pointing at a missing file.
2026-07-26 07:28:27 -04:00
Fimeg
7cb55401e6 TASK-26: sensor evidence and a single authority over it
The device state machine is not observational, it is blind: nothing in any
repo ever sends SensorInput, so observed_confidence cannot leave 0.0 and the
forensic log cannot fill. Meanwhile blueline-proximity-lock is live and
acting on proximity on its own authority, unowned by any package. Carved as
its own task because 08(a) and 15 are both efferent and assume afferents
that do not exist - wiring actuators first would manufacture exactly the
success-shaped switches 19 forbids.

Also: 08(b) corrected (ChargeType and PercentageTrusted existed on the bus
but reported defaults for days; three fixes needed, only the third moved it),
25 gains the real kernel blockers and the unowned-file inventory, and STATE
no longer claims the kernel ships by pacman.
2026-07-25 08:14:15 -04:00
Fimeg
616c933e5b TASK-08b unblocked: pmi8998 charge control is live; note the settings-packaging stage 2026-07-24 22:11:45 -04:00
Fimeg
66053e1948 tasks: one gitea repo for every package (25); keyboard rethink (24); device-state deploy
25 captures the pipeline unification: souveraine's CI is the only one
doing repo-add --sign, so everything else has to be hand-carried to the
phone. Records the phone-side wiring that went live today and the two
pacman traps behind it (DownloadUser vs a custom XferCommand, and the
DisableSandbox* lines that were never real options).
2026-07-24 20:29:17 -04:00