[Phase 2.1] Router eligibility for ephemeral provisioning instances #41
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#41
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?
Deliverables
Update
runtime/intent_router.pyto evaluate worker-instance readiness:Routing Logic
Key Distinction
no_eligible_worker, trigger provisioning flowState Transitions
spawned→ eligible for routingclaimed→ ineligible (already assigned)executing→ ineligiblecompleted|failed|timed_out→ ineligibleAcceptance
boundary.foundtriggers when no eligible instances existcapability.starvationwhen demand > eligible supply