Bezel Workflow architecture-spec
internal prototype · canonical JSON + Dreamborn Forge HTML
internal generated
architecture-spec · supabase_json

Bezel Workflow architecture-spec

architecture-spec artifact · for Bezel Workflow · status draft

Components
  • Flow Definition: name: string, purpose: string
  • Router Agent / Flow Engine: name: string, purpose: string
  • Topic-Based Pull Queues: name: string, purpose: string
  • Role per Integration: name: string, purpose: string
  • Connector Agents: name: string, purpose: string
  • Credential Vault: name: string, purpose: string
  • Completion Event Stream: name: string, purpose: string
  • Observability and Audit: name: string, purpose: string
Execution Model
  • bezel flow: 5 items
  • temporal contrast: Temporal uses worker pull queues but trigger/state-change orchestration. Bezel uses pull semantics in both execution and control planes.
Open Questions
  • Whether MVP vault is GCP Secret Manager, Cloudflare Secrets, or a thin abstraction over both.
  • How much self-healing is allowed to happen autonomously before requiring human approval.
  • Whether HCS claim proofs are exposed in V1 product UI or kept as internal audit infrastructure.