From 01f2ac5bb705d6fb1a8a3502ae13cad3db2dcab6 Mon Sep 17 00:00:00 2001 From: Jeffrey Smith Date: Fri, 3 Apr 2026 18:25:45 +0000 Subject: [PATCH] Chore roadmap v013x additions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Slot three new versions into v0.13.x series: - v0.13.0 Custom Public Root Surface (unblocks everything) - v0.13.6 Package Registry Extension (after file-share) - v0.13.10 armature.run Deployment (dogfood gate) Existing versions renumbered accordingly (v0.13.0-8 → v0.13.1-9, quality gate → v0.13.11). Design decisions log updated. Co-Authored-By: Claude Opus 4.6 (1M context) --- ROADMAP.md | 36 ++++++++++++++++++++++-------------- 1 file changed, 22 insertions(+), 14 deletions(-) diff --git a/ROADMAP.md b/ROADMAP.md index 436b4ca..a541540 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -215,23 +215,28 @@ Design doc: `docs/DESIGN-chat-v012x.md`. ### v0.13.x — Reference Libraries + Extensions -Core libraries and remaining extensions. `llm-bridge` is the key -delivery — extends both notes and chat through composability primitives, -and introduces the **tool meta-tool** pattern: `sw.actions.list()` becomes -the LLM tool registry, so installing an extension = granting AI a new -capability. Zero configuration. +Custom public root surface unblocks everything — anonymous visitors, +landing pages, and the package registry. `llm-bridge` is the key +library delivery — extends both notes and chat through composability +primitives, and introduces the **tool meta-tool** pattern: +`sw.actions.list()` becomes the LLM tool registry, so installing an +extension = granting AI a new capability. Zero configuration. +`armature.run` deployment is the dogfood gate at the end of the series. | Version | Title | |---------|-------| -| v0.13.0 | `vector-store` Library | -| v0.13.1 | `llm-bridge` Core Library | -| v0.13.2 | `llm-bridge` → Chat: Multi-Persona Context + Tool Meta-Tool | -| v0.13.3 | `llm-bridge` → Notes: AI Toolbar Actions | -| v0.13.4 | `file-share` Extension | -| v0.13.5 | `code-workspace` Extension | -| v0.13.6 | `image-gen` + `image-edit` Extensions | -| v0.13.7 | Tool Meta-Tool Hardening + Scoping | -| v0.13.8 | Integration Quality Gate | +| v0.13.0 | Custom Public Root Surface | +| v0.13.1 | `vector-store` Library | +| v0.13.2 | `llm-bridge` Core Library | +| v0.13.3 | `llm-bridge` → Chat: Multi-Persona Context + Tool Meta-Tool | +| v0.13.4 | `llm-bridge` → Notes: AI Toolbar Actions | +| v0.13.5 | `file-share` Extension | +| v0.13.6 | Package Registry Extension | +| v0.13.7 | `code-workspace` Extension | +| v0.13.8 | `image-gen` + `image-edit` Extensions | +| v0.13.9 | Tool Meta-Tool Hardening + Scoping | +| v0.13.10 | `armature.run` Deployment | +| v0.13.11 | Integration Quality Gate | --- @@ -353,6 +358,9 @@ These are candidates, not commitments. Each requires a design doc. | Layered prompt architecture (6 layers) | Admin safety not overridable. Clear separation: platform → space → character → context → tools → user. | | Personas in llm-bridge, not chat | Chat sees AI as just another participant_type. Persona identity is llm-bridge's concern. | | llm-bridge after notes + chat (v0.13.x) | Proves the composability hooks work without being designed for a specific consumer. | +| Custom public root first in v0.13.x | Unblocks registry, landing page, and armature.run. Small kernel change, high leverage. | +| Package registry as reference extension | Proves public surfaces work. Needs files module for .pkg storage. Self-referential: Armature's registry runs on Armature. | +| armature.run as dogfood gate | If armature.run can't run on Armature, the platform isn't ready. Issues feed into quality gate fixes. | | Sidecar connect-inward | No K8s RBAC, no service mesh, no DNS discovery. Works on any deployment target. | | Sidecar HTTP/JSON, not gRPC | KISS. 4-endpoint contract. Every language has HTTP. | | User sidecars in v0.14.5 | Prove instance contract first, extend to users with same mechanism. |