Scaffold Lumbridge architecture and research plan

docs/decisions/0001-product-boundary.md

@@ -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.
+

docs/decisions/0002-usage-provenance.md

@@ -0,0 +1,15 @@
+# 0002: Usage data always carries provenance
+
+Status: accepted for the architecture phase.
+
+Provider quotas and subscription windows do not share a stable universal API.
+Lumbridge therefore stores observations with their source and derives forecasts
+without overwriting the facts.
+
+Allowed provenance values begin as provider-reported, harness-reported, locally
+measured, estimated, and unavailable. The UI may simplify these labels in compact
+views, but the detail view and export retain them.
+
+Lumbridge will not scrape browser cookies, copy upstream OAuth tokens, or label a
+local estimate as an exact remaining subscription balance.
+