Product Department Loop
5 managed loops
Time from recurring feedback to an accountable product theme.
Hermes Brain receives business events, chooses the right Loopgraph loop, and keeps human owners accountable for approvals, blockers, and metrics.
Hermes Brain listens for events, asks Loopgraph for eligible routing cards, chooses the right loop, and records every decision back into Loopgraph.
Provider webhooks, lifecycle callbacks, schedules, and manual events terminate at Hermes before any loop can run.
Hermes receives a normalized envelope and Loopgraph routing cards, then Loopgraph validates the selected route before queueing work.
Approvals, policy exceptions, and customer-facing actions stay accountable to named owners.
Once provider webhooks terminate at Hermes and the router skill submits decisions, this table will show real event receipts, business problems, selected loops, validation state, queue/run status, and correction history. The examples below are illustrative only.
| Example Event | Signal | Expected Route | Human Owner | Rollout |
|---|---|---|---|---|
| feedback.repeated_theme_detected | Support, CRM, and product usage show the same customer pain | Product / Feedback Clustering | Product lead | Shadow → problem brief |
| release.measurement_window_closed | Feature adoption, support load, and release notes are ready | Product / Release Learning | Product lead | Draft learning review |
| campaign.performance_anomaly | CAC rises while qualified conversion falls | Marketing / Ads | Growth lead | Shadow → recommend |
| content.brief_approved | Approved evidence and reviewer arrive from a content system | Marketing / Content Creation | Content lead | Draft for review |
| page.conversion_drop | Ambiguous landing-page signal with missing campaign mapping | Human choice or unhandled problem | Marketing operator | Ask before route |
Grouped by durable business problem, not by duplicate webhook deliveries.
No business problems have been opened by Hermes yet.
Active LoopSpecs Hermes may choose after deterministic eligibility.
No materialized routing cards yet.
Planned contracts plus the last exact, secret-free Hermes controller receipt.
Each department loop manages specific workflow loops and rolls evidence back into the company brain.
5 managed loops
Time from recurring feedback to an accountable product theme.
7 managed loops
Campaign cohorts with complete spend and downstream observation evidence.
10 managed loops
Flagged account risks confirmed by accountable reviewers.
11 managed loops
Flagged opportunities confirmed as requiring intervention.
9 managed loops
Time to an accountable issue disposition.
6 managed loops
Material variance with reconciled and reviewable driver evidence.
5 managed loops
Time a candidate process remains stalled before accountable resolution.
6 managed loops
Time from a complete redline packet to qualified legal disposition.
1 managed loops
A custom operating loop becomes explicit enough to run, review, and improve.
Run the management cron or simulate escalation cases to populate rollup data.
Active loops are producing useful traces. The highest leverage decision is whether to scale the marketing campaign test after downstream quality is verified.
Customer-facing actions require separate approval.
Policy exceptions create accountable review work instead of silent execution.
Escalations keep owner, deadline, confidence, and unresolved questions attached.
Persisted cases from CLI simulate runs in .loopgraph/cases/
Run `npm run loopgraph -- simulate ...` to create typed escalation cases.