Help one person's agent work across many machines without losing track of who is in charge. You will make delegation and recovery predictable.
Not open yet: First team
This work starts when that stage arrives, so there is no application to submit today and we will not pretend otherwise. What is written below is what the role is for and what would make somebody right for it, published early on purpose so you can decide whether it is worth watching.
The work
Build durable task state, queues, leases, fencing, cancellation and reconciliation. Design failover so a recovered replica cannot become a second conflicting authority. Distinguish control-plane replication from execution workers and expose uncertainty when external outcomes cannot be confirmed.
The milestone
In your first 90 days, demonstrate delegated work across two devices, interruption recovery and prevention of duplicate externally visible actions in the supported test cases.
Evidence
Bring strong reasoning about consistency, retries, failure detection and distributed transactions. Show a system you operated through real failures and the guarantees it actually provided.
Evidence, not credentials. We are describing work you can point at, in whatever form it exists.
The exercise
Trace a task whose worker finishes after its lease expires and whose external API response is lost.