Skip to content

Council minutes artifact: render a sitting's question, synthesis, and verbatim takes to HTML on close #708

Description

@dotdevdotdev

Goal

When a council sitting wraps, produce a presentation-quality standalone HTML 'minutes' artifact: the original question, the orchestrator's synthesis, and the verbatim per-soul takes (attributed, with take/ack/pass status), one section per prompt for multi-prompt sittings. Owner request 2026-07-04.

Design (handoff pattern: in-context distill, deterministic render)

  • Everything verbatim already persists under ~/.agentwire/council/<name>/prompts/<id>/ — the renderer reads it deterministically. The synthesis exists only in the orchestrator's context, so it's an input: --synthesis <file-or-text> (optional; omitted = minutes without synthesis section).
  • CLI: agentwire council minutes [--name <sitting>] [--prompt <id|all>] [--synthesis ...] → writes ~/.agentwire/artifacts/council-<name>-minutes/index.html, prints the path, and opens it as an artifact window when the portal is up. MCP: council_minutes(...).
  • council_stop gains --minutes/--no-minutes (default: render when any prompt exists) so closing a sitting leaves the record behind automatically. Prompt history is already kept on stop, so minutes can also be rendered for past sittings (cc-vocab, monetization, … exist today).
  • HTML: self-contained (inline CSS, no external fetches — artifact CSP blocks them), theme-aware, sections: question → synthesis → takes (soul name, status, verbatim text) → sitting metadata (roster, timestamps).
  • Pairs with the artifact-download issue for pull-out/share, but doesn't depend on it to render.

Verification

agentwire council minutes --name cc-vocab --synthesis 'test' renders today's real sitting into a readable standalone HTML; council_stop on a fresh sitting auto-produces minutes; sitting with zero prompts produces none.

Built by dotdev.dev

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions