24 lines
1.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
# 0008: Every workspace panel uses a terminal-first 3×1 composition
|
||
|
||
Status: accepted for the native vertical slice.
|
||
|
||
Every Lumbridge workspace panel defaults to three horizontal regions in one
|
||
column. The top 20% exposes that pane's agent, tools, context, goal, target, and
|
||
attention state. The middle 60% is that pane's terminal-first work surface. The
|
||
bottom 20% is that pane's answer, choice, chat, approval, and local-analyst
|
||
boundary.
|
||
|
||
This composition keeps the information needed to understand and steer a process
|
||
attached to the same visual object as its terminal. The workspace may contain a
|
||
responsive number of these panels under decision 0009; the selected panel alone
|
||
owns keyboard input.
|
||
|
||
The framework spike retains six updating surfaces even when one is outside the
|
||
five-panel ultrawide window. That preserves the earlier streaming and reducer
|
||
workload for performance comparison. Hidden panels do not receive keyboard input
|
||
merely because they continue to update.
|
||
|
||
Window and panel 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.
|