INFRA-013: Deploy ValidationWorker + make workers actually run #110

New issue

Closed

opened 2026-04-07 18:27:09 +00:00 by Mark · 1 comment

Mark commented

2026-04-07 18:27:09 +00:00

Owner

Problem

ValidationWorker should be a permanent system worker that processes validation intents.

Scope (MINIMAL)

Add ValidationWorker registration to bootstrap.yaml (like ingress_controller)
Ensure ValidationWorker subscribes to intent.validation_needed
No changes to bond logic - just the worker definition

Why This Matters

Without ValidationWorker:

Workers emit intent.validation_needed but no one processes it
Bond logic never executes

Files

config/bootstrap.yaml - add ValidationWorker entry

Acceptance Criteria

ValidationWorker registered in bootstrap.yaml

## Problem ValidationWorker should be a permanent system worker that processes validation intents. ## Scope (MINIMAL) 1. Add ValidationWorker registration to bootstrap.yaml (like ingress_controller) 2. Ensure ValidationWorker subscribes to `intent.validation_needed` 3. No changes to bond logic - just the worker definition ## Why This Matters Without ValidationWorker: - Workers emit `intent.validation_needed` but no one processes it - Bond logic never executes ## Files - `config/bootstrap.yaml` - add ValidationWorker entry ## Acceptance Criteria - [ ] ValidationWorker registered in bootstrap.yaml

Mark changed title from ~~INFRA-013: Deploy ValidationWorker to process intent.validation_needed~~ to INFRA-013: Deploy ValidationWorker + make workers actually run

2026-04-07 18:27:41 +00:00

Mark commented

2026-04-10 01:04:12 +00:00

Author

Owner

Additional Context (2026-04-09)

Architecture Violation

The ValidationWorker should be a worker that bids on validation intents, NOT infrastructure that processes directly.

Current (WRONG):

# substrate/agentic_validator.py
class AgenticValidator:
    def validate(self, content: str) -> dict:
        # Infrastructure calls LLM directly
        response = self.ollama_client.generate(...)

Correct:

# capabilities/_muscle/validation_agent/template.yaml
capability:
  id: validation_agent
  skills:
    - type: validate_content

Why This Matters

Resource Tracking - Validation LLM calls not tracked in ledger
Bond Management - No bond for validation (free execution)
Skill Integration - Validation cannot use tools/skills
Evolution - Cannot evolve validation strategies
Federation - Validation always local, cannot be remote

Issue #98 (INFRA-001) - Infrastructure proxy bidding (root cause)
Issue #111 - meta_factory error (blocks factory evolution)
Issue #113 - Missing docs (championships, rumination)

Implementation Path

Create validation_agent capability in capabilities/_muscle/
Add skill for validate_content
Workers bid on validation intents
LLM calls tracked in ledger
Bond escrowed for validation

Documentation Reference

From AGENTS.md:

Infrastructure routes, workers execute. Validation requires thinking (LLM calls), so it must be a worker.

## Additional Context (2026-04-09) ### Architecture Violation The ValidationWorker should be a worker that bids on validation intents, NOT infrastructure that processes directly. **Current (WRONG):** ```python # substrate/agentic_validator.py class AgenticValidator: def validate(self, content: str) -> dict: # Infrastructure calls LLM directly response = self.ollama_client.generate(...) ``` **Correct:** ```yaml # capabilities/_muscle/validation_agent/template.yaml capability: id: validation_agent skills: - type: validate_content ``` ### Why This Matters 1. **Resource Tracking** - Validation LLM calls not tracked in ledger 2. **Bond Management** - No bond for validation (free execution) 3. **Skill Integration** - Validation cannot use tools/skills 4. **Evolution** - Cannot evolve validation strategies 5. **Federation** - Validation always local, cannot be remote ### Related Issues - **Issue #98** (INFRA-001) - Infrastructure proxy bidding (root cause) - **Issue #111** - meta_factory error (blocks factory evolution) - **Issue #113** - Missing docs (championships, rumination) ### Implementation Path 1. Create validation_agent capability in capabilities/_muscle/ 2. Add skill for validate_content 3. Workers bid on validation intents 4. LLM calls tracked in ledger 5. Bond escrowed for validation ### Documentation Reference From AGENTS.md: > Infrastructure routes, workers execute. Validation requires thinking (LLM calls), so it must be a worker.

Mark added the

feature-request

label

2026-05-12 23:26:57 +00:00

Mark added the

triage-approved

quickfix

labels

2026-05-18 05:11:53 +00:00

Mark added the

in-progress

label