23 lines
1.2 KiB
Markdown
23 lines
1.2 KiB
Markdown
# 0008: The default workspace is a primary-terminal 3×1 composition
|
||
|
||
Status: accepted for the native vertical slice.
|
||
|
||
Lumbridge defaults to three horizontal bands in one column. The top 20% exposes
|
||
pane, agent, tools, context, goal, target, and attention state. The middle 60%
|
||
is the terminal-first work region. The bottom 20% holds answers, choices, chat,
|
||
approvals, and the local-analyst boundary.
|
||
|
||
This composition favors the region where engineers type and read for most of the
|
||
day. It keeps context and decisions visible without making every surface a small
|
||
dashboard card. The middle region may contain a responsive number of vertical
|
||
work lanes under decision 0009; the selected lane alone owns keyboard input.
|
||
|
||
The framework spike retains six updating surfaces even when five are offscreen.
|
||
That preserves the earlier streaming and reducer workload for performance
|
||
comparison. Hidden surfaces do not receive keyboard input merely because they
|
||
continue to update.
|
||
|
||
Window and lane geometry determine each terminal's rows and columns. The UI
|
||
resizes the terminal engine and PTY through the bounded runtime actor; it does
|
||
not resize only the text view or infer terminal wrapping after the fact.
|