Skip to content

Backlog

Maintained by: Product Owner (priorities) + Lead Architect (specs).

✅ Done

  • M1 — Dynamic Triggers — $schedule/$unschedule, system actor, external watcher.
  • v0.1 Cleanup — legacy runtime-name purge, WASM single-source, SQL parameterized, parity proof in CI.
  • Workflow DSL v2 runtime integration — explicit states/actions, current state helpers, terminal metadata, v2 process_event execution.
  • Canonical workflow paths — $path identity, namespace-scoped runtime lookup, canonical spawn refs, path-aware API/Admin/editor.
  • Bootstrap cleanup — only system/bootstrap visible; non-system registry bootstrap governance is internal.
  • Editor v0.2.0 — persistent Filetree, Graph/JSON tabs, Preferences, polished JSON editor, graph auto-fit, workspace export/import.
  • Workspace export/import v1 — platform exports selected workspace to folder/ZIP; standalone opens folder/ZIP.

🔵 Next

Workspace Save/Deploy with baseline diff

Problem: The editor can export/import workspaces and edit in memory, but it cannot yet save changed files back to disk or deploy changed workflows through a reviewed diff.

Required design: follow workflow-workspace-editor-spec.md.

Scope:

Slice Outcome
Store interfaces Shared WorkflowWorkspaceStore, BrowserWorkspaceStore, baseline store abstractions
Diff core Compare current vs baseline by $path; statuses: added/changed/unchanged/deleted
Change review Mandatory dialog before Save/Deploy; deleted reported but not applied in v1
Standalone Save Workspace Write only added/changed files back to filesystem after review
Embedded Deploy Workspace Submit only added/changed workflows through signed process_event events

Guardrails:

  • no raw DB writes,
  • no whole-workspace deploy/write when only one file changed,
  • no deletion in v1,
  • validation before diff action,
  • baseline/current model preserved.

📋 Later

  • Workflow lifecycle/versioning — immutable workflow versions and decision-time rule preservation.
  • Dynamic governed namespace creation — create namespace registries through governed system workflows.
  • Workflow deployment approval — second-review gate for workflow changes.
  • M2 — Audit completeness — verify_chain(process_id), evidence export, standalone verify CLI.
  • M3 — Key storage split — Ed25519 key in sessionStorage or stronger isolated tier; JWT separate.
  • M4 — Screening & case management.
  • M5 — Regulatory reporting.