Product Department Loop
5 managed loops
Product decisions start from validated customer pain instead of scattered requests.
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.
Non-secret route plan derived from materialized routing contracts.
Each department loop manages specific workflow loops and rolls evidence back into the company brain.
5 managed loops
Product decisions start from validated customer pain instead of scattered requests.
5 managed loops
More qualified activated or paying customers from channels that can scale without degrading cohort quality.
7 managed loops
At-risk revenue gets faster human attention without generic customer communication.
5 managed loops
Sales spends time on accounts with real potential and clear next actions.
6 managed loops
Maintainers spend less time sorting issues while security-sensitive items reach the right owner faster.
5 managed loops
Operational work moves faster without bypassing policy or audit requirements.
5 managed loops
Hiring teams reduce candidate drop-off and make decisions with better evidence.
5 managed loops
Contract review cycles speed up while legal judgment stays focused on material risk.
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.