docs: frontend roadmap in to-discuss
624c9fc002d6ce33439a8bd2e9c5f1406ac9d74f
Oliver Jan Krylow <oliver@bugabinga.net> · 2026-09-25 17:02 UTC
unsigned 1 parent
repositories / smith
smith
There are many coding harnesses - but this one is fast
owned by admin
Changed files (1)
TO_DISCUSS.md
ready@@ -14,6 +14,12 @@
- Catalog + refresh → plugin. Trigger: catalog churn hurts.
- Input-queue policies (steering, follow-up naming) → plugin. Core mechanism: lifecycle-event queues. Trigger: interactive input work.
+## Frontends
+
+- smith-web: SSE skeleton first (std-only possible), websocket when live input and multi-viewer arrive — websocket forces the async runtime decision. Sequence: formalize smith-rpc as first smith-ui consumer, then smith-web.
+- Fleet / remote effects: p2p multiplexing of machines, tools, plugin instances across smith peers. Layer: beside the effect layer, not smith-ui. Trust tier for fleet peers is the spec-worthy core. Candidate transport: iroh. Trigger: multi-machine usage hurts.
+- smith-mcp: smith AS MCP server for other harnesses — protocol adapter mode like rpc (inbound serving is host-level networking, not plugin territory). Trigger: external-harness integration wanted.
+
## Rethinks
- Benchmarking: regression detection + learning, relative comparisons, in-repo baselines, no machine-specific numbers. Trigger: RELS planning.