Roadmap restructure v038 v039 (#231)
Co-authored-by: gobha <jasafpro@gmail.com> Co-committed-by: gobha <jasafpro@gmail.com>
This commit is contained in:
139
docs/ROADMAP.md
139
docs/ROADMAP.md
@@ -15,10 +15,12 @@ No compatibility guarantees before 1.0.
|
||||
|
||||
## Dependency Graph
|
||||
|
||||
Two parallel implementation tracks converge at v0.50.0 (MVP). The
|
||||
extension track builds the package ecosystem and workflow capabilities.
|
||||
The operations track builds production readiness for multi-team
|
||||
deployment. Neither blocks the other until the MVP gate.
|
||||
Three parallel implementation tracks converge at v0.50.0 (MVP). The
|
||||
extension track (v0.38.x) builds the package ecosystem that dynamic
|
||||
workflows depend on. The workflow track (v0.39.x) builds both simple
|
||||
and dynamic workflow capabilities on that foundation. The operations
|
||||
track builds production readiness. A polish series (v0.40.x) follows
|
||||
to stabilize for MVP.
|
||||
|
||||
```
|
||||
v0.9.x–v0.28.7 Foundation through Platform Polish ✅
|
||||
@@ -52,17 +54,23 @@ v0.9.x–v0.28.7 Foundation through Platform Polish ✅
|
||||
│ v0.37.17–18 Surfaces ✅ │
|
||||
│ v0.37.19 Tag │
|
||||
│ │ │
|
||||
│ v0.38.x Workflow │
|
||||
│ Product Maturity │
|
||||
v0.38.0–.4 │ │
|
||||
Extension │ │
|
||||
Continuation │ │
|
||||
│ │ │
|
||||
v0.39.0 │ │
|
||||
v0.39.1 │ │
|
||||
v0.39.2 │ │
|
||||
v0.39.3 │ │
|
||||
├────────────┤ │
|
||||
│ │ │
|
||||
│ v0.39.x Workflow │
|
||||
│ Product Maturity │
|
||||
│ (simple + dynamic) │
|
||||
│ │ │
|
||||
│ v0.40.x Polish │
|
||||
│ (bug hunt, dead │
|
||||
│ code, stabilize) │
|
||||
│ │ │
|
||||
══════╪════════════╪═════════════════╪══════
|
||||
│ MVP v0.50.0 │
|
||||
│ (all three tracks complete │
|
||||
│ (all tracks complete │
|
||||
│ + mobile + deploy docs) │
|
||||
══════╪════════════╪═════════════════╪══════
|
||||
│
|
||||
@@ -254,36 +262,81 @@ light mode CSS audit, dead code hunt. Every capability has a UI.
|
||||
|
||||
---
|
||||
|
||||
## v0.38.x — Workflow Product Maturity
|
||||
|
||||
See [ROADMAP-0.38](Workflow/ROADMAP-0.38.md) for full version plan.
|
||||
|
||||
Visual workflow builder series. Bridges .37 plumbing to MVP gate
|
||||
("team admins build workflows visually").
|
||||
|
||||
| Version | Summary | MVP Role |
|
||||
|---------|---------|----------|
|
||||
| v0.38.0 | Form Builder | **Blocker** — visual field editor replaces JSON textarea |
|
||||
| v0.38.1 | Stage Reorder + Bulk Ops | DnD reorder, multi-select operations |
|
||||
| v0.38.2 | SLA Alerting | Scheduled scanner, breach notifications |
|
||||
| v0.38.3 | Visitor Experience | Branding, progress indicator, email notifications |
|
||||
| v0.38.4 | Workflow Templates + Clone | 5 built-in templates, deep copy |
|
||||
| v0.38.5 | Analytics Dashboard | Throughput, cycle time, SLA compliance |
|
||||
|
||||
---
|
||||
|
||||
## v0.39.x — Extension Track Continuation
|
||||
## v0.38.x — Extension Track Continuation
|
||||
|
||||
Resumes the extension track (v0.29–v0.31 ✅) with three new platform
|
||||
primitives: multi-file Starlark packages, extension connections, and library
|
||||
packages. See design docs for full specifications.
|
||||
primitives: multi-file Starlark packages, extension connections, and
|
||||
library packages. Culminates in a git-board rewrite that validates the
|
||||
entire stack. **Must ship before v0.39.x** — dynamic workflows depend
|
||||
on `load()`, connections, and libraries.
|
||||
|
||||
See design docs for full specifications.
|
||||
|
||||
| Version | Summary | Design Doc |
|
||||
|---------|---------|------------|
|
||||
| v0.39.0 | Multi-file Starlark | [DESIGN-MULTI-FILE-STARLARK.md](DESIGN-MULTI-FILE-STARLARK.md) — `load()` support, disk-based scripts, package-scoped loader. Prerequisite for libraries. 5 backend changesets. |
|
||||
| v0.39.1 | Extension Connections | [DESIGN-EXT-CONNECTIONS-LIBRARIES.md](DESIGN-EXT-CONNECTIONS-LIBRARIES.md) Part 1 — `ext_connections` table, scoped CRUD (personal → team → global resolution), `connections` Starlark module, 3 management UIs. |
|
||||
| v0.39.2 | Library Packages | Part 2 — `library` package type, `ext_dependencies` table, `lib.load()` with per-library permission context, dependency resolution, uninstall protection. |
|
||||
| v0.39.3 | Full Composition | Part 3 — Libraries declare connection types for consumers, reference `gitea-client` library, migrate `git-board` to library-backed surface. |
|
||||
| v0.38.0 | Multi-file Starlark | [DESIGN-MULTI-FILE-STARLARK.md](DESIGN-MULTI-FILE-STARLARK.md) — `load()` support, disk-based scripts, package-scoped loader. Prerequisite for libraries. 5 backend changesets. |
|
||||
| v0.38.1 | Extension Connections | [DESIGN-EXT-CONNECTIONS-LIBRARIES.md](DESIGN-EXT-CONNECTIONS-LIBRARIES.md) Part 1 — `ext_connections` table, scoped CRUD (personal → team → global resolution), `connections` Starlark module, 3 management UIs. |
|
||||
| v0.38.2 | Library Packages | Part 2 — `library` package type, `ext_dependencies` table, `lib.load()` with per-library permission context, dependency resolution, uninstall protection. |
|
||||
| v0.38.3 | Full Composition | Part 3 — Libraries declare connection types for consumers, reference `gitea-client` library. |
|
||||
| v0.38.4 | Git-board Rewrite | Capstone validation — rewrite git-board as multi-package, multi-platform extension (Gitea/GitLab/GitHub). Proves the entire extension architecture works end-to-end. Reference implementation for future extension authors. |
|
||||
|
||||
---
|
||||
|
||||
## v0.39.x — Workflow Product Maturity
|
||||
|
||||
See [ROADMAP-0.39](Workflow/ROADMAP-0.39.md) for full version plan.
|
||||
|
||||
Dual workflow architecture: **simple** (static stages, fixed forms,
|
||||
declarative rules) and **dynamic** (Starlark-driven branching, API-backed
|
||||
pre-screening, tailored data collection). A single workflow graph can
|
||||
mix both types.
|
||||
|
||||
Depends on: v0.38.x (dynamic stages require `load()`, connections,
|
||||
and libraries for external API calls and reusable logic).
|
||||
|
||||
### Stage Graph Architecture
|
||||
|
||||
Three node types in the workflow graph:
|
||||
|
||||
- **Simple stage** — declarative form, fixed fields, built-in renderer.
|
||||
Team admins author these visually (form builder).
|
||||
- **Dynamic stage** — Starlark hook runs at entry, returns form
|
||||
config/routing based on customer data. Developers author these.
|
||||
- **Automated stage** — no UI, Starlark execution only (API calls,
|
||||
data transforms, pre-screening). Invisible to visitors.
|
||||
|
||||
**Branching:** layered approach — declarative rules (`if customer.type
|
||||
== enterprise → stage A`) for simple cases, optional Starlark hook for
|
||||
complex branching logic. Progressive complexity.
|
||||
|
||||
**Visitor surface:** standalone portal (branded URL, no chat chrome).
|
||||
The portal renders whatever the current stage dictates — it doesn't
|
||||
care whether the stage config came from static definition or Starlark.
|
||||
|
||||
### Version Plan
|
||||
|
||||
| Version | Summary | MVP Role |
|
||||
|---------|---------|----------|
|
||||
| v0.39.0 | Stage Graph Engine + Form Builder | **Blocker** — graph execution engine with simple/dynamic/automated node types; visual field editor replaces JSON textarea |
|
||||
| v0.39.1 | Stage Reorder + Bulk Ops | DnD reorder, multi-select operations |
|
||||
| v0.39.2 | SLA Alerting | Scheduled scanner, breach notifications |
|
||||
| v0.39.3 | Visitor Portal | Standalone branded portal, progress indicator, email notifications, session resume |
|
||||
| v0.39.4 | Workflow Templates + Clone | Built-in templates, deep copy |
|
||||
| v0.39.5 | Analytics Dashboard | Throughput, cycle time, SLA compliance |
|
||||
|
||||
---
|
||||
|
||||
## v0.40.x — Polish
|
||||
|
||||
Bug hunt, dead code hunt, stabilization. As many sub-versions as
|
||||
needed to reach a polished MVP-ready product. May pull in features
|
||||
from ongoing stakeholder meetings.
|
||||
|
||||
- [ ] UI bug fixes
|
||||
- [ ] Dead code removal
|
||||
- [ ] Performance audit
|
||||
- [ ] Accessibility pass
|
||||
- [ ] Additional features TBD from stakeholder input
|
||||
|
||||
---
|
||||
|
||||
@@ -294,13 +347,19 @@ on a 3-node cluster. An IT team can operate the platform without
|
||||
reading Go source code. Team admins build workflows visually.
|
||||
|
||||
**Requires all of:**
|
||||
- Extension track through v0.31.2 (full package ecosystem, visual
|
||||
workflow builder, SDK-based surfaces, team workflow self-service)
|
||||
- Extension track through v0.31.2 (package ecosystem, SDK-based
|
||||
surfaces, team workflow self-service) ✅
|
||||
- Operations track through v0.34.0 (multi-replica HA, observability,
|
||||
data portability) ✅
|
||||
- Workflow product v0.35.0 (form rendering, data pipeline, conditional
|
||||
routing, structured review, monitoring dashboard)
|
||||
- Full OpenAPI spec v0.36.0 (complete API documentation for all domains)
|
||||
routing, structured review, monitoring dashboard) ✅
|
||||
- Full OpenAPI spec v0.36.0 (complete API documentation) ✅
|
||||
- UI rewrite v0.37.x (Preact+htm migration, all surfaces) ✅
|
||||
- Extension continuation v0.38.x (multi-file Starlark, connections,
|
||||
libraries, git-board rewrite)
|
||||
- Workflow maturity v0.39.x (stage graph engine, simple + dynamic
|
||||
workflows, visitor portal, analytics)
|
||||
- Polish v0.40.x (bug hunt, dead code, stabilization)
|
||||
|
||||
**Additionally requires:**
|
||||
- [ ] Deployment guide: step-by-step for IT team (PG cluster,
|
||||
|
||||
Reference in New Issue
Block a user