One event. A tree of consequences.

Something happens in your system. Provenance logs it, builds the interaction tree, and fires notifications as branches. Metric alerts watch the patterns independently. Two systems, one operational history.

💳

Fintech

A payment fails at the gateway

A customer attempts to pay. The payment flows through checkout, fraud detection, and the gateway — then fails. Subscriptions fire notifications as part of the tree. Alerts monitor the broader pattern.

Interaction TreeUOW a3f8c2d1

Subscription renewal triggered
billing-svc

Fraud check passed
fraud-svc

Payment submitted to Stripe
payment-gateway

Card declined — expired
stripe-api

📨"Your payment failed — update your card"
→ customer via SendGrid

📨"Payment failure: usr_42, card expired"
→ Slack #payments

📨Retry logic triggered
→ AWS Lambda (auto-retry)

📨 nodes = subscription-triggered notifications (part of the UOW tree)

Metric Alerts — monitoring this workflow

🚨

PAYMENT/FAILED count > 5 in 2 minutes

→ PagerDuty on-call engineer

🎯

Daily revenue reaches $10,000 target

→ Slack #leadership

📉

Payment success rate drops below 95%

→ Email → CFO + Slack #finance

Alerts evaluate metrics over time — they're not triggered by a single event but by patterns and thresholds.

Takeaway: Subscriptions react to individual events (email the customer, notify Slack, trigger a Lambda retry). Alerts watch the aggregate (failure rate, revenue targets). Both work together — different mechanisms, same data.

📦

Logistics

An order moves through fulfillment

A customer places an order. It flows through payment, inventory, packing, and shipping. Subscriptions notify the customer at each stage. Alerts watch for stuck orders and volume milestones.

Interaction TreeUOW b7e4f1a9

Order placed — 3 items, $249.99
web-store

📨"Order confirmed! Receipt attached."
→ customer via SendGrid

Payment captured
payment-svc

Inventory reserved
warehouse-api

Packed and labeled
warehouse-api

Handed to carrier
shipping-api

📨"Your order shipped! Track here."
→ customer via SMS webhook

Delivery failed — address not found
carrier-webhook

📨"Delivery issue — rescheduling"
→ customer via SendGrid

📨"Failed delivery: ord_b7e4"
→ Slack #ops

📨Create support ticket
→ JIRA (webhook subscriber)

📨 nodes = subscription-triggered notifications (part of the UOW tree)

Metric Alerts — monitoring this workflow

⏰

ORDER/PLACED with no SHIPMENT/SHIPPED after 48 hours

→ Slack #ops + JIRA ticket

🎯

1,000 orders this month

→ Slack #wins + Discord #team

📉

Delivery failure rate > 5%

→ Email → Head of Logistics

Alerts evaluate metrics over time — they're not triggered by a single event but by patterns and thresholds.

Takeaway: The customer gets proactive updates at every stage (subscriptions in the tree). Operations gets alerted on systemic issues (metric alerts watching patterns). JIRA tickets are created automatically via webhook subscribers.

🚀

Platform Engineering

A deploy causes an error spike

CI/CD deploys a new version. Subscriptions notify the team. When errors spike, an AWS Lambda auto-correlates the deploy. Alerts watch error rates and trigger rollbacks.

Interaction TreeUOW c9d2e5f3

Build completed — v2.4.1
github-actions

Deployed to production
k8s-controller

📨"Deploy v2.4.1 live ✓"
→ Slack #deploys

📨Trigger post-deploy smoke tests
→ AWS Lambda (test-runner)

Health check passed
k8s-controller

Error rate spike: 12x baseline
error-tracker

📨Auto-correlate with recent deploys
→ AWS Lambda (correlator)

📨"Error spike — likely caused by v2.4.1"
→ Slack #platform

📨Create incident
→ JIRA (webhook)

📨 nodes = subscription-triggered notifications (part of the UOW tree)

Metric Alerts — monitoring this workflow

🚨

ERROR count > 10 within 5 min of any DEPLOYMENT/COMPLETED

→ PagerDuty on-call + auto-rollback Lambda

📊

Deploy frequency drops below 2/week

→ Slack #engineering-leads

⏱️

Mean time to recovery (MTTR) exceeds 30 min

→ Email → VP Engineering

Alerts evaluate metrics over time — they're not triggered by a single event but by patterns and thresholds.

Takeaway: Subscriptions handle immediate reactions (notify Slack, run smoke tests, correlate errors via Lambda). Alerts handle thresholds (error rate, deploy frequency, MTTR). The Lambda subscribers add custom logic without changing your deploy pipeline.

📡

Telco / IoT

A SIM activation stalls mid-provisioning

A customer buys a SIM. Activation triggers identity checks, network provisioning, billing, and device config. Subscriptions keep the customer informed. Alerts watch activation success rates.

Interaction TreeUOW d4a7b8c2

SIM activation requested
retail-pos

📨"Welcome! Activating your SIM."
→ customer via SMS (webhook)

Identity verified (KYC)
kyc-service

Network profile created
network-mgmt

Billing account provisioned
billing-api

Device config push — timeout
device-mgmt

📨"Activation delayed — working on it"
→ customer via SMS (webhook)

📨Retry config push
→ AWS Lambda (retry-handler)

📨"Config timeout: device_mgmt"
→ Discord #noc

📨 nodes = subscription-triggered notifications (part of the UOW tree)

Metric Alerts — monitoring this workflow

🚨

Config push timeout > 3 in 5 minutes

→ PagerDuty NOC team

🎯

500 activations in a day (new record)

→ Slack #growth + email → CEO

📉

Activation success rate < 90%

→ Email → Head of Network Ops

Alerts evaluate metrics over time — they're not triggered by a single event but by patterns and thresholds.

Takeaway: Subscriptions handle per-event reactions (SMS the customer, retry via Lambda, notify Discord). Alerts watch the fleet-level health (timeout patterns, activation rates, volume milestones).

🏥

Healthcare

A nurse accesses sensitive patient data

A nurse logs in and accesses records. Every access is logged as an interaction. Subscriptions handle patient notifications. Alerts watch for unusual access patterns.

Interaction TreeUOW e5f1a3b7

Session started — Nurse Williams
auth-svc

Patient record accessed: #PT-4521
ehr-system

Lab results viewed
lab-api

Prescription created — Amoxicillin
pharmacy-svc

📨"Prescription ready for pickup"
→ patient via SMS (webhook)

📨Update pharmacy queue
→ AWS Lambda (queue-mgr)

📨Log access for compliance
→ compliance webhook

📨 nodes = subscription-triggered notifications (part of the UOW tree)

Metric Alerts — monitoring this workflow

🚨

50+ record accesses in 10 min by single user

→ Security team via email + Slack

📋

Monthly compliance export due

→ Email → Compliance Officer

⚠️

After-hours access to restricted records

→ Slack #security + audit flag

Alerts evaluate metrics over time — they're not triggered by a single event but by patterns and thresholds.

Takeaway: Subscriptions handle per-event compliance logging and patient notifications. Alerts watch for anomalous patterns (bulk access, after-hours activity). The audit trail builds itself — no separate system needed.

Two systems. One operational history.

Subscriptions react to individual events — they're branches in the tree. Send emails, trigger Lambdas, post to Slack, create JIRA tickets.

Alerts watch patterns over time — they're independent monitors. Threshold breaches, rate changes, goal milestones.

Together, they give you complete operational intelligence.

Start growing your tree.

One SDK call. One interaction. Subscriptions and alerts take care of the rest.

No credit card required. Free tier forever.