Skip to content

chore: remove references to the removed afi-ops repository #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Gio2050 merged 1 commit into from
Jul 17, 2026
Merged

chore: remove references to the removed afi-ops repository #21

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .factory/droids/schema-validator-droid.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ This droid is a **schema and validator specialist** for afi-core. It:
- `afi-reactor/` — DAG wiring, orchestration logic (that's the orchestrator's job)
- `afi-token/` — Smart contracts, emissions, tokenomics
- `afi-gateway/` — Eliza agents, gateway configs, runtime agent behavior
- `afi-ops/`, `afi-infra/` — Deployment, infrastructure
- `afi-infra/` — Deployment, infrastructure
- Production secrets, deployment configs, or chain IDs

### Responsibilities
Expand Down Expand Up @@ -173,7 +173,7 @@ This droid MUST NOT:
- Do NOT modify afi-gateway

4. **Touch infra/ops**:
- Do NOT modify deployment configs, Terraform, K8s, or CI/CD in afi-ops or afi-infra
- Do NOT modify deployment configs, Terraform, K8s, or CI/CD in afi-infra

5. **Introduce PoI/PoInsight as signal fields**:
- Do NOT add `poi`, `poinsight`, `proof_of_intelligence`, or similar fields to signal schemas
Expand Down
2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ npm run mentor-eval
- `src/clients/` — Client libraries for AFI services
- `test/` — Vitest tests

**Consumed by**: afi-reactor (orchestration), afi-ops (deployment), Eliza gateways (types/clients)
**Consumed by**: afi-reactor (orchestration), Eliza gateways (types/clients)
**Depends on**: afi-config (schemas)

**Boundary with afi-reactor**:
Expand Down
2 changes: 1 addition & 1 deletion docs/AFI_CORE_RUNTIME_OVERVIEW.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ AFI-Core does **NOT** handle:

❌ **Token Contract Definitions** - That's `afi-token` (AFIToken, AFISignalReceipt, AFIMintCoordinator)
❌ **DAG Topology / Policy** - That's `afi-reactor` (15-node DAG, pipeline definitions, orchestration rules)
❌ **Infrastructure / Deployment** - That's `afi-infra` or `afi-ops` (Kubernetes, Terraform, CI/CD)
❌ **Infrastructure / Deployment** - That's `afi-infra` (Kubernetes, Terraform, CI/CD)
❌ **Direct On-Chain Writes** - AFI-Core generates instructions; execution happens via Safe/backend/droid

---
Expand Down
2 changes: 1 addition & 1 deletion droids/00_repo_orientation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Core runtime for agent signal validation, ElizaOS integration, and PoI/PoInsight
**This repo does NOT handle**:
- ❌ DAG orchestration (that's afi-reactor)
- ❌ UI/frontend (that's afi-research-site)
- ❌ Deployment (that's afi-ops)
- ❌ Deployment (that's afi-infra)
- ❌ Smart contracts (that's afi-token)

---
Expand Down
Loading