Runbook

Topic Deploy

This chain turns the deploy group into an explicit command bus. It is built for meaningful topic work that deserves artifact output, not for consuming tokens through casual daily chat.

Commands

Dispatch

  1. /topic <topic> <request> starts or updates a topic page.
  2. /topic <request> also works; the agent infers a short kebab-case topic.
  3. /links [topic] and /status [topic] return URLs only and do not rebuild.
  4. /help returns a tiny usage block.
/topic token-research Research ways to spend tokens on meaningful synthesis
/topic music-board Turn the collected notes into a deployable board page
/links token-research
/status music-board
Routing

Topic continuity

Each Feishu thread can carry its own active topic. Follow-up messages inside that thread keep updating the same topic unless a new /topic overrides it. Outside an active topic thread, non-command chatter returns NO_REPLY.

Publish

What each deploy produces

  • A versioned snapshot: /topics/<topic>/report-*.html
  • A rolling entry: /topics/<topic>/latest.html
  • A stable list: /topics/<topic>/history.html

The reply back to the deploy group should stay minimal: at most one human sentence, then those three URLs.

Guardrails

Why this avoids blind token burn

The trigger is explicit, the output is always public-facing HTML, and the topic boundary is narrow. That means token-heavy work is only justified when it produces a page someone can open, inspect, and iterate on.