Graph gallery

Make the route visible.

These are illustrative design patterns, not downloadable shipped templates or turnkey integrations. Each uses behaviors Ravenroot can model; real endpoints, credentials, policies and extensions remain the integrator’s responsibility.

Personal automation

Small routines with explicit edges.

Start with deterministic transforms and guarded actions. Every step stays visible when the routine grows.

Morning brief graph that collects updates, handles failures, branches on priority, formats and delivers a brief, records a quiet day, and completes — PERSONAL · REAL RAVENROOT UI · DAGRE / HIERARCHYMorning brief with priority, quiet-day and unavailable paths.

Pattern 01

Priority notification

HTTP

Receive event

CEL

Normalize

DECISION

Is urgent?

ACTION

Notify

Use a checked condition to keep low-priority items on a quiet route and allowlist the notification endpoint for the action route.

Pattern 02

Weekly digest builder

INPUT

Items

CEL

Filter

TEMPLATE

Format

LOG

Record

A bounded transform and template can prepare text without requiring a model provider. Delivery remains a separately controlled action.

Enterprise automation

Decision paths operators can explain.

Separate validation, routing and side effects so controls are reviewable at the node and deployment boundaries.

Incident response graph with normalization, severity routing, context gathering, evidence, approval, remediation and escalation, exception and completion paths — ENTERPRISE · REAL RAVENROOT UI · ELK / ORTHOIncident response with explicit approval and exception routes.

Pattern 03

Order exception routing

INGEST

Order event

CEL

Validate

FAN-OUT

Route outcome

HTTP

Controlled action

Outcome edges can separate normal, review and error paths. The HTTP node remains constrained by host and tool allowlists.

Pattern 04

Multi-source readiness check

BRANCH

Start checks

HTTP

Query systems

JOIN ALL

Correlate

DECISION

Proceed?

Basic correlated all/any fan-in exists, with documented limitations. Do not treat it as distributed coordination or advanced quorum handling.

Pattern 05

Governed AI handoff

CLASSIFY

Policy check

AGENT

Bounded objective

RESULT

Validate

ACTION

Route

Conceptual only until an integrator supplies and configures an AgentRuntime. Ravenroot ships no agent implementation and performs no autonomous planning itself.

Pattern 06

Audit-friendly transformation

INPUT

Payload

CEL

Transform

LOG

Record

SSE

Observe

Keep bounded data manipulation in checked CEL, then follow correlated execution transitions through the activity stream and structured logs.