[Direction]: Shared Goal Authority and cross-host coordination

[huangruiteng]

Outcome

Let agents on different hosts coordinate over one explicitly shared LoopX goal
without turning a storage provider, host session, claim, or lease into a new
control-plane authority.

The canonical proposal is the
Shared-Goal Online Authority and Pluggable Coordination Provider RFC,
proposed by NoKV Lab and introduced through
#2787.

Current stage

Draft contract and provider qualification. NoKV is an unpromoted optional
provider candidate. The current RFC maps a static API baseline and does not
claim qualification against a live NoKV deployment.

This direction is deliberately named Shared Goal Authority and Cross-host
Coordination, not "a shared metadata database." Run history, status, quota,
scheduler state, host sessions, and evidence keep their existing owners; an
agent does not connect directly to NoKV, and NoKV does not become LoopX
authority.

Next qualifying slice

1. extract the provider-neutral coordination command/precondition/receipt/
   outcome core;
2. qualify a file-backed provider on the same contract;
3. prove target-scoped conflicts and atomic original-receipt replay with
   deterministic fixtures;
4. only then evaluate a live NoKV provider behind the same LoopX authority
   boundary.

The first useful command remains a bounded claim_work contract. Renew,
release, reclaim, stale fencing, distributed quota, multi-tenant authentication,
high availability, and wider state synchronization are later decisions, not
implicit scope.

Contributor-ready cuts

• independently review the provider-neutral claim contract and illegal
  transitions;
• add deterministic conflict, retry, replay, and stale-generation fixtures;
• document deployment and failure boundaries without provider credentials or
  private payloads;
• propose one narrow file-backed parity slice before provider-specific runtime
  code.

[huangruiteng]

Direction governance is now merged in
#3248.

• Canonical map: English · 中文
• Pinned community projection: Discussion #2851
• Claimable work: Contributor Task Board

This issue remains the long-lived direction and decision tracker. Concrete
implementation should use a separate bounded issue or task-board row with an
explicit base branch, smallest slice, non-goals, and validation plan.