Architecture Overview
System Design
CyberAi is designed as a GitHub-native control plane that coordinates AI agents, repositories, and runners in a decentralized ecosystem. The architecture follows a hub-and-spoke model where this repository serves as the central hub.
Core Components
1. Contract Registry
The contract registry (/contracts) contains machine-readable
contracts that define capabilities, requirements, and metadata for all
ecosystem participants.
- Agents: AI services that perform specific tasks
- Repositories: Code repositories that provide functionality
- Runners: Execution environments for agents
2. Prompt Library
The prompt library (/prompts) provides standardized
instructions for operators and agents, ensuring consistent behavior
across the ecosystem.
3. Automation Tools
Tools (/tools) provide operational scripts for:
- Bootstrap: Environment setup and validation
- Audit: Continuous validation and security checks
4. Static Site
The site (/site) serves as the public face of CyberAi,
providing documentation, contract browsing, and API access.
Data Flow
┌─────────────┐
│ GitHub │
│ Actions │
└──────┬──────┘
│
├─→ Bootstrap Tool
├─→ Audit Tool
├─→ Contract Validation
│
v
┌─────────────────┐
│ Contracts │◄─── Agents
│ Registry │◄─── Repositories
└─────────────────┘
│
v
┌─────────────────┐
│ GitHub Pages │
│ (cyberai.net) │
└─────────────────┘ Integration Points
GitHub Actions
Automated workflows handle:
- Contract validation on every commit
- Site deployment to GitHub Pages
- Continuous integration and testing
GitHub Pages
The site is automatically deployed from the main branch's
/site/dist folder after build.
DNS Configuration
Custom domain cyberai.network is configured via CNAME
file and DNS records pointing to GitHub Pages.
Security Model
- Contract Validation: All contracts must pass schema validation
- Audit Tools: Automated security scanning on every commit
- Permissions: Least-privilege access for all components
- Transparency: All operations logged and auditable
Scalability
The system is designed to scale horizontally:
- Static site deployment via CDN (GitHub Pages)
- Decentralized agent execution
- Contract registry as source of truth
- No central server dependencies