Functionality is determined by the presence of a folder inside .github-intelligence. If a folder exists, that intelligence is available. If it does not, it is not. There are no hidden configuration files, no opaque service registrations, no runtime feature flags — just folders.
Read the full design philosophy in .ASPIRATION.md.
The .github-intelligence folder is the orchestrator. It contains all intelligence folders and discovers which are present, activating only those that exist.
Folders prefixed with github-intelligent- (inside .github-intelligence) hook directly into GitHub surfaces:
| Folder | GitHub Surface |
|---|---|
github-intelligent-action |
GitHub Actions — the compute engine |
github-intelligent-branch |
Branches and branch protection rules |
github-intelligent-code-review |
Structured code reviews |
github-intelligent-codespace |
GitHub Codespaces — cloud development environments |
github-intelligent-commit |
Commits — the immutable audit trail |
github-intelligent-deployment |
Environments and staged rollouts |
github-intelligent-discussion |
GitHub Discussions — long-form Q&A and RFCs |
github-intelligent-fork |
Forks — upstream/downstream collaboration |
github-intelligent-issue |
GitHub Issues — the primary conversation interface |
github-intelligent-label |
Labels — classification and routing |
github-intelligent-mention |
@mentions — cross-surface invocation |
github-intelligent-milestone |
Milestones — planning, progress tracking, and goal management |
github-intelligent-notification |
Notifications — smart digests and summaries |
github-intelligent-package |
GitHub Packages — container and package registry |
github-intelligent-page |
GitHub Pages — documentation and dashboards |
github-intelligent-project |
GitHub Projects (v2) — project management |
github-intelligent-pull-request |
Pull requests — the full PR lifecycle |
github-intelligent-reaction |
Reactions — feedback signals and indicators |
github-intelligent-release |
Releases and tags — changelogs and versioning |
github-intelligent-repository |
The repository itself — runtime and storage |
github-intelligent-security |
Security — scanning, audits, and secret detection |
github-intelligent-sponsor |
GitHub Sponsors — funding and sponsorship management |
github-intelligent-star |
Stars and watchers — community engagement and social signals |
github-intelligent-team |
Teams — organization team management and access control |
github-intelligent-wiki |
GitHub Wikis — knowledge bases and decision logs |
Folders prefixed with github-intelligence- (inside .github-intelligence) operate above individual GitHub surfaces, providing coordination, infrastructure, and cross-cutting concerns:
| Folder | Purpose |
|---|---|
github-intelligence-analytics |
Cross-intelligence analytics, metrics, and insights |
github-intelligence-bridge |
Bridges between GitHub events and the agent system |
github-intelligence-cron |
Scheduled, periodic task execution |
github-intelligence-dashboard |
Real-time activity monitoring |
github-intelligence-emergency |
Emergency response — incident detection and crisis automation |
github-intelligence-guardrail |
Safety enforcement and constraint validation |
github-intelligence-health |
System health monitoring and diagnostics |
github-intelligence-knowledge |
Knowledge base and persistent memory layer |
github-intelligence-plugin |
Plugin system for extending capabilities |
github-intelligence-swarm |
Multi-agent coordination and swarm intelligence |
- Presence is permission. A folder inside
.github-intelligenceis a visible, auditable signal. - Absence is denial. If a folder does not exist, that intelligence does not exist.
.github-intelligenceis the truth. Look inside the.github-intelligencefolder and you know exactly what intelligences are active.