Workflow visibility without workflow noise.
SherryGeaux stages automation complexity instead of celebrating it. The graph still exists. It just stops greeting humans before the promise, the policy, and the risk.
Current automation
Trust markers
Portfolio health, confidence, and next-right action.
The first screen should answer what exists, what is healthy, what is failing, and where attention belongs now.
Automation portfolio
Attention queue
A calm explanation of what the automation does.
Phases are semantic blocks, not a wall of nodes. The user sees purpose, sequence, and trust before they ever see mechanics.
Lead Routing
Phases
Inputs and outputs
Readable logic instead of branch anxiety.
Branches should read as policy. The user should understand the rule before ever thinking about a router or conditional node.
Routing rules
| Priority | Rule | Condition | Action |
|---|
Operational truth, diffs, and recovery.
Recent runs, what changed, where the failure happened, and the one move that restores momentum without panic.
Recent runs
Selected run detail
The machine room, deliberately demoted.
Raw mappings, payload fragments, and implementation notes remain available, but they never take over the first conversation.
Substrate summary
Why this stays in the basement
- The engine is powerful, but power should not be confused with interface quality.
- Operators need trust, policy, and visibility before they need payloads and expressions.
- Deloudification means implementation detail becomes an expert drill-down, not the front door.