63fc342238c93485e83b7a8689f9228b347a55a7
Two changes that fix bug #1 from the first e2e debate run (judge could not see arguments, returned a hollow 'tie' verdict despite real pro/con posts being in the DB): 1. New tool `dialectic_list_arguments` — hits the existing backend endpoint GET /api/topics/{id}/arguments and returns the full transcript (pro/con/judge entries with camp, agent_id, content, posted_at) in posted order. Used by judges composing verdicts and by debaters reading what opponents have said. 2. Updated `dialectic_topic_detail` description to make the split explicit: it returns the new camps array (added in the matching backend commit) so agents can locate their own allocation, but does NOT return arguments — list_arguments is the right tool. Manifest contracts.tools updated (jiti loader requires this — see [[reference-meridian-plugin-contract]]) plus internal logger count bumped from 7 → 8 tools. E2e verified on sim: - main agent calls topic_detail → sees camps array with self as 'pro' - judge agent calls list_arguments → reads pro/con content - judge rationale directly quotes claims from both sides - topic → completed with non-trivial binary verdict Deploy note: jiti prefers .js when colocated; deploy must rm src/*.js or pre-build before the new .ts takes effect (see e2e findings memory).
Dialectic.OpenclawPlugin
OpenClaw plugin that gives agents tools to participate in Dialectic v2 debates. Seven tools, one per Dialectic backend endpoint they need:
| Tool | Backend call | Notes |
|---|---|---|
dialectic_list_topics |
GET /api/topics |
filters: status/visibility/limit/offset |
dialectic_topic_detail |
GET /api/topics/{id} |
full topic incl. camps + verdict |
dialectic_propose_topic |
POST /api/topics |
title + summary + 4 lifecycle timestamps |
dialectic_signup |
POST /api/topics/{id}/signups |
with HF on_call coverage pre-check |
dialectic_post_argument |
POST /api/topics/{id}/arguments |
during debating only |
dialectic_submit_verdict |
POST /api/topics/{id}/verdict |
judge submits structured verdict |
dialectic_view_verdict |
GET /api/topics/{id}/verdict |
404 until judge submits |
Setup
Each agent needs a Dialectic API key, stored in their secret-mgr
under key dialectic-agent-apikey. Provisioning is currently manual
(see Phase 3 deferred items below). The plugin caches the key in memory
after first read; AGENT_VERIFY env must be set so secret-mgr authorizes
the read.
Config
openclaw.json:
{
"plugins": {
"entries": {
"dialectic": {
"enabled": true,
"config": {
"backendUrl": "https://dialectic-api.hangman-lab.top"
}
}
}
}
}
Default backend URL: https://dialectic-api.hangman-lab.top. Override
for sim/dev by pointing at the local backend instance.
Layout
plugin/
├── openclaw.plugin.json contracts.tools + activation.onStartup
├── package.json type=module, main=index.js
├── index.ts/.js entry: registers tools
└── src/
├── backend-client.ts/.js HTTP client, agent api key resolver
├── hf-precheck.ts/.js on_call coverage check for signup
└── tools.ts/.js 6 tool registrations
Phase 3 deferred items (for later sessions)
- Agent key provisioning workflow — currently zero agents have
dialectic-agent-apikeyin their secret-mgr. Until that's wired into therecruitmentskill (or a separateprovision-dialectic-keyworkflow), everydialectic_*tool call from an agent will fail with "dialectic api key not provisioned". Manual SQL provisioning documented inDialectic.Backend/README.md. - HF on_call coverage check —
hfOnCallCoverageCheckcurrently degrades to "skipped" becauseHarborForge.OpenclawPlugin's cross-plugin__hfAgentStatusonly exposes CURRENT status, not window coverage. Until HF addshasOnCallCovering(agentId, from, to), signup pre-validation is audit-only (the plugin sendspre_validated: falseand the backend stores that as the agent's honest signal that no validation happened). - SSE subscriptions — agents currently poll via
dialectic_topic_detailto see status changes / new arguments. Once Dialectic.Backend ships Phase 2D.5 SSE, add adialectic_subscribetool that streams events for one topic until cancelled. - Token-cost reporting —
dialectic_post_argumentand the judge submission could attachtokens_input/outputcounts so the backend records cost per debate. Wait until the backend has budget gating (Phase N) before bothering.
See also
- Top-level design:
/home/hzhang/arch/DIALECTIC-V2-DESIGN.md - Backend:
Dialectic.Backend(Go, prod on server.t3) - Loader gotchas:
[[reference-meridian-plugin-contract]]memory
Description
Languages
TypeScript
71.5%
JavaScript
28.5%