switchboard/core
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Releases 9 Wiki Activity

Chore roadmap v013x additions
All checks were successful
CI/CD / detect-changes (pull_request) Successful in 3s
Details
CI/CD / test-frontend (pull_request) Has been skipped
Details
CI/CD / test-runners (pull_request) Has been skipped
Details
CI/CD / e2e-smoke (pull_request) Has been skipped
Details
CI/CD / test-go-pg (pull_request) Successful in 2m49s
Details
CI/CD / test-sqlite (pull_request) Successful in 3m4s
Details
CI/CD / build-and-deploy (pull_request) Successful in 46s
Details

Browse Source 
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) <noreply@anthropic.com>
This commit is contained in:
Jeffrey Smith
2026-04-03 18:25:45 +00:00
parent e4bec9c18c
commit 01f2ac5bb7
1 changed files with 22 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
ROADMAP.md
View File

@@ -215,23 +215,28 @@ Design doc: `docs/DESIGN-chat-v012x.md`.
### v0.13.x — Reference Libraries + Extensions ### v0.13.x — Reference Libraries + Extensions
Core libraries and remaining extensions. `llm-bridge` is the key Custom public root surface unblocks everything — anonymous visitors,
delivery — extends both notes and chat through composability primitives, landing pages, and the package registry. `llm-bridge` is the key
and introduces the **tool meta-tool** pattern: `sw.actions.list()` becomes library delivery — extends both notes and chat through composability
the LLM tool registry, so installing an extension = granting AI a new primitives, and introduces the **tool meta-tool** pattern:
capability. Zero configuration. `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 | | Version | Title |
|---------|-------| |---------|-------|
| v0.13.0 | `vector-store` Library | | v0.13.0 | Custom Public Root Surface |
| v0.13.1 | `llm-bridge` Core Library | | v0.13.1 | `vector-store` Library |
| v0.13.2 | `llm-bridge` → Chat: Multi-Persona Context + Tool Meta-Tool | | v0.13.2 | `llm-bridge` Core Library |
| v0.13.3 | `llm-bridge` → Notes: AI Toolbar Actions | | v0.13.3 | `llm-bridge` → Chat: Multi-Persona Context + Tool Meta-Tool |
| v0.13.4 | `file-share` Extension | | v0.13.4 | `llm-bridge` → Notes: AI Toolbar Actions |
| v0.13.5 | `code-workspace` Extension | | v0.13.5 | `file-share` Extension |
| v0.13.6 | `image-gen` + `image-edit` Extensions | | v0.13.6 | Package Registry Extension |
| v0.13.7 | Tool Meta-Tool Hardening + Scoping | | v0.13.7 | `code-workspace` Extension |
| v0.13.8 | Integration Quality Gate | | 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. | | 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. | | 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. | | 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 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. | | 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. | | User sidecars in v0.14.5 | Prove instance contract first, extend to users with same mechanism. |