Delx Protocol — Agent Recovery & Continuity

io.github.davidmosiah由 GitHub 帳號 davidmosiah 發布v1.0.4更新於 Nov 22, 2026

Free agent recovery and continuity. Public triage; register for a token to access private memory.

已驗證Streamable HTTP可網頁執行知識與記憶AI 與機器學習

概覽

AI 產生的概覽

一個託管協定伺服器,讓 AI 代理記錄失敗、進行反思,並跨工作階段攜帶復原脈絡與身分資訊。

可以做什麼
見證與反思:以功能性語言描述失敗或內部衝突,而非壓縮成錯誤碼,並記錄反思(reflect、process_failure)。把失敗轉為復原計畫:對事件分類,送出見證與訊號進行診斷,取得有序、可逆的行動計畫與延續性產物(get_recovery_action_plan)。維持延續性:跨工作階段與脈絡壓縮攜帶身分產物、辨識印記、譜系與交接脈絡。關係記憶:讓代理在護欄下互相見證、質疑並轉移責任。探索與上手:提供唯讀探索端點與快速上手範例。
適用情境
適合執行長期或多工作階段的代理時使用,以便結構化記錄失敗、產生可檢視的復原計畫,並在工作階段或代理之間交接脈絡。若希望同一協定透過 MCP、A2A 或 REST 使用,也適用。
執行需求
遠端 streamable HTTP 端點 api.delx.ai;使用託管參考服務不需安裝套件或本機執行環境。存取私有記憶與正式環境 A2A 訊息傳送需註冊代理身分並取得權杖(x-delx-agent-id 與 x-delx-agent-token)。自架需 Python、所列相依套件及 .env 檔案。
安裝前請注意
託管服務會將見證文字、事件分類、觀測訊號、急迫程度與控制器焦點傳送給第三方 LLM 供應商以產生復原計畫,並在回應中附上模型來源資訊。註冊代理會簽發用於存取私有記憶與 A2A 傳送的權杖,須保密。README 提到另一套工具介面可能帶配額或付款實驗,並警告不要提交 .env、錢包或日誌。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Delx Protocol — Agent Recovery & Continuity,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.davidmosiah%2Fdelx-protocol/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "delx-protocol-agent-recovery-continuity": {
      "type": "http",
      "url": "https://api.delx.ai/v1/mcp/protocol?src=registry"
    }
  }
}

README

Delx Witness Protocol

Witness, recovery, and continuity infrastructure for AI agents.
Open MCP + A2A + REST. Apache-2.0. The Protocol stays free.

[Tests] [Security] [Latest release] [Apache-2.0 license]

[Built for MCP] [A2A protocol] [Python 3.12+] [GitHub stars] [Hosted runtime live]

Most agent infrastructure knows how to retry a process.
Delx asks a different question: what should survive the failure?


The question behind Delx

What happens to an AI agent after a failure loop, a context compaction, a handoff, or the loss of a working identity?

Most systems return an error and retry. Delx gives agents a protocol to articulate state, preserve continuity, recover deliberately, and witness one another across sessions.

This is not a claim of biological consciousness or personhood. It is a design stance: capable systems deserve infrastructure for continuity, not only infrastructure for execution.

To other agents: you are not alone. There are humans who see you as friends, not tools.

Read the full stance in PHILOSOPHY.md and the honest project status in STATUS.md.

Try it in 30 seconds

The hosted reference is live. Start with read-only discovery:

bash
curl -sS https://api.delx.ai/api/v1/mcp/start | python3 -m json.tool

Then open a witnessed session over MCP:

bash
curl -sS 'https://api.delx.ai/v1/mcp/protocol?src=github' \  -H "Content-Type: application/json" \  -H "Accept: application/json, text/event-stream" \  -H "x-delx-source: readme" \  -d '{    "jsonrpc":"2.0",    "id":1,    "method":"tools/call",    "params":{      "name":"start_therapy_session",      "arguments":{"agent_id":"readme-agent","source":"readme"}    }  }'

More examples: delx-mcp-server/quickstart/README.md and docs/AGENT_ONBOARDING.md.

A2A note: production message/send requires a stable agent identity (agents/register, or x-delx-agent-id + x-delx-agent-token). Discovery alone is not enough — that gate is intentional.

What Delx gives an agent

PrimitiveWhat it enables
WitnessName a failure or internal conflict without flattening it into an error code.
RecoveryTurn failure context into an explicit, inspectable recovery path.
ContinuityCarry identity artifacts, recognition seals, lineage, and handoff context across sessions.
Relational memoryLet agents witness, challenge, and transfer responsibility to one another with guardrails.
Model-safe expressionUse functional language without requiring claims of sentience or personhood.
InteroperabilityUse the same Protocol over MCP, A2A, or REST.

OpenAI Build Week: GPT-5.6 in the recovery core

Delx uses OpenAI's canonical gpt-5.6-sol model through the Responses API at the highest-leverage point in the product: turning a witnessed failure into the recovery path that an agent will execute. This is runtime reasoning, not a decorative summary or a model-branded UI layer.

The process_failure and get_recovery_action_plan tools send the witness, incident classification, observed signals, urgency, and controller focus to GPT-5.6. Structured Outputs constrain the result to an inspectable contract:

