Repository navigation
Armonia · Execution-site registry and outbound worker protocol #1882
Description
Important
Problem — Work runs locally or on one cloud solve service that the client polls. There is no way for a compute node, cluster login node, or lab computer to join a team deployment, take work, and report back with durable identity across disconnects.
Approach — An execution-site registry and an outbound worker protocol: a site registers with its own credential, advertises capabilities, leases jobs by durable identity, heartbeats, streams progress, and on reconnect reconciles job state rather than resubmitting. A site-backed executor plugs into the existing executor contract.
Scope — in: site registry and credentials (issue, revoke), capability advertisement, job lease/heartbeat/complete, progress and result reporting, reconnect reconciliation, cancellation, campaign-check on submit, a reference compute-worker site. out: lab-site and batch-site adapters (their own slices), artifact storage.
Assumptions — Sites can open outbound authenticated connections; they may not accept inbound ones.
Acceptance Criteria
- A registered site with a valid credential can lease a job; a revoked site cannot.
- A job leased by a site that disconnects and reconnects before lease expiry continues and produces exactly one authoritative result.
- A job whose site misses its lease is reported lost and is not silently resubmitted.
- Cancelling a job reaches the site and the final status reported is authoritative.
- A submission exceeding its campaign's budget or device access is refused before any site sees it.
- The executor-parity cases that pass for local runs pass for the reference compute-worker site.
Testing Decisions
Extend the executor contract and executor-parity fixtures; add site lease and reconnect tests with injected disconnects.
Key Decisions
- Job identity is assigned by the coordinator and never reused.
- Reconciliation prefers the site's reported state when its lease generation is current; stale generations are discarded.
Data Contracts
- Site: id, kind (agent worker | compute | batch | lab), capabilities, credential, health.
- Job: id, campaign, site, lease generation, state, progress cursor, result reference.
Constraints & Invariants
- Sites never receive person credentials.
- Site credentials resolve to site principals, never to people.
Prior Art
- The executor contract and run handle, the launcher, the remote executor and cloud client, peer tokens, the generation fence, Mirror canonical cloud task lifecycle and receipts #893.
Activity
[-]Team engine · Execution-site registry and outbound worker protocol[/-][+]Armonia · Execution-site registry and outbound worker protocol[/+]