INFRA-001: Restore infrastructure proxy bidding subscription in mesh_node.py #98
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#98
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
Subscription to
intent.discoveredexists (line 249), but bidding logic is missing. Infrastructure needs to bid on behalf of registered workers.Scope (MINIMAL)
_on_intent_discovered(), add bidding logic:ledger.find_eligible_worker_instances(intent_type)bond_pool >= min_bondledger.escrow_bond(worker_id, intent_id, bond)ledger.acquire_claim_lease(intent_id, worker_id)Files
docker/mesh_node.py-_on_intent_discovered()add biddingAcceptance Criteria
intent.claimedon successAdditional Context (2026-04-09)
Test Evidence
From E2E test execution (tests/e2e/test_skill_tool_e2e.py):
Related Issues
Blocking Dependencies
This issue blocks:
Implementation Path
Phase 1: Remove _execute_as_worker() from mesh_node
Phase 2: Spawn ephemeral_worker.py as subprocess
Phase 3: Workers subscribe to backplane independently
Phase 4: Workers emit results via result.committed
Performance Impact
Current: Threads in mesh_node process (fast but wrong)
Correct: Subprocess spawning (slower but architecturally sound)
Trade-off: Accept spawning overhead for process isolation, independent scaling, correct architecture, and federation support.
✅ IMPLEMENTED - 2026-04-25
Infrastructure proxy bidding is now fully implemented via
BidManagerclass:Implementation:
docker/bid_manager.py- NewBidManagerclass handles all bidding logicbid()- Main entry point called from mesh_node on intent.discovered_find_workers()- Finds eligible workers (literal → semantic fallback → factory catchall)_filter_by_bond()- Filters workers by bond pool >= min_bond_bid_all_workers()- Escrows bond and scores workers (similarity × 0.4 + reputation × 0.3 + bond_ratio × 0.3)_emit_claimed()- Emitsintent.claimedsignal on winning bidIntegration in
docker/mesh_node.pyline 571:Acceptance Criteria Status:
_find_workers()with literal + semantic fallback)_bid_all_workers()→ledger.escrow_bond())_emit_claimed())intent.claimedon success (via backplane signal)Tests: 151 tests collected, bid-related tests passing.
Note: The original spec suggested adding logic directly to
_on_intent_discovered()but the actual implementation uses a cleanerBidManagerclass pattern for better separation of concerns.