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

Restructure roadmap: workflows → v0.3.x, notes shifts to v0.4.0

Browse Source 
Workflows are big enough for their own minor series. v0.3.x now
includes workflow architecture, team roles (role-based stage
assignment, multi-party sign-off), and trigger composition.
Notes moves from v0.3.0 to v0.4.0. MVP becomes v0.5.0.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jeffrey Smith
2026-03-27 14:02:55 +00:00
parent 2b3a3f08ef
commit 242709526b
1 changed files with 16 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
ROADMAP.md
View File

@@ -89,15 +89,26 @@ SDK stabilization, and the first rebuilt extension (tasks).
| Default surface routing | ✅ | Resolution chain: user preference → global config → first extension → `/welcome`. Users can set personal default in Settings > General. Admin sets global default in Admin > Settings. |
| Admin navigation | ✅ | Replaced Back button with UserMenu in admin topbar. Eliminates back-button infinite loop. |
### v0.2.6 — Workflow Architecture
### v0.2.6 — Extension Lifecycle
| Step | Status | Description |
|------|--------|-------------|
| Workflow design session | ⬚ | Define what "workflow" means in the extension-first model. Determine if the existing `workflows` table/handler survives, gets rebuilt, or gets removed. Document the Starlark contract for multi-step automation. |
| Trigger composition model | ⬚ | How do triggers, schedules, and workflows compose? Event chains, conditional branching, error handling. Design doc before code. |
| Extension lifecycle | ⬚ | Define permanent vs PoC extensions. Package graduation criteria. Dependency policy. What ships with core vs what's installed separately. |
## v0.3.0 — Notes Surface
## v0.3.x — Workflow Architecture
Workflows are the core platform capability. This series implements the
full multi-step automation system with team role integration.
### v0.3.0 — Workflow Design + Schema
| Step | Status | Description |
|------|--------|-------------|
| Workflow design session | ⬚ | Define what "workflow" means in the extension-first model. Determine if the existing `workflows` table/handler survives, gets rebuilt, or gets removed. Document the Starlark contract for multi-step automation. See `docs/DESIGN-WORKFLOW-REDESIGN-0.2.6.md`. |
| Team roles | ⬚ | Different roles per team responsible for different workflow stages. Role-based stage assignment, multi-party validation (2-party sign-off at stage boundaries). |
| Trigger composition model | ⬚ | How do triggers, schedules, and workflows compose? Event chains, conditional branching, error handling. Design doc before code. |
## v0.4.0 — Notes Surface
Obsidian-style rich-text notes rebuilt as an installable surface package.
Zero platform special-casing. Proves the full extension stack E2E.
@@ -107,7 +118,7 @@ Zero platform special-casing. Proves the full extension stack E2E.
- Folder tree, backlinks, tags — all extension-provided
- Markdown import/export
## v0.4.0 — MVP
## v0.5.0 — MVP
Extension and operations tracks converge. First externally usable release.