implementation-roadmap · supabase_json
Bezel Workflow implementation-roadmap
implementation-roadmap artifact · for Bezel Workflow · status draft
phases
| id | goal | name | outputs |
|---|---|---|---|
| P0 | Lock intent, positioning, competitive landscape, architecture, and demo scope. | Project Framing and Artifact Base | - Studio project - source-thought - intent - competitive-landscape - positioning-spec - architecture-spec - implementation-roadmap |
| P1 | Define machine-first Flow JSON, job payloads, completion events, connector role contracts, retry semantics, and terminal status rules. | Flow Schema and Runtime Contract | - FLOW.json schema - job/completion schemas - contract tests |
| P2 | Use existing Bezel API task/claim runtime to materialize Flow jobs, route to topics/roles, process completions, and fan out/fan in. | Queue and Router MVP | - Router Agent loop - topic/role mapping - parallel fan-out demo - claim expiry/retry integration |
| P3 | Ship first integration roles with credential references and structured outputs. | Connector Foundation | - Gmail connector - Google Sheets connector - HubSpot connector - generic HTTP/webhook connector - connector response contracts |
| P4 | Implement workflow-scoped credential storage with vault references and auditable credential reads. | Credential Vault and Access Logs | - vault abstraction - OAuth callback path - API key secret creation path - credential access log surface |
| P5 | Let users see jobs, claims, completions, retries, failures, and Router decisions in one workflow run timeline. | Observability Surface | - workflow run timeline - integration status cards - failure/retry detail - audit export |
| P6 | Create a simple Flow authoring surface for triggers, sequential steps, parallel fan-out, connector credentials, and terminal actions. | First Workflow Builder | - builder UI - Flow validation - test-run mode - publish/activate mode |
| P7 | Prove Bezel can process a high-volume workflow where one event fans out to multiple connector roles and completes with no lost jobs. | Killer Demo: Invoice Processing Fan-Out | - invoice demo dataset - Airtable/Sheets write - HubSpot update - Gmail send - Router completion dashboard |
| P8 | Demonstrate controlled recovery from an unexpected API response or changed field shape. | Self-Healing Connector Pilot | - drift detector - agent interpretation path - human approval policy - before/after audit trail |
immediate next actions
- Use screen-architecture-spec as UI planning baseline.
- Write workflow-builder-ux-spec for builder shell and step config panel.
- Write run-timeline-ux-spec for executions, claims, Router decisions, redaction, and debug/replay.
- Write connector-config-ux-spec for credentials/connections and self-healing review.
- Keep auth/login/create-account out of Workflow screen scope because API owns that baseline.
Agent Handoff
Start Here
- Use screen-architecture-spec as UI planning baseline.
- Write workflow-builder-ux-spec for builder shell and step config panel.
- Write run-timeline-ux-spec for executions, claims, Router decisions, redaction, and debug/replay.
- Write connector-config-ux-spec for credentials/connections and self-healing review.
- Keep auth/login/create-account out of Workflow screen scope because API owns that baseline.
Completion Evidence
No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.
Phases
- Project Framing and Artifact Base: id: string, goal: string, name: string, outputs: object
- Flow Schema and Runtime Contract: id: string, goal: string, name: string, outputs: object
- Queue and Router MVP: id: string, goal: string, name: string, outputs: object
- Connector Foundation: id: string, goal: string, name: string, outputs: object
- Credential Vault and Access Logs: id: string, goal: string, name: string, outputs: object
- Observability Surface: id: string, goal: string, name: string, outputs: object
- First Workflow Builder: id: string, goal: string, name: string, outputs: object
- Killer Demo: Invoice Processing Fan-Out: id: string, goal: string, name: string, outputs: object
- Self-Healing Connector Pilot: id: string, goal: string, name: string, outputs: object
Immediate Next Actions
- Use screen-architecture-spec as UI planning baseline.
- Write workflow-builder-ux-spec for builder shell and step config panel.
- Write run-timeline-ux-spec for executions, claims, Router decisions, redaction, and debug/replay.
- Write connector-config-ux-spec for credentials/connections and self-healing review.
- Keep auth/login/create-account out of Workflow screen scope because API owns that baseline.
Structured Payload
Machine-readable source fields
kind
implementation-roadmap
phases
| id | goal | name | outputs |
|---|---|---|---|
| P0 | Lock intent, positioning, competitive landscape, architecture, and demo scope. | Project Framing and Artifact Base | - Studio project - source-thought - intent - competitive-landscape - positioning-spec - architecture-spec - implementation-roadmap |
| P1 | Define machine-first Flow JSON, job payloads, completion events, connector role contracts, retry semantics, and terminal status rules. | Flow Schema and Runtime Contract | - FLOW.json schema - job/completion schemas - contract tests |
| P2 | Use existing Bezel API task/claim runtime to materialize Flow jobs, route to topics/roles, process completions, and fan out/fan in. | Queue and Router MVP | - Router Agent loop - topic/role mapping - parallel fan-out demo - claim expiry/retry integration |
| P3 | Ship first integration roles with credential references and structured outputs. | Connector Foundation | - Gmail connector - Google Sheets connector - HubSpot connector - generic HTTP/webhook connector - connector response contracts |
| P4 | Implement workflow-scoped credential storage with vault references and auditable credential reads. | Credential Vault and Access Logs | - vault abstraction - OAuth callback path - API key secret creation path - credential access log surface |
| P5 | Let users see jobs, claims, completions, retries, failures, and Router decisions in one workflow run timeline. | Observability Surface | - workflow run timeline - integration status cards - failure/retry detail - audit export |
| P6 | Create a simple Flow authoring surface for triggers, sequential steps, parallel fan-out, connector credentials, and terminal actions. | First Workflow Builder | - builder UI - Flow validation - test-run mode - publish/activate mode |
| P7 | Prove Bezel can process a high-volume workflow where one event fans out to multiple connector roles and completes with no lost jobs. | Killer Demo: Invoice Processing Fan-Out | - invoice demo dataset - Airtable/Sheets write - HubSpot update - Gmail send - Router completion dashboard |
| P8 | Demonstrate controlled recovery from an unexpected API response or changed field shape. | Self-Healing Connector Pilot | - drift detector - agent interpretation path - human approval policy - before/after audit trail |
project
Bezel Workflow
repo decision
rule
Do not create a separate Bezel Workflow repo yet. Build Workflow and API together while preserving explicit product/runtime boundaries.
canonical repo
/Users/justinking/Vaults/Projects/bezel-api
separation model
- Separate artifacts and product language in Studio.
- Separate package/module boundaries inside the repo where practical.
- Separate human UI/Workflow concerns from runtime API contracts.
- Shared contracts for FLOW.json, claims, events, connector manifests, and credential references.
- Avoid routing local-first Workflow dogfooding through hosted API calls unless the feature explicitly targets hosted/multi-tenant runtime.
future split condition
Only split repos if Bezel Workflow becomes a separately deployed product with a different release cadence or ownership model from Bezel API.
schema version
roadmap.v1
source memory id
99edd8d2-5780-43a2-bbd0-03982353768a
immediate next actions
- Use screen-architecture-spec as UI planning baseline.
- Write workflow-builder-ux-spec for builder shell and step config panel.
- Write run-timeline-ux-spec for executions, claims, Router decisions, redaction, and debug/replay.
- Write connector-config-ux-spec for credentials/connections and self-healing review.
- Keep auth/login/create-account out of Workflow screen scope because API owns that baseline.
screen architecture ref
1d2a8bc9-639a-4f13-8ddb-8808f88d8db8
two world product model
rule
Workflow compiles human-authored Flows into runtime contracts; API/runtime executes agent-readable contracts and emits structured events back to Workflow.
repo model
same repo/build stream, separate product and runtime layers
agent readable product
Bezel API
human readable product
Bezel Workflow
architecture decision ref
3a1bb081-67f9-41ae-9600-a91fbb14ecda
product screen build sequence
- Workflows list
- Workflow builder shell
- Step / connector config panel
- Credentials / connections
- Runs / executions list
- Run detail / timeline
- Agent pool / roles
- Queue / topic monitor
- Debug / replay
- Self-healing review
- Policies / guardrails