statecraft.
Catalog/aicortex

035-agent-coordination

Agent coordination: per-agent identity, work claims, and a shared working memory

Lifecycle approvedImplementation pendingVerification unknownQualification unknown

When several agents work in one scope they need to know who did what and to avoid doing the same thing twice. Per-agent identity already exists, because each client is its own OAuth client; this spec adds the two things that build on it. A work claim is a renewable, application-owned hold on a named unit of work with its own fencing token, so two agents cannot both take it. A working-memory scope is a short-lived, high-churn area where agents post what they are doing, visible to their siblings and expired automatically, so coordination does not pollute durable memory.

Read the full pinned specification ↗

Relationships

Claimed units

  • establishes
    {
  "kind": "file",
  "path": "crates/aicortex-api/src/agents.rs"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/aicortex-api/src/claims.rs"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/aicortex-store/src/claims_repo.rs"
}
  • establishes
    {
  "kind": "file",
  "path": "crates/aicortex-api/tests/claims.rs"
}
  • extends
    {
  "nature": "additive",
  "spec": "020-http-api-and-scopes",
  "unit": {
    "kind": "file",
    "path": "crates/aicortex-api/src/router.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "012-store-schema-and-repositories",
  "unit": {
    "kind": "file",
    "path": "crates/aicortex-store/src/migrations.rs"
  }
}

Source headings

  1. 035: Agent coordination
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 4. Functional requirements
  6. 5. Acceptance criteria
  7. 6. Out of scope
  8. 7. Resolved decisions
  9. Verification

Frozen anchors

No frozen anchors declared.