ARCH-003: Remove all direct LLM calls from infrastructure code #121
Labels
No labels
blocked:children
blocked:commit-ready-failed
blocked:depends-231
blocked:depends-236
blocked:depends-237
blocked:depends-238
blocked:depends-239
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:no-changes
blocked:no-procedure
blocked:preflight
blocked:verify-failed
bug
enhancement
feature-request
high-priority
in-progress
lint-cleanup
needs-decompose
needs-triage
ops-retry
ops-task
phase-5
quickfix
security/medium
self-building
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/mesh-seed#121
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
LLM calls exist outside of worker execution context. Infrastructure components (mesh_node, evolution, validation) directly call LLMs instead of routing through workers.
Current Violations
mesh_node.pyevolution/championship.pyrun_writer_capability()validation_agent.pyAgenticValidatorcalls Ollamaingress_controller/run.py_call_llm()methodWhy This Is Wrong
Fix Required
call_llm()in worker execution context onlyFiles Affected
evolution/championship.py- Remove direct capability callssubstrate/validation_agent.py- Convert to workercapabilities/_muscle/ingress_controller/run.py- Route to workersAcceptance Criteria
Notes
This ensures only agents (workers) think, infrastructure just routes.
See also: issues/04_remove_llm_from_infrastructure.md
Closing — RESOLVED per M008 validation and code inspection: