Scaffold Lumbridge architecture and research plan
This commit is contained in:
@@ -0,0 +1,15 @@
|
||||
# 0001: Lumbridge is the workspace, not one more mandatory agent
|
||||
|
||||
Status: accepted for the architecture phase.
|
||||
|
||||
Lumbridge owns terminals, workspaces, session durability, integration, review,
|
||||
and usage observability. Existing coding harnesses remain first-class processes.
|
||||
ACP provides rich structure and PTYs provide universal compatibility.
|
||||
|
||||
This boundary preserves user subscriptions, harness-native capabilities, and
|
||||
choice. It also prevents an early attempt to build a terminal, IDE, multiplexer,
|
||||
provider SDK, and universal agent loop as one inseparable component.
|
||||
|
||||
We may later ship an optional Lumbridge-native harness, but the application must
|
||||
remain valuable without it.
|
||||
|
||||
Reference in New Issue
Block a user