META: Reopened / Improperly Implemented Issues

Mark commented

2026-04-11 01:22:26 +00:00

Owner

Overview

This document tracks issues that were marked as "fixed" or "complete" but were implemented incorrectly, violating architectural principles.

INFRA-003, INFRA-004, INFRA-005, INFRA-013 - Bidding and Validation

Status: IMPROPERLY IMPLEMENTED
Commits: a8dc4cf, 4d34c3e, d5693a7, a6ed4b9

What was claimed:

Fixed bidding logic
Added worker spawning
Implemented validation agent

What was actually done:

mesh_node executes work in _execute_as_worker() instead of spawning independent workers
Added async threads in mesh_node process instead of separate worker processes
Validation agent exists but may bypass proper mesh flow

Why it's wrong:

Violates "substrate routes, workers execute" principle
mesh_node is infrastructure, not an agent
No process isolation
Tests pass but architecture is broken

What needs to be done:

✅ DONE - Remove _execute_as_worker() from mesh_node
✅ DONE - Actually spawn ephemeral_worker.py as separate processes
✅ DONE - Workers subscribe to backplane and receive intents independently

Issues #58, #59, #60, #70, #71, #72 - Complete Feature Set

Status: PARTIALLY IMPLEMENTED / BROKEN
Commit: 687044b

What was claimed:

Complete prompt tuning system
Worker template system
Artifact system
Tool library
File input pipeline

What was actually done:

Tool library exists but capabilities call tools directly (not through workers)
Evolution system hardcoded for specific types
Prompt tuning may not integrate properly with worker spawning
Artifacts work but mesh_node creates them (should be workers)

Why it's wrong:

Tools should be called by workers, not mesh_node
Evolution bypasses mesh flow
Infrastructure doing agent work

What needs to be done:

Refactor tool calls to happen in worker context
Fix evolution to use mesh intent flow
See: ARCH-003 (Remove LLM from infrastructure)

Issue #72 - Tool Factory Pattern

Status: IMPROPERLY IMPLEMENTED
Commits: a310e25, 6b475e0, a0ef9a2

What was claimed:

Implemented factory pattern for tools
Tool runner and library complete

What was actually done:

Tools exist and work
But mesh_node may call them directly instead of workers
Tool factory generates tools but integration is wrong

Why it's wrong:

Tools are called by infrastructure, not agents
Bypasses worker skill system

What needs to be done:

Ensure all tool calls happen through workers
Remove direct tool calls from mesh_node
Workers load skills, skills call tools

Summary

These issues were marked complete but violate the fundamental architecture:

Infrastructure executes instead of routing
Workers don't actually spawn as independent agents
Evolution bypasses mesh flow

The code "works" (tests pass) but the architecture is fundamentally broken.

Status Update (2026-04-10):

Worker spawning now fixed - uses subprocess instead of threads
Architecture verification tests added
E2E test proves mesh accepts HTTP intents
Next: Fix worker registration so mesh actually has workers to execute intents

See also: issues/REOPENED_IMPROPERLY_IMPLEMENTED.md

## Overview This document tracks issues that were marked as "fixed" or "complete" but were implemented incorrectly, violating architectural principles. ## INFRA-003, INFRA-004, INFRA-005, INFRA-013 - Bidding and Validation **Status:** IMPROPERLY IMPLEMENTED **Commits:** `a8dc4cf`, `4d34c3e`, `d5693a7`, `a6ed4b9` ### What was claimed: - Fixed bidding logic - Added worker spawning - Implemented validation agent ### What was actually done: - mesh_node executes work in `_execute_as_worker()` instead of spawning independent workers - Added async threads in mesh_node process instead of separate worker processes - Validation agent exists but may bypass proper mesh flow ### Why it's wrong: - Violates "substrate routes, workers execute" principle - mesh_node is infrastructure, not an agent - No process isolation - Tests pass but architecture is broken ### What needs to be done: - ✅ **DONE** - Remove `_execute_as_worker()` from mesh_node - ✅ **DONE** - Actually spawn `ephemeral_worker.py` as separate processes - ✅ **DONE** - Workers subscribe to backplane and receive intents independently --- ## Issues #58, #59, #60, #70, #71, #72 - Complete Feature Set **Status:** PARTIALLY IMPLEMENTED / BROKEN **Commit:** `687044b` ### What was claimed: - Complete prompt tuning system - Worker template system - Artifact system - Tool library - File input pipeline ### What was actually done: - Tool library exists but capabilities call tools directly (not through workers) - Evolution system hardcoded for specific types - Prompt tuning may not integrate properly with worker spawning - Artifacts work but mesh_node creates them (should be workers) ### Why it's wrong: - Tools should be called by workers, not mesh_node - Evolution bypasses mesh flow - Infrastructure doing agent work ### What needs to be done: - Refactor tool calls to happen in worker context - Fix evolution to use mesh intent flow - See: ARCH-003 (Remove LLM from infrastructure) --- ## Issue #72 - Tool Factory Pattern **Status:** IMPROPERLY IMPLEMENTED **Commits:** `a310e25`, `6b475e0`, `a0ef9a2` ### What was claimed: - Implemented factory pattern for tools - Tool runner and library complete ### What was actually done: - Tools exist and work - But mesh_node may call them directly instead of workers - Tool factory generates tools but integration is wrong ### Why it's wrong: - Tools are called by infrastructure, not agents - Bypasses worker skill system ### What needs to be done: - Ensure all tool calls happen through workers - Remove direct tool calls from mesh_node - Workers load skills, skills call tools --- ## Summary These issues were marked complete but violate the fundamental architecture: - **Infrastructure executes instead of routing** - **Workers don't actually spawn as independent agents** - **Evolution bypasses mesh flow** The code "works" (tests pass) but the architecture is fundamentally broken. **Status Update (2026-04-10):** - Worker spawning now fixed - uses subprocess instead of threads - Architecture verification tests added - E2E test proves mesh accepts HTTP intents - Next: Fix worker registration so mesh actually has workers to execute intents See also: issues/REOPENED_IMPROPERLY_IMPLEMENTED.md

Mark referenced this issue from a commit

2026-04-19 16:33:53 +00:00

Remove remaining local issue files now tracked in Forgejo

Mark added the

feature-request

label

2026-05-12 23:53:05 +00:00

Mark added the

triage-approved

quickfix

labels

2026-05-18 04:18:28 +00:00

Mark added the

in-progress

label

2026-05-27 17:14:09 +00:00

Mark commented

2026-05-27 17:19:53 +00:00

Author

Owner

🤖 [quickfix-mesh-seed-122] still working — overseer retry