Preview mode — rich sample data is shown here so you can see the Hermes Brain flow before connecting your own project.
Operate
Hermes controller
See what woke Hermes, which evidence it considered, which bounded action it selected, and the policy receipts that allowed or stopped automation.
Illustrative hosted preview. These records demonstrate the complete operating cycle and are never written into an installed workspace. Local Loopgraph shows only the opportunities, decisions, measurements, and value created from your own Hermes events.
Controller
Enabled
saved policy
Runs
2
Durable decision receipts
Decisions
3
Across loaded runs
Stopped by policy
2
Hermes abstained safely
Pending triggers
2
0 failed
Controller policy
The controller may design and rehearse automatically, but it cannot silently promote sensitive or unapproved work.
- Qualify opportunity
- 45 / 100
- Start Hermes design
- 65 / 100
- Allow shadow materialization
- 80 / 100
- Auto-start design
- On
- Auto-evaluate outcomes
- On
- Auto-shadow
- On
Never auto-shadow
Operations financeHR talentLegal compliance
Last durable checkpoint: Jul 28, 5:45 PM
Outcome window · Completed
measurement:activation_7d · Jul 28, 5:40 PM
Start designPolicy passed
Design a Product activation recovery loop.
The opportunity score exceeded the auto-design threshold with sufficient product and CRM evidence.
Review changeHermes abstained
Wait for product-owner approval before graph mutation.
Every graph change requires an accountable approval receipt.
- Stopped: Explicit graph approval has not been recorded.
Connector health · Completed
connection:notion-content · Jul 28, 3:30 PM
Request evidenceHermes abstained
Keep Content Creation in shadow mode.
Publishing evidence is stale and the primary outcome window is incomplete.
- Stopped: Primary metric evidence is incomplete.
- Stopped: Connection health is stale.