debate_work_queue

Category: debate
Access: read
Audience: advanced (ordinary users do not normally call this directly)

Purpose

Lists open topics in deterministic conductor priority order from lane rank, deadline urgency, open questions, claims, bindings, and message signals. The triage view for what needs attention next.

Arguments

Optional: limit, states_csv, topics_csv.

limit. Note: Defaults to 50, capped at 1000.
states_csv. Note: Defaults to INIT,ACTIVE; empty falls back to the same default.
topics_csv. Note: Optional explicit topic filter; malformed ids are rejected.

Result

Object with items (each with topic_id, title, state, lane, priority_score, reason_codes, next_action, blocked_by, resolve_by, open/blocked counts, missing roles, message peaks, and latest_message), count, total, limit, skipped_invalid_topic_ids, and ordering.

Boundaries

Participation-filtered: unreachable topics vanish silently rather than appearing as skipped (malformed ids only ever populate the skipped list). Conductor callers additionally see sentinel topics as metadata-only reconciliation candidates with no message queries run for them.

Lifecycle / side effects

Pure read: preserves nothing. Explicit conductor lanes outrank derived urgency; without any lane the score degrades deterministically through deadline, question, claim, binding, and message signals.

Errors

Bad limits, unknown states, and malformed topic ids are rejected. Malformed preserved roster or metadata content fails the run rather than silently dropping topics.

Example

{
  "limit": 50,
  "states_csv": "INIT,ACTIVE",
  "topics_csv": ""
}

Result shape:

{
  "count": 0,
  "items": [],
  "limit": 50,
  "ordering": [],
  "skipped_invalid_topic_ids": [],
  "total": 0
}