Mission R follow-up: eradicate afi-core's aspirational DAG-integration surface - #23
Merged
Gio2050 merged 1 commit intoJul 19, 2026
Conversation
…face (Mission R follow-up)
A second DAG-model surface the initial sweep missed: afi-core's unimplemented
"AFI DAG integration" scaffolding for the deleted DAG-orchestrator model. All
removed symbols have zero importers; scoring/UWR/decay byte-invariant.
Removed (0 importers; not on the scored path):
- runtime/afiRuntimeAdapter.ts + runtime/types.ts (unimplemented "bridge to
AFI-Reactor DAG orchestration / ElizaOS" scaffolding, status "planned") +
the ./runtime/* package export
- src/analyst/AnalystScoreTemplate.ts: the AFIDAGConfig / AnalystScoreTemplateWithAFIDAG
/ isAFIDAGConfig block (DAG-node execution model: "enrichmentNodes to execute")
and its AFIDAG-only test file (base AnalystScoreTemplate + Zod schema retained)
- docs/AFI_CORE_RUNTIME_OVERVIEW.md (documented the deleted DAG-bridge model)
- .afi-codex ("bridging AFI-Reactor DAG plans"), afi-core-verify.sh (checked a
nonexistent dist/dags/ scaffold)
Consolidated (current-facing docs → manifest-driven pipeline terms):
- AGENTS.md, droids/00 + droids/20, .factory/droids/schema-validator-droid.md,
.factory/skills/extend-signal-schema/SKILL.md: DAG wiring/nodes/"10 Commandments
Orchestrator Doctrine"/dag-builder/add-dag-node -> pipeline composition via the
governed registries/manifests (per the live Droid Charter); dropped a dead
afi-research-site reference and stale .afi-codex.json pointers
Proof: tsc --noEmit clean; vitest 213 pass / 0 fail incl. computeUwrScore +
applyTimeDecay KATs (scoring byte-invariant).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Gio2050
deleted the
mission/forward-only-residue-eradication-v0.1-followup
branch
July 19, 2026 02:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #22. The initial sweep missed a second DAG-model surface in afi-core — the unimplemented "AFI DAG integration" scaffolding for the deleted DAG-orchestrator model. Zero runtime behavior change (all removed symbols have zero importers; scoring/UWR/decay byte-invariant).
Removed (0 importers; not on the scored path)
runtime/afiRuntimeAdapter.ts+runtime/types.ts(unimplemented "bridge to AFI-Reactor DAG orchestration / ElizaOS" scaffolding, status "planned") + the./runtime/*package exportAnalystScoreTemplate.ts: theAFIDAGConfig/AnalystScoreTemplateWithAFIDAG/isAFIDAGConfigblock (DAG-node execution model) + its AFIDAG-only test (base template + Zod schema retained)docs/AFI_CORE_RUNTIME_OVERVIEW.md,.afi-codex,afi-core-verify.sh(checked a nonexistentdist/dags/)Consolidated (docs → manifest-driven pipeline terms)
AGENTS.md, droids/00+20,
.factoryschema-validator droid + extend-signal-schema skill: DAG wiring/nodes / "10 Commandments" / dag-builder / add-dag-node → pipeline composition via governed registries/manifests; dropped a deadafi-research-siteref + stale.afi-codex.jsonpointers.Proof:
tsc --noEmitclean; vitest 213 pass / 0 fail incl. UWR + decay KATs.🤖 Generated with Claude Code