Skip to content

scope.md

Latest commit

 

History

History
36 lines (26 loc) · 1.18 KB

scope.md

File metadata and controls

36 lines (26 loc) · 1.18 KB

Scope

github-agent-bridge is intentionally GitHub-only.

Boundary

flowchart TD
    A[Mailbox] --> B[Generic inbox worker]
    A --> C[GitHub Agent Bridge]

    B --> B1[ordinary email triage]
    B --> B2[calendar invites]
    B --> B3[reminders/status emails]

    C --> C1[classify GitHub notification]
    C --> C2[enqueue durable GitHub job]
    C --> C3[coalesce per owner/repo#number]
    C --> C4[react 👀]
    C --> C5[dispatch OpenClaw agent work]
Loading

Rules

Rule Reason
Do not become a generic inbox assistant. Keeps policy, safety, and failure modes narrow.
Do not mutate non-GitHub mail. Prevents accidental mailbox side effects.
Keep generic email logic elsewhere. Calendar/status/personal triage has different semantics.
Accept delegated GitHub messages from another worker. Allows a future single IMAP owner if needed.

Mailbox ownership

The bridge may scan the same mailbox with its own high-water cursor, but it must only mutate GitHub notification messages.

If a generic worker becomes the sole IMAP owner later, it can call gab enqueue-json for GitHub messages instead of letting the bridge read IMAP directly.