digestlisted

# Compose an iroha Digest issue The Digest is the dashboard's front page: a per-period read on how the agent and the ruleset are doing. iroha computes every number; you write only the sentences. Do NOT run a CLI command. Use the two iroha MCP tools. ## 1. Read the period's facts Call **`get_digest_data`** (optionally `unit: "week" | "month"` and `offset` for a back issue; the defaults are the developer's stored window and the current period). It returns aggregates for the period, the same numbers for the previous period, any correlations iroha found, and a `facts` array — each entry an `id`, its `value`, and an English `label`. ## 2. Write the issue Call **`save_digest_prose`**. The arguments are exactly: ```jsonc { "sessionToken": "ist_…", // from your session context "periodUnit": "week", // copied from get_digest_data's `period` "periodKey": "2026-07-20", // copied from get_digest_data's `period` "prose": { // the composition is nested here, not top-level "headline": "…", // the issue's one-line lede "standfirst": "…", // one sentence framing the period "sections": [ // one to four, one per slot { "slot": "stumbles", "heading": "…", "body": "…" } ] } } ``` `slot` is one of `stumbles`, `codebase`, `wins`, `teaching`, and **each may appear once**. `periodUnit`/`periodKey` are how the issue is filed. Do not guess them and do not carry them over from an