GitHub issue automation
Start from a GitHub issue event, normalize it, select work from the Project queue, claim it with a short-lived lock, and dispatch an agent run with branch and session metadata.
Project issue selectionGuides
Start with the workflows Rainrail is being built to operate.
These guides describe the first operational paths at a high level and link into the repository contracts that implementation work should follow.
First workflowsIssue intake, manual/chat input, review follow-up, and Cloudflare reporting.
Initial guides
Manual and chat intake
Publish operator-entered manual prompts or web chat messages as first-party source events that use Core intake and replay without going through the legacy EEP Bridge bundle.
Manual source contractPR review loop
Use pull request and review events as neutral workflow inputs, then route review follow-up into the same task and runtime provider boundaries used for issue automation.
Workflow plugin contractCloudflare event reporting
Deploy the Worker bridge, register required secrets, publish Cloudflare tail or error events, and smoke test health without committing operational credentials.
Cloudflare Worker operationsHow to read the guides
Treat product-site guide pages as orientation. When a guide affects payload shape, Project queue locking, provider auth, retry behavior, or capability-gated actions, the linked docs are the implementation source of truth.