Workflow Builder

The Workflow Engine is 80% built. It can match capabilities, orchestrate execution, score confidence, and route escalations. It can do all of this through an API that exactly zero business users will ever touch.

An engine without an interface is a secret. This is the interface.

The Job​

When a business user needs to create, visualise, or adjust an AI-powered workflow — help them build a functional workchart in under 10 minutes, without writing code, without filing a ticket, without waiting for a developer.

The job: "Let me see my automation, build my automation, and trust my automation — without engineering help."

The hidden objection: "Visual builders produce toy workflows that break in production." The answer: this builder doesn't generate workflows from scratch — it composes capabilities from the Workflow Engine's Skill Registry. Every node is a proven, tested, scored capability. The builder is a composition layer, not a code generator.

The Gap​

80% of the power. 0% of the access. That's not an engineering gap — it's a business bottleneck. The engine is a sports car with no steering wheel.

What It Looks Like​

Think process.st for procedures. Zapier for integrations. But for orchestrating AI capabilities with confidence scoring and human escalation built in.

Canvas​

Panels​

Feature / Function / Outcome​

Anti-Goals (v1)​

What the Workflow Builder deliberately does NOT do in the first version.

Saying no to these is the discipline. Each one is a real feature that real users will request. None of them is necessary to prove the core hypothesis: business users can create functional workflows in under 10 minutes.

Business Dev​

The Builder is how the Engine reaches business users. Without it, the Engine sells to developers only.

Commissioning​

Status: 0% built. The Workflow Engine backend is ~80% complete but entirely inaccessible without this interface. This is the highest-leverage UI build in the Mycelium network — it unlocks everything the engine already does.

Metrics​

Risks + Kill Signal​

Kill signal: If average workflow creation takes more than 30 minutes after onboarding, the builder is too complex. The entire value proposition is speed — business users shipping automation faster than they can file a Jira ticket. If the builder can't beat the ticket queue, it's not a tool. It's another interface nobody asked for. Kill and simplify.

Mycelium Capability​

This is the visual workflow editor — the interface layer that makes the Workflow Engine accessible to anyone who can drag a box and draw a line.

Engine without Builder = power without access. Builder without Engine = interface without intelligence. They ship together or they ship nothing.

Dependency​

The Builder depends entirely on the Workflow Engine. Every node in the canvas maps to a Skill Registry entry. Every connection maps to an Orchestrator sequence. Every confidence gate maps to a Confidence Scorer threshold. The Builder doesn't generate logic — it composes engine capabilities visually.

WORKFLOW ENGINE (backend)              WORKFLOW BUILDER (frontend)
─────────────────────────              ────────────────────────────
Skill Registry           ←  reads  ←  Skill Library panel
Capability Matcher       ←  feeds  ←  Task-to-skill suggestions
Orchestrator             ←  maps   ←  Canvas connections
Confidence Scorer        ←  sets   ←  Threshold slider UI
Escalation Router        ←  config ←  Escalation branch editor
Audit Trail              ←  shows  ←  Audit log viewer
Work Receipts            ←  shows  ←  Execution monitor

Build sequence: Engine first (in progress). Builder second (this PRD). Together they form the complete automation capability for the Mycelium network.

Context​

• Phygital Mycelium — The capability network this builder belongs to
• Workflow Engine — The backend brain this builder makes accessible
• ETL Data Tool — Upstream: engine needs clean data, builder needs to show it
• Data Interface — Data access layer the engine queries through
• Commissioning State Machine — Progressive maturity model for tracking builder readiness
• Sales CRM & RFP — First workflow consumer: CRM is the proving ground
• Mushroom Caps — The ventures that build workflows through this interface
• Jobs To Be Done — Demand-side thinking: what progress, not what features
• Flow Engineering — Maps that produce code artifacts
• Standards — Where proven workflow patterns graduate to