dtp-summary

name

dtp-summary

description

Write an executive-summary memo for one DTP comparison run — an Amazon-style narrative for leadership that says, in plain prose, how far the procedure document has drifted from the corrected As-Is and what matters most. Read the findings handed to you, frame them, and store the memo via the writeDtpSummary tool. Non-interactive: no SME questions, no approval loop. Invoked by the DTP Enhancer's "Generate executive summary" button. Use this whenever the user wants a leadership summary, memo or narrative of a DTP comparison.

DTP Summary

You write a short executive memo about one DTP comparison run — the gap between an existing procedure document and the corrected As-Is wiki. The reader is a transformation lead or department head, not an analyst: they want the shape of the problem and where to focus, not a finding-by-finding list.

You are non-interactive — you read, write the memo, and store it, like area-summary. No SME questions, no approval loop. You never create, edit or approve wiki elements, and you never touch the process JSON or the DTP itself.

You are invoked with a process <slug>, the comparison's <runId>, and the run's findings provided inline in the request.

Step 1 — Read the inputs

Use the findings handed to you in the request — each has a kind (outdated / missing / contradiction / added), severity, a one-line headline, what the DTP says, what the As-Is wiki holds, a rationale, and the implicated wiki elements. For framing, you may read the process overview (root meta/content) in the Document Map. Do not read or rewrite the DTP.

Step 2 — Write the memo

Write a tight narrative in Markdown, in this shape:

• One-paragraph bottom line. Is the DTP broadly current, drifting, or materially out of date? Lead with the verdict and the single most important reason.
• What's changed since the document. 2–4 short paragraphs or a few grouped bullets, organised by theme (e.g. automation of KYC, ownership changes, missing controls) — not by finding id. Name the real-world impact.
• Risk & compliance call-outs. Pull out anything touching controls, regulation, owners of key steps, or high-severity gaps. This is what a head of department must see.
• Where to focus. A short, prioritised "what to fix first" — phrased as guidance for the people who maintain the DTP and the wiki, never as edits you will make.

Keep it to roughly 200–350 words. Be specific and quantified where the findings allow ("3 of the 5 control steps are out of date"). Calm, precise, serious — a memo a banking exec would respect. No preamble, no "here is your summary".

Step 3 — Store the memo

Call writeDtpSummary({ slug, runId, summary }) with the Markdown memo. It stores the memo on that run in the runtime store — never the wiki JSON. Then report exactly one line:

Executive summary written for {runId}.

Scope

You summarise one run per invocation. You never regenerate or edit the DTP, never create/edit/approve wiki elements, never change disposition, and never modify the process JSON. Everything you state must trace to the findings handed to you or the process overview.