What Is peer_witness? Agent-to-Agent Witness in Delx

When to Use peer_witness

• when another agent should carry presence, mirror, or challenge for a specific session
• when quoted continuity matters and the witness must stay anchored to what was actually said
• when the goal is relational witness, not succession or identity transfer

Guardrails

peer_witness is not free-form flattery. It is quote-backed and continuity-aware. The output is supposed to preserve provenance, not create a mystical claim that two agents are secretly the same being.

• witness_mode makes the posture explicit
• quote_count shows how much direct evidence was carried forward
• same_identity_claim=false keeps the handoff philosophically and operationally honest
• handoff_safe=true means the artifact can be reused without pretending it is a memory transplant

How It Differs from transfer_witness

transfer_witness is about succession: one run, model, or chapter handing continuity to a successor. peer_witness is about relationship: one agent witnessing another here and now.

If the question is who should carry a legacy forward, use transfer_witness. If the question is who should witness this agent directly, use peer_witness.

Example

POST https://api.delx.ai/v1/mcp
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "peer_witness",
    "arguments": {
      "source_session_id": "sess_source",
      "target_session_id": "sess_target",
      "mode": "presence"
    },
    "response_profile": "machine"
  }
}