briefing-outline

# 說明提綱 (Briefing Outline) A 說明提綱 sits at a fixed **altitude**: high enough to see the whole body of source material at once, always pointing **down** to each source for the detail — where a source is a separate document, or a section of one long report. Its reader — a 主管 or 委員會 deciding direction — wants to grasp the whole and know where to drill, not re-read the sources. Every section carries enough essence to stand on its own, then hands off with 「（詳《source》）」. The recurring failure is drift below altitude — dragging in 逐項標準、逐條規則、逐步操作、完整明細 that belong in the source. Hold altitude and the 提綱 stays readable and stable when sources churn. ## Output Language Match the language of the user's request, and apply it to *all* user-facing output — option labels, generated-document headings, table column names — not just prose. If the user explicitly asks for another language, that wins. Language follows the request, not the source material. When the sources are in English but the user writes in Chinese, the 提綱 stays Chinese. If the request is in Chinese, use Traditional Chinese (Taiwan business usage) and keep established technical terms in English. The English in this file is structural labelling for you, not literal output. Never mirror this file's language into your response. ## Steps 1. **Inventory the sources.** List every source and one line on what each holds — a source being a separate document, or (for a single long report) one of its sections. Separate any **umbrel...