2.9 KiB
2.9 KiB
Gjallar Architecture
Objective
Gjallar owns framebuffer-native, multi-scale TUI composition: turning many surface inputs into one dense, inspectable operator display where different regions may use different text resolutions.
Authority Map
- Owner: Gjallar owns display composition, pane partitioning, per-pane virtual text grids, font-scale selection, framebuffer lowering, and future sparse refresh output. Gjallar also owns local cursor state, title-bar hit testing, and minimized/restored panel state.
- Inputs: provider catalogs, provider-owned surface trees, display dimensions, font assets, runtime flags, mouse input, Odin's canonical marquee tape, and eventually direct CultMesh subscriptions.
- Outputs:
gjallar.overviewcomposition state, visible framebuffer frames, cursor presentation, minimized panel presentation, and renderer telemetry. - Derived state: pane weights, pixel rectangles, chosen font sizes, one-row gutter blocks, continuous readable marquee ribbon positions, dirty rectangles, glyph runs, title-bar hit regions, local minimized-panel keys, and compact agent-readable projections.
- Forbidden writers: discovery systems do not decide Gjallar layout; providers do not tune themselves for Nightwing; framebuffer backends do not invent provider truth; Gjallar does not derive marquee content from provider status summaries; Odin and providers do not own Nightwing-local minimized state.
- Shared paths: full-frame rendering, sparse refresh, future browser previews, and agent text capture should lower the same overview model.
- Deletion line: any code that both discovers provider truth and decides final screen composition belongs on one side or the other. Gjallar shows; discovery systems see.
Current Pipeline
Odin provider catalog
-> display provider selection
-> provider surface fetch
-> canonical marquee tape passthrough
-> synthetic gjallar.overview surface
-> EveNode panel extraction
-> weighted AABB packing
-> local minimized-state application
-> title-bar hit-region emission
-> one-row gutter cell plan
-> continuous readable marquee ribbon path
-> per-panel text pressure estimate
-> PSF font selection
-> frame draw commands
-> BGRA framebuffer present
Target Pipeline
SurfaceSource[]
-> GjallarOverview
-> PaneTree
-> PaneGrid[]
-> RenderPlan
-> backend
Backends:
FramebufferBackend: full BGRA frame writes, current implementation.SparseCellBackend: dirty cell/glyph/rect pipe for high-frequency remote or terminal targets.AgentTextBackend: token-efficient navigation and panel capture for agents.
First Product Claim
Gjallar is not a terminal multiplexer and not a dashboard theme. It is a multi-resolution text compositor. The important gap is that each pane can become its own virtual terminal scale while still belonging to one coherent display.