| Filename | Latest commit message | Latest commit date |
|---|---|---|
fdb0acfdce
OverviewWidget draws a grid of workspaces and places windows in them by Hyprland coordinates — HyprlandData.windowList, monitorData, Hyprland.monitorFor. Under viewtop none of it resolves, and more to the point viewtop has no workspaces at all: one space, a tiling layout. The old overview could not be repaired by repointing it at another data source, because the thing it draws does not exist. It rendered an empty frame, which reads as the overview being broken. WindowOverview lists what does exist. Cards from ToplevelManager.toplevels — the same list the dock and TaskbarApps already read, so there is one idea of what is open — each holding a live ScreencopyView of one window, which only became possible when the compositor started serving a per-window capture source; until then a card could have shown nothing but the screen it was covering. The motion is the reference shell's, read out of overview_window_card.dart rather than invented: stagger at index * 45 ms capped at the fifth card, intro scale 0.86 to 1.0, dismiss past 32% of the card height, 56 px of downward rubber-banding, settle under 200 ms. The cap is the part worth keeping — without it the tenth card starts half a second after the first and the overview feels like it is loading rather than opening. Captures run only while the overview is up. A live capture per window is a render of that window every frame, and leaving them going behind a closed overview is battery spent drawing what nobody can see. |
||
| .. | ||
| assets/keyboard | ||
| ii-base | ||
| ii-phone | ||
| modules | ||
| panelFamilies | ||
| scripts/wallpaper | ||
| services | ||
| deploy.sh | ||
| GlobalStates.qml | ||
| II-BASE.md | ||
| ii-base.pin | ||
| qmldir | ||
| README.md | ||
| settings-launch.sh | ||
| settings.qml | ||
| SettingsWindow.qml | ||
| shell.qml | ||
| souveraine-settings.desktop | ||
Souveraine quickshell surface
The desktop shell as a Souveraine surface — the primary visual frontend for SouveraineOS, with the TUI remaining the dive-in instrument.
Architecture
services/Souveraine.qml— the substrate singleton. The ONE server connection every shell module hangs off: agent inventory, conversation lifecycle, the SSE turn stream (raw events re-emitted viastreamEvent(var)), the backchannel (cancelTurn()/interject(text)), and the desktop sensorium — every send carries ambient context (active window, open apps, cursor position) so she perceives the room she is being spoken to in. Device sensors (SouveraineOS positional data from the Pixel 3 kernel path) extendcollectAmbient().services/Ai.qml— ii-compat adapter. Keeps the API the illogical-impulse sidebar expects; owns no transport. Shapes wire events into the message objects the existing chat UI renders.modules/—souveraine/(ours: lock, navigation, dial, subconscious),settings/,common/, andii/(the files where we override upstream). Each subscribes to the Souveraine singleton. Still pending here: presence (portrait PNGs from memfs, posture state machine), the cockpit pane and the agent manager.
What changes
- "Models" in the sidebar are Souveraine agents (
GET /v1/agents). Picking one starts a conversation with that agent — memory, sensors, subconscious and all. - Messages stream over the server's SSE endpoint
(
POST /v1/conversations/:id/messages), authenticated with the agent's bearer token from~/.souveraine/server/agents/<id>/api_token. - Subconscious surfacings, reflection, and archivist pressure render in the chat as interface notes (dedicated widgets later).
- Reasoning and sensor activity render inside collapsible
<think>blocks. - Keys/providers/temperature are owned by
souveraine.toml— the sidebar's/keyand/tempcommands now just point there. The keyring path is dead. - Token pressure is fetched after each turn from
GET /v1/conversations/:id/tokens.
Portability (KDE / non-Hyprland)
Souveraine.qml itself is compositor-agnostic: quickshell runs on any
wlroots-ish Wayland compositor and KWin; window sensing uses the
foreign-toplevel protocol (KWin implements it); the cursor read tries
hyprctl, then kdotool, then degrades to nothing — ambient never blocks
a send. Server autostart is desktop-neutral (systemd user unit, nohup
fallback), so opening any surface summons her.
What is NOT portable yet is the chrome: the chat UI is illogical-impulse's
sidebar. The path for "I run KDE, can I use this?" is a standalone
quickshell config (own ShellRoot + a window hosting the chat/presence
modules) that ships Souveraine.qml unchanged — planned once the modules
stop being ii-embedded. Same service, same mappings, different shell.
Deploy
./deploy.sh # compose ~/.config/quickshell/souveraine
./deploy.sh -u # remove the composed config (ii untouched)
./deploy.sh --phone # rsync this surface to the phone and deploy there
deploy.sh no longer just swaps Ai.qml — it BUILDS the whole config: our
files symlinked from the repo, untouched upstream directories borrowed as
whole-dir symlinks into ~/.config/quickshell/ii, and that ii tree itself
rsynced from this repo's ii-base/ pin on every run (plus ii-phone/ on
aarch64). Never hand-edit ~/.config/quickshell/ii — the next deploy
overwrites it. Read the header of deploy.sh; it is the authority.
Requires the server: souveraine server (default http://127.0.0.1:8484,
override with ai.souveraineUrl in the ii config).
Wire contract
The server's SSE layer is a full mirror of BackendEvent (see
src/api/models.rs::StreamEvent — exhaustive From impls both ways, so a
new engine event is a compile error at the seam, not a silent skip). The
surface consumes the personification channel: subconscious tokens buffer and
flush as one bubble when the N+1 pass ends (subconscious_pass), halts land
as body signals, interstitials render by register (cenno = quiet aside,
her_voice = gutter passage), primary_complete releases the input while the
stream stays open for the subconscious, and context_pressure drives the
live token counter. atmosphere/outfit/itinerary are logged, awaiting
their shell-chrome layer.
Server-side, the backchannel and verbs exist for every surface:
POST /v1/conversations/:id/cancel (interrupt, *[raised hand]*
semantics), .../interject (mid-turn notes, queued between turns),
GET .../messages (transcript backfill), POST .../fork (/btw
side-quests). SendMessageRequest.ambient injects the sensorium note.
RemoteBackend rides all of it, so TUI remote mode gained cancel/interject/
fork/resume in the same stroke.
Not yet wired
- Sidebar UI hooks for cancel (Esc) and interject (type-while-busy) — the service functions exist, the ii chat input doesn't call them yet
- Conversation resume in the sidebar (server verb exists; surface always starts fresh)
- Atmosphere/outfit/itinerary driving actual shell chrome (events arrive; modules pending)
- File/image attachments (server has an image path; surface doesn't use it yet)
- Regenerate (Souveraine conversations are forward-only by doctrine)
- "Blank LLM mode" — a memoryless passthrough agent for throwaway questions; needs a server-side agent flavor first
- Dedicated widgets for surfacing/subconscious bubbles instead of interface notes