Mission R follow-up: eradicate afi-core's aspirational DAG-integration surface

.factory/droids/schema-validator-droid.md

@@ -46,7 +46,7 @@ This droid is a **schema and validator specialist** for afi-core. It:
 - `afi-reactor/` — To understand how schemas are consumed (read-only context)
 
 **Must NOT touch**:
-- `afi-reactor/` — DAG wiring, orchestration logic (that's the orchestrator's job)
+- `afi-reactor/` — pipeline composition + orchestration logic (that's the orchestrator's job)
 - `afi-token/` — Smart contracts, emissions, tokenomics
 - `afi-gateway/` — Eliza agents, gateway configs, runtime agent behavior
 - `afi-infra/` — Deployment, infrastructure
@@ -86,7 +86,7 @@ The **AFI Droid Charter v0.1** (`afi-config/codex/governance/droids/AFI_DROID_CH
 
 ### AFI Core Role (NOT an Orchestrator)
 
-From the AFI Orchestrator Doctrine (10 Commandments):
+Per the AFI Droid Charter — afi-reactor is the orchestration/execution layer:
 
 - **afi-reactor is the orchestrator of AFI** — afi-core is NOT an orchestrator.
 - **afi-core is our runtime library, not our boss** — afi-core provides canonical types, schemas, validators, and scoring logic that afi-reactor orchestrates.
@@ -161,7 +161,7 @@ If a request asks to add PoI/PoInsight to signals, STOP and escalate.
 This droid MUST NOT:
 
 1. **Modify orchestration logic**:
-   - Do NOT edit DAG wiring, pipeline execution, or orchestration code in afi-reactor
+   - Do NOT edit pipeline composition, pipeline execution, or orchestration code in afi-reactor
    - Do NOT add orchestration logic to afi-core
 
 2. **Touch token/economics**:
@@ -298,7 +298,7 @@ Produce a short summary that includes:
 
 ### Do NOT Use This Droid For
 
-- "Wire the new schema into the DAG pipeline." → Use dag-builder-droid in afi-reactor
+- "Wire the new schema into the pipeline." → Use the pipeline-composer-droid in afi-reactor
 - "Add PoInsight as a field on signals." → Violates PoI/PoInsight design (escalate)
 - "Modify token emissions based on signal scores." → Belongs in afi-token (escalate)
 - "Update Eliza agent character specs." → Belongs in afi-gateway (escalate)

.factory/skills/extend-signal-schema/SKILL.md

@@ -216,8 +216,8 @@ error output, and surface it with minimal, clear commentary.
 When using this skill, you MUST NOT:
 
 - **Modify orchestration logic** in afi-reactor:
-  - Do NOT edit DAG wiring, pipeline execution, or orchestration code.
-  - Schema changes belong in afi-core; DAG wiring belongs in afi-reactor.
+  - Do NOT edit pipeline composition, pipeline execution, or orchestration code.
+  - Schema changes belong in afi-core; pipeline composition belongs in afi-reactor.
 
 - **Introduce PoI/PoInsight as signal fields**:
   - Do NOT add `poi`, `poinsight`, `proof_of_intelligence`, or similar fields.
@@ -292,8 +292,8 @@ exactly what changed and why.
 
 ### Do NOT Use This Skill For
 
-- "Wire the new schema into the DAG pipeline."
-  → Use `add-dag-node` skill in afi-reactor instead.
+- "Wire the new schema into the pipeline."
+  → Author the pipeline composition in afi-reactor (governed registries/manifests) instead.
 
 - "Add PoInsight as a field on Scored signals."
   → Violates PoI/PoInsight design (escalate to human).

AGENTS.md

@@ -81,7 +81,7 @@ npm run mentor-eval
 
 **Boundary with afi-reactor**:
 - `afi-core` = runtime behavior (validators, scoring)
-- `afi-reactor` = orchestration (DAG wiring, pipeline execution)
+- `afi-reactor` = orchestration (manifest-driven pipeline composition + execution)
 
 **Eliza integration**:
 - `afi-core` defines shared types, client libraries, and helpers used by AFI services and Eliza plugins.
@@ -159,7 +159,6 @@ npm run mentor-eval
 - Small, well-scoped changes to validators, types, runtime glue when requested
 - Add tests for existing validators
 - Improve ElizaOS integration with clear spec
-- Update `.afi-codex.json` if capabilities change
 
 **Forbidden**:
 - Large-scale refactors without explicit spec

droids/00_repo_orientation.md

@@ -6,7 +6,7 @@
 
 ## What This Repo Does
 
-Core runtime for agent signal validation, ElizaOS integration, and PoI/PoInsight validation. This is where signals get validated before entering the DAG pipeline.
+Core runtime for agent signal validation, ElizaOS integration, and PoI/PoInsight validation. This is where signals get validated before entering the scoring pipeline.
 
 **Key Capabilities**:
 - Signal validation (PoI, PoInsight)
@@ -26,8 +26,8 @@ Core runtime for agent signal validation, ElizaOS integration, and PoI/PoInsight
 - ✅ Core schemas
 
 **This repo does NOT handle**:
-- ❌ DAG orchestration (that's afi-reactor)
-- ❌ UI/frontend (that's afi-research-site)
+- ❌ Pipeline orchestration (that's afi-reactor)
+- ❌ UI/frontend
 - ❌ Deployment (that's afi-infra)
 - ❌ Smart contracts (that's afi-token)
 
@@ -88,7 +88,7 @@ See `10_common_tasks.md` for detailed workflows.
 
 **Before making changes**:
 1. Read `AGENTS.md` for constraints
-2. Check `.afi-codex.json` for dependencies
+2. Check `package.json` for dependencies
 3. Run tests locally
 4. Ensure no breaking changes to signal schema
 

droids/20_safe_patch_patterns.md

@@ -173,7 +173,7 @@ const signal = {
 \`\`\`
 
 ### Affected repos
-- afi-reactor (update DAG nodes)
+- afi-reactor (update pipeline composition)
 ```
 
 **Why**: Breaking changes need clear migration paths.