A compact map of the github-agent-bridge documentation set.
| Need | Document | Type |
|---|---|---|
| Understand what this project is | ../README.md |
Overview |
| Install a deployment | installation.md |
How-to |
| Understand system design | architecture.md |
Explanation |
| Configure policy | policy-reference.md |
Reference |
| Roll out safely | shadow-canary.md |
How-to |
| Operate production | operations.md |
How-to |
| Configure dashboard GitHub OAuth | dashboard-github-oauth.md |
How-to |
| Develop the bridge | development.md |
How-to |
| Diagnose known failures | failure-modes.md |
Reference |
| Understand release automation | releases.md |
Reference |
| Keep scope clean | scope.md |
Explanation |
flowchart TD
A[Scope] --> B[Architecture]
B --> I[Installation]
I --> C[Policy]
C --> D[Shadow/canary rollout]
D --> E[Operations]
B --> F[Development]
F --> G[Releases]
E --> H[Failure modes]
- Keep reference documents factual and table-driven.
- Keep how-to documents task-oriented and procedural.
- Keep explanation documents focused on why the system exists and how pieces relate.
- Do not bury operational warnings inside long prose; use callouts and checklists.