backlog(B-0571): GitHub App for factory automation — separate API rate-limit pool#3951
Merged
Merged
Conversation
…mit pool Sibling row to B-0570 (scarcity tracker). The primary capacity-mitigation for the 5000/hr per-user GitHub API saturation Aaron flagged today. GitHub Apps have separate rate-limit pools designed for automation, with clean [bot] attribution. Installation auth token rotates ~1hr (handled by token-rotation logic). Factory automated agents (peer Otto bg worker, Lior antigravity, scheduled routines) auth via the App; human contributors keep using PATs. 7-slice decomposition: App creation → install → token-fetch script → rotation/caching → agent migration (Otto, Lior) → docs + scarcity-tracker integration. Composes with B-0570 (scarcity tracker — visibility layer for the pools this row expands). Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Files a P2 backlog row designing a "Zeta-Factory" GitHub App installation to give automated agents a separate API rate-limit pool from human-user PATs, as a primary mitigation for the shared-bucket saturation surfaced in sibling row B-0570.
Changes:
- Adds
docs/backlog/P2/B-0571-*.mddesign row with acceptance criteria, 7-slice decomposition, design sketch, alternatives table, and open questions. - Updates
docs/BACKLOG.mdgenerated index with the new B-0571 entry under P2.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/backlog/P2/B-0571-github-app-factory-automation-2026-05-16.md | New per-row backlog file (118 lines) describing the GitHub App proposal. |
| docs/BACKLOG.md | Generated index line for B-0571 added under P2. |
This was referenced May 16, 2026
This was referenced May 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Sibling row to B-0570 (scarcity tracker). Primary capacity-mitigation for the per-user GitHub API saturation flagged today. Files the design row for a "Zeta-Factory" GitHub App installation on the LFG repo, with installation-token auth replacing PAT auth for automated agent work.
Why
GitHub Apps have separate rate-limit pools designed for automation (vs the shared per-user 5000/hr bucket that saturated today across 3-4 concurrent agents). Plus clean `[bot]` attribution. Plus least-privilege permissions scope.
Per the mitigation-axes table in B-0570: this is the substrate-honest primary mitigation. Tier audit (B-0572) is the cheaper test (free 3× if LFG is already Enterprise); App is the architectural answer.
Diff
Acceptance highlights
Composes with
🤖 Generated with Claude Code