Watch
1
0
Fork
You've already forked SouveraineOS
0
Commit graph SouveraineOS/STATE.md
Author SHA1 Message Date
Fimeg
b78342a337 dump: fingerprint handoff, and the protocol is recovered
STATE moved to 2026-08-09. One instrument is waiting on a finger;
everything else about the enrol lifecycle is reachable in RAM today.
2026-08-09 10:01:51 -04:00
Fimeg
18c58fc079 docs: the day viewtop got its package, its titles and its borders
STATE.md was five days stale. It now carries what is on the phone
(viewtop r76, souveraine r333) and the four defects fixed on the glass:
per-window capture was unreachable because quickshell holds wlr handles and
the ext capture source is named by an ext handle with nothing correlating
them; titles were never republished on commit; the border was a filled slab
that relied on the client covering its middle; capture came back flipped.

Also the packaging hole, which was the important one — viewtop's PKGBUILD
existed and appeared in none of packages.yml's build lists, so nothing ever
built it. Half closed: it builds now, but a viewtop commit still does not
trigger a rebuild.

TASK-15 question 1 is answered and closed: dropping the accelerometer claim
took iio-sensor-proxy from 15.3% to 1.1%, sensors overall 17.2% to 2.6% of
a core. Consequence noted against 08(g) — confidence loses accel's +0.3.

New: 54, 55, 56, and 57/58 (Pi dock head, SMB2 OTG boost) with the USB
notes they point at.
2026-08-04 18:18:17 -04:00
Fimeg
96094c7893 TASK-43: touch served; next lane is KMS on device
viewtop at 458a354. Records the touch fork (provenance from the event
source; the agent reaches the seat but never the evidence stream) and
marks lanes 1 and 2 done — the Smithay frontend and the session-lock
server both landed.

Adds the resume steps for KMS on device: what it will actually show
(clients on black — shell-host is still thirteen lines), the cheap proof
that needs no pixels (sensor_health.touch is `unknown` on the phone and
has never been anything else), the missing test client, and the DRM
master risk on a daily driver.

Also: the `vanguard` ssh entry on the phone has the wrong user, which
presents as a key failure.
2026-08-02 08:56:05 -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
66dbb601fa docs: add SHELL-SURFACES.md — the migration checklist
Migrations have been silently lossy: the subconscious surface was stranded for
over a week by the ii -> souveraine shell move, and five packages went stale,
both because there was no list of what exists to tick off. SHELL-SURFACES.md is
that list — every shell surface and first-party service, the contract it is
defined against, its substrate today, and whether it reaches the glass.

States the rule that would have caught it: a feature defined as QML in a shell
tree dies with that tree; one defined against a contract survives (the
subconscious model in services/Ai.qml crossed untouched; only its views, riveted
to the ii overlay system, stranded). Marks the ii-substrate furniture rows
UNVERIFIED — that verification is the checklist's first demand. STATE.md points
at it from the resume anchor.
2026-07-30 12:59:59 -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
712e8a9ec3 DUMP: the session that retired flashing 2026-07-25 06:06:22 -04:00
Fimeg
ce66a2a74f STATE: phone updates with pacman; flashing retired 2026-07-24 22:06:02 -04:00
Fimeg
19475878dd deprecate chatty/libcmatrix/qtpim, clean stale refs
Chatty superseded by souveraine's Matrix sensorium. libcmatrix unused.
qtpim contacts work stalled. All repos archived on Gitea.

- STATE.md: remove component sections, update secrets consumers, decisions
- Mark deprecated docs with headers
- Update INVENTORY.md Tier 3 entries as deprecated
- Update secrets.md consumer list
2026-07-21 13:51:14 -04:00
Fimeg
b563c37d0a provisioning-gaps: log every hand-fill from the first federation test
STATE.md: federation test passed — two instance branches, both agents
speaking on glm-5.2, identities split.
2026-07-16 16:11:15 -04:00
Fimeg
b11037b7d6 aarch64 artifact for c96f95b verified green on archdev 2026-07-16 12:12:16 -04:00
Fimeg
05037d1c66 resume anchor: next-session order (phone federation test, auxo/chatty), fresh artifact note 2026-07-16 12:08:46 -04:00
Fimeg
71b014b587 shell UX round: dock drag fix, rail/keyboard, overview dismiss 2026-07-16 12:04:33 -04:00
Fimeg
7bc6d4fa82 federation: instance awareness live half landed (hosted_agents in announce) 2026-07-16 11:18:25 -04:00
Fimeg
fe1cd49d53 federation: steps 1+2 landed (memfs_commit signal, memory sync); archdev-verified 2026-07-16 11:12:53 -04:00
Fimeg
0da372b314 state + federation design of record
machined system tier landed in souveraine (5039163/116562a); boot-gate
vs session-lock doctrine on record. FEDERATION.md moves here from
souveraine's gitignored docs tree, rewritten: implemented pieces cited,
memfs transport roughed (shared bare remote, branch-per-instance,
domain merge policy, memfs_commit firehose signal), instance awareness
design, and the install-time agent instantiation flag.
2026-07-16 10:41:14 -04:00
Fimeg
921b03eaee STATE: Chatty/libcmatrix now on Gitea 2026-07-16 09:10:43 -04:00
Fimeg
dc4fd14bbd SouveraineOS umbrella: docs, dumps, handoffs, cross-repo STATE 2026-07-16 08:59:26 -04:00