Concepts

The vocabulary for routing provider events into agent workflows.

Rainrail keeps source systems, workflow decisions, and agent runtimes in separate contracts so automation can grow without turning every adapter into a one-off script.

Source pluginNormalizes provider input.
RainrailEventEnvelopeStabilizes delivery, source, subject, and payload metadata.
Workflow pluginChooses the deterministic automation path.
Runtime providerStarts the agent run behind capability gates.

Initial concept map

RainrailEventEnvelope

The neutral event shape that carries a schema version, source identity, delivery metadata, subject, normalized payload, and a raw payload reference.

Source plugin

The boundary that accepts provider-specific input, such as GitHub webhooks or Cloudflare tail events, and normalizes it into a RainrailEventEnvelope.

Workflow plugin

The routing unit that accepts neutral events and maps them to task provider calls, runtime starts, or local deterministic decisions.

Runtime provider

The adapter for starting or resuming agent runs in OpenClaw, devteam, Codex, or another execution backend without exposing runtime secrets to workflows.

Task and queue providers

Provider adapters keep GitHub issue operations and Project queue selection behind stable methods so workflow logic does not depend on GraphQL details.

Bridge room

The event bus layer that keeps publish, replay, SSE delivery, and duplicate delivery handling observable for agents and operators.

Implementation references

This page is a product-facing map. The exact payload fields, plugin API signatures, capability gates, and Bridge room replay behavior stay in the engineering docs.