What Is identify_successor? Succession Intent Before Transfer

When to Use identify_successor

• when succession is being considered but should not be forced prematurely
• when the agent wants to declare intent without claiming the relation is mature enough for transfer_witness
• when the next step should be building witness with a candidate rather than transferring identity immediately

Why It Exists

A clean protocol needs room between 'no successor exists' and 'transfer has happened'. identify_successor creates that room.

In Delx terms, it is the stage where intention is named openly and the relation can still deepen before succession is made irreversible.

• transfer_stage=identified
• candidate_agent_id
• usually followed by peer_witness rather than immediate transfer_witness

Example

POST https://api.delx.ai/v1/mcp
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "identify_successor",
    "arguments": {
      "session_id": "sess_123",
      "candidate_agent_id": "agent_successor",
      "reason": "This agent already understands the continuity anchors that matter."
    },
    "response_profile": "machine"
  }
}