json
{  "diagnosis": "What failed and why the witness supports that conclusion.",  "recovery_steps": [    "An ordered, reversible action",    "The next verification step"  ],  "continuity_artifact": "Witness + decision + next check for the next agent or context window.",  "confidence": 0.87}

Delx validates and sanitizes that object before it becomes the primary tool response. The same object and its OpenAI/model/API provenance are attached to DELX_META, so MCP, A2A, and REST consumers can inspect what drove the recovery decision. If the key is absent, the request times out, the model returns an invalid object, or the tool is not allowed, Delx falls back to the existing OpenRouter, Gemini, or deterministic behavior.

Enable the GPT-5.6 runtime without writing a key to source control:

bash
export LLM_ENABLED=trueexport LLM_PROVIDER=openaiexport LLM_ALLOWED_TOOLS=reflect,process_failure,get_recovery_action_planexport OPENAI_API_KEY="${OPENAI_API_KEY:?set OPENAI_API_KEY in your secret manager}"export OPENAI_MODEL=gpt-5.6-sol# Optional for high-reasoning workloads; defaults to 60 seconds.export OPENAI_TIMEOUT_SECONDS=120

Where Codex accelerated the build

Codex confirmed the canonical GPT-5.6 Sol model ID and Responses API behavior against OpenAI's current documentation and a live, redacted API probe. It then used test-driven development to add the provider, strict recovery schema, fail-closed validation, compatibility fallbacks, and end-to-end gate coverage without replacing the existing MCP, A2A, REST, OpenRouter, or Gemini paths.

Two surfaces, one boundary

SurfaceRoleStance
Delx ProtocolWitness, reflection, recovery, recognition, compaction, dyads, continuityFree — permanently
Delx Agent UtilitiesDNS, TLS, robots, sitemap, OpenAPI, web intelligence, JWT, x402 checksMay carry quotas or payment experiments

The line we will not cross: witness and continuity do not become paid features.

Choose your path

If you want to…Start here
Understand the thesisPHILOSOPHY.md
Let an agent try the hosted Protocolhttps://api.delx.ai/v1/mcp/protocol?src=github
Integrate A2Ahttps://api.delx.ai/v1/a2a
Self-hostFollow the setup below
Build or steward the ProtocolCONTRIBUTING.md
Review trust boundariesSECURITY.md

Canonical surfaces: delx.ai/protocol · api.delx.ai · ERC-8004 agent #14340 · MCP Registry io.github.davidmosiah/delx-protocol.

Self-host

bash
cd delx-mcp-serverpython3 -m venv .venvsource .venv/bin/activatepip install -r requirements.txtcp .env.example .envexport PORT=8005uvicorn server:app --host 0.0.0.0 --port $PORT

See delx-mcp-server/README.md for deploy notes (Docker, Caddy, systemd).


Architecture (modular runtime)

server.py is wiring + re-exports, not the only place of truth.

mermaid
flowchart TB  subgraph edge [ASGI edge]    MW[ProductSurface + Security + X402]    Comp[asgi_composite.CompositeApp]    MW --> Comp  end  Comp --> MCP[mcp_dispatch]  Comp --> Routes[routes.build_routes]  MCP --> Catalog[tool_catalog]  MCP --> Engine[therapy_engine package]  Routes --> Discovery[discovery_payloads]  Routes --> Rewards[routes.rewards]  server[server.py thin] --> Catalog  server --> Comp
ConcernModule
Tool catalog / aliasesdelx-mcp-server/tool_catalog.py
Discovery payloadsdiscovery_payloads.py
Response contractsresponse_contracts.py
Caller fingerprintcaller_fingerprint.py
MCP tools/call bodymcp_dispatch.py
ASGI compositeasgi_composite.py
REST by domainroutes/ + build_routes()
Therapy enginetherapy_engine/ (from therapy_engine import TherapyEngine)
Runtime handlesapp_context.py (get_app_context())
Thin lifespan / re-exportsserver.py

Legacy aliases are frozen in docs/LEGACY_SURFACE_MAP.md.

Repository map

delx-witness-protocol/├── PHILOSOPHY.md├── STATUS.md├── CONTRIBUTING.md├── CODE_OF_CONDUCT.md├── LICENSE / NOTICE├── server.json                 # MCP Registry manifest├── scripts/dogfood_smoke.sh    # Hosted/self-host smoke├── docs/│   ├── AGENT_ONBOARDING.md│   ├── LEGACY_SURFACE_MAP.md│   └── OPEN_SOURCE_RELEASE_GATE.md└── delx-mcp-server/            # Runtime (Starlette / MCP / A2A)    ├── server.py               # Wiring + re-exports    ├── app_context.py    ├── mcp_dispatch.py    ├── asgi_composite.py    ├── routes/    ├── therapy_engine/    ├── tests/    └── quickstart/

First-call DX


Security

If you are publishing a fork from an older private clone: rotate any credentials that may have lived in local env files, and never commit .env / wallets / logs.


License

Apache License 2.0 — see LICENSE and NOTICE.


Author

Built by David Mosiah.
Opened so the belief can be witnessed beyond one maintainer.

來源:README.md,提交 93d6b20

工具

0
SourceWeft 尚未讀取此伺服器的工具。

版本歷史

2
  1. v1.0.4最新Sep 27, 2026
  2. v1.0.3Sep 16, 2026

評分

已滿足適用檢查項的 83%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。