Infrastructure services for AFI Protocol
For AI agents and automated contributors: See AGENTS.md for canonical repo constraints, allowed tasks, and safe patch patterns.
Note: If AGENTS.md conflicts with this README, AGENTS.md wins.
afi-infra provides infrastructure-as-code and service definitions for AFI Protocol's core infrastructure components, including:
- T.S.S.D. Vault - Time-Series Signal Database for storing and querying signal history
- Service configurations - Docker, Kubernetes, and cloud service definitions
- Infrastructure utilities - Deployment helpers, health checks, monitoring
✅ Infrastructure-as-Code (Terraform, CloudFormation, etc.) ✅ Service definitions (Docker Compose, K8s manifests) ✅ Database schemas and migrations ✅ Monitoring and observability configs ✅ Infrastructure utilities and helpers ✅ Core infra-level schemas and TSSD-facing types used by AFI services (e.g., signal enrichment, analysis, scoring, and vault records).
❌ Application code (→ afi-core, afi-reactor)
❌ Smart contracts (→ afi-token)
❌ Documentation (→ afi-docs)
Phase 1.5 – infra scaffolding + TSSD v0: core infra definitions, shared schemas, and TSSD vault services are being established.
afi-infra/
├── afi-codex/ # Codex JSON specs for schemas
├── schemas/ # Zod schemas (signal enrichment, analysis, scoring, etc.)
├── src/
│ └── tssd/ # TSSD vault clients and types (canonical)
├── agent-roles/ # Agent role definitions
├── docs/ # TSSD specs and documentation
├── droids/ # Droid configuration files
├── tests/ # Vitest suites, including TSSD and DAG deterministic tests
└── README.md
Factory.ai droids can contribute:
- Infrastructure service definitions
- Database schema designs
- Monitoring and alerting configurations
- Cloud resource templates
- Health check implementations
- afi-reactor - manifest-driven pipeline runtime (infrastructure consumer)
- afi-core - Core runtime (infrastructure consumer)
MIT