Bezel Workflow flow-schema
flow-schema artifact · for Bezel Workflow · status draft
flow-schema artifact · for Bezel Workflow · status draft
No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.
- kind: flow-schema
- repo: /Users/justinking/Vaults/Projects/bezel-api
- project: Bezel Workflow
- purpose: FLOW.json is the human-product source of truth compiled into agent-readable runtime plans. It is above today’s low-level PlanIntake task graph.
- created by: atlas-codex
- updated at: 2026-05-09T13:17:30.522Z
- draft schema: id: string, name: string, steps: object, status: string, trigger: object, version: number, terminal: object, variables: object, observability: object, workspace_ref: string
- schema version: flow-schema.v1
- source memory id: 99edd8d2-5780-43a2-bbd0-03982353768a
- architecture decision ref: 3a1bb081-67f9-41ae-9600-a91fbb14ecda
- required compiler behavior: 5 items
- unresolved schema questions: 3 items
Machine-readable source fields
flow-schema
/Users/justinking/Vaults/Projects/bezel-api
Bezel Workflow
FLOW.json is the human-product source of truth compiled into agent-readable runtime plans. It is above today’s low-level PlanIntake task graph.
atlas-codex
2026-05-09T13:17:30.522Z
flow_customer_invoice_processing_v1
Invoice Processing Fan-Out
| id | role | type | input | retry | action |
|---|---|---|---|---|---|
| extract_invoice | roles.invoice.extractor | agent_task | - source: {{trigger.body}} | - backoff: exponential - max attempts: 2 | extract.invoice_fields |
| fanout_update_hubspot | roles.hubspot | connector_action | - invoice: {{steps.extract_invoice.output}} | company.update_or_create_note | |
| fanout_write_sheet | roles.google_sheets | connector_action | - row: {{steps.extract_invoice.output}} | row.append | |
| fanout_send_email | roles.gmail | connector_action | - invoice: {{steps.extract_invoice.output}} - template: invoice_processed | email.send |
draft|active|archived
invoice_received
webhook|schedule|poll|manual|local_event
No structured fields captured.
gmail|google_drive|http|local_file|custom
cred_gmail_ops
schema.invoice_event.v1
1
| action | channel | connector |
|---|---|---|
| message.send | #ops | slack |
- fanout_update_hubspot.completed
- fanout_write_sheet.completed
- fanout_send_email.completed
fail_run|continue_with_warnings|route_to_human
| name | type | source | required |
|---|---|---|---|
| invoice_id | string | trigger.body.invoice_id | true |
No structured fields captured.
true
metadata_only|full|none
workspace id or local workspace alias
flow-schema.v1
99edd8d2-5780-43a2-bbd0-03982353768a
3a1bb081-67f9-41ae-9600-a91fbb14ecda
- Validate IDs are unique and dependencies exist.
- Resolve step roles to workspace roles/queues.
- Compile parallel fan-out as multiple tasks sharing the same dependency.
- Preserve human labels and connector/action refs in safe metadata for timeline rendering.
- Store sensitive input by reference or redacted metadata where possible.
- Whether trigger definitions live inside FLOW.json or as separately versioned Trigger manifests.
- Whether Router Agent decisions are represented as explicit router steps or runtime behavior.
- How loops/map-over-items should be represented without becoming too complex for V1.