Update docs/plans/2026-04-23-prototype-options.md
ca36b1b108f9 jacobcole 2026-04-23 1 file
index aea1267..76e6e39 100644
@@ -1,7 +1,3 @@
-visibility: public
-
# Prototype options — brainstorm
**Date:** 2026-04-23
@@ -42,7 +38,9 @@ Six concrete bundles Jacob asked about. Each card's header lists its coordinates
---
-### Option 2 — "Piyush-style" (two-box, per-user, `claude -c -p`)
+### Option 2 — "No-Docker architecture" (two-box, `claude -c -p` per turn)
+
+*Previously called "Piyush-style." Renamed 2026-04-23 to be honest about provenance — the pattern is Piyush-inspired but the specific design is not what he shipped. See [mockup 03](../mockups/03-piyush-literal.html) for Piyush's literal architecture.*
**(A=2-box, B=per-user, C=claude-c-p, D=claude's --session-id, E=none, F=terminal+browser)**
@@ -110,7 +108,7 @@ Any of options 1-5 can adopt this. noos's graph DB is queried over HTTP (`x-api-
## Hybrids worth naming
-**Option 2 + Option 6:** Piyush-layout with noos graph as a separate machine's HTTP service. Most likely to be the v0.1 shape.
+**Option 2 + Option 6:** No-Docker layout (bot server + Claude box) with noos graph as a separate machine's HTTP service. Most likely to be the v0.1 shape.
**Option 4 + Option 6:** Pure-texting MVP with noos graph for memory. Ship in days, upgrade to Option 2 if development-surface ends up needed.
@@ -155,4 +153,4 @@ Treat those as **provisional** until Q0-Q4 close.
- [Piyush-era design study](../wiki/piyush-era-design.md)
- [Codex review 2026-04-23](../reviews/codex-2026-04-23.md) — pushed for `claude --print` spike
- `~/memory/research/openclaw-group-chat-security.md` — Option 5 risk model
-- [cortex-inheritance.md](../wiki/cortex-inheritance.md) — inheritance rules
\ No newline at end of file
+- [cortex-inheritance.md](../wiki/cortex-inheritance.md) — inheritance rules