@litfamily/litclaude 1.0.19 → 1.0.21

package/plugins/litclaude/skills/lit-docx/references/tonalities/journal.md

@@ -0,0 +1,142 @@
+# Journal
+
+Journal is long-form reading set in two columns: an essay, a newsletter, a white paper, a research
+summary for colleagues that is not bound for a named journal. It sits close to a publisher profile. A
+masthead with authors, affiliations, an abstract and keywords opens page 1, the body runs in two
+ragged-right columns with a 6 mm gutter, sections carry decimal numbers so that "Section 2.4" in the
+text points somewhere, and the header holds the short title and the folio. Latin body text is set in
+Times New Roman for its narrow measure; Hangul, headings and every other element stay in Pretendard.
+The pack has no accent colour: rules, headings and the one callout style are all near-black ink.
+
+## When to use it
+
+Choose Journal for 칼럼, 뉴스레터, 백서, 연구 요약, a long explainer, or an English essay of three pages
+and more with few tables. It is the first candidate for essays and white papers and moves up when the
+source is mostly running prose in English, when it cites sections and references, or when the reader
+is expected to read from start to finish rather than look things up.
+
+## When it is the wrong choice
+
+- A journal submission or a named publisher's format: use that publisher profile (`--publisher
+  elsevier`, `acs`, `ieee`, `nature`); a tonality never stands in for a journal's rules.
+- A document of wide tables: every table of more than three columns spans the page, and a run of those
+  reads as Report with extra gutters.
+- A briefing or a memo: two columns on a two-page memo slow the reader down.
+- A procedure: steps in narrow columns wrap badly; Manual.
+
+## Structure
+
+Journal is the only pack with two columns, an abstract in its title block and Times New Roman body
+text, so any other tonality rendered from the same source differs from it in at least three structural
+features (`qa_docx.py a.docx --compare b.docx`, check `tonality.structure`).
+
+- **Page 1: the masthead.** An optional label line with the Korean date on the right (`2026. 6. 30.`),
+  the title, the subtitle as a standfirst in muted ink, the authors and organisation, numbered
+  affiliations and a corresponding address when the frontmatter has them, one ink rule, the notice once
+  in small muted text, then the abstract and keywords (초록 / 주요어 or Abstract / Keywords) from the
+  frontmatter. The two-column body starts under the masthead on the same page. `variant=` on a cover is
+  accepted and ignored.
+- **Summary form.** The abstract is the summary. There is no summary section and no key-figure strip;
+  the first paragraph of the body states what the piece argues and for whom.
+- **Numbering.** Decimal: h1 `1`, h2 `1.1`, in plain ink at heading size, so cross-references resolve.
+  References or further reading close the piece as a numbered list; that back-matter heading is left
+  unnumbered.
+- **Components and their purpose.** One kind only: `callout`, for a definition, a caveat or a method
+  note that sits outside the line of argument, at about one per four pages. It is drawn as a 1 pt ink
+  rule down its left side with a bold title, no fill. A `::: sidebar`, `::: keyfigures` or `::: columns`
+  written in the source keeps its content as ordinary text with its title as a bold lead line, and
+  stdout says so.
+- **Wide material.** A table of four or more columns spans both columns with its caption; a table of up
+  to three columns stays in the column at column width. Figures take the column width.
+- **Running head.** From page 2, the short title at the top left and the folio at the top right, small
+  and muted. No
+  section name in the header.
+- **Contents.** None.
+
+## Tokens
+
+Values at the pack default (density 9, variance 6), from `templates/tonalities/journal.yaml`. The pack
+has no accent: `accent_on` is empty, so the title rule and the callout rule are drawn in ink.
+
+| Token | Value |
+|---|---|
+| Paper, margins | A4; top 25, bottom 27, left 25, right 25 mm; two columns, 6 mm gutter |
+| Body | Times New Roman for Latin, Pretendard for Hangul, 10.5 pt, ragged right |
+| Line pitch | Latin 133 % of the size (Word multiple about 1.16 in Times New Roman), Hangul 175 % (1.14 in Pretendard) |
+| Paragraph spacing | 6 pt after (5 pt English), no indent |
+| Scale | h1 13.5 pt (1.3x), h2 12 pt (1.15x), h3 10.5 pt bold, in Pretendard; title 26.5 pt (2.5x) |
+| Ink | body and headings `#1A1A1A`; muted `#555555`; rules `#8C8C8C` |
+| Accent | no accent |
+| Tables | booktabs, 9.5 pt, header bold, numbers right-aligned |
+| Running head | header: short title left, folio right, 8.5 pt muted |
+| Components | callout only |
+| Figures | at most 0.40 of the frame height, sized to the column width |
+| Fill | no body page under 0.35 (`fill.page`) |
+
+**Dials.** Density 7 opens the margins to 27/29/27/27 mm and the pitch to 137 % Latin and 180 % Hangul,
+for a white paper meant to be printed; the columns get narrower, so check that three-column tables
+still fit. Density 10 closes the top margin to 24 mm for a newsletter with a fixed page count. Variance
+no longer adds component kinds.
+
+## Worked source
+
+```markdown
+---
+title: 재택근무 1년의 협업 비용
+subtitle: 4개 본부 설문으로 본 회의 시간 변화
+authors: [김연구, 이분석]
+organization: 예시연구소
+date: 2026-09-30
+abstract: 재택근무 도입 1년 뒤 본부별 회의 시간과 응답 지연을 비교했다. (예시)
+keywords: [재택근무, 협업, 회의 시간]
+tonality: journal
+---
+
+# 조사 방법
+
+2026년 7-8월에 4개 본부 612명에게 설문을 보냈고 523명이 응답했다(예시). 응답자 구성은 2.2절에서 다룬다.
+
+::: callout kind=note title="응답률 주의"
+개발 본부의 응답률이 다른 본부보다 낮아 본부 간 비교에는 오차가 크다.
+:::
+
+표 1. 본부별 주간 회의 시간 (예시)
+
+| 본부 | 2025년 9월 (시간) | 2026년 9월 (시간) | 변화 (시간) |
+|---|---|---|---|
+| 개발 | 3.9 | 5.1 | +1.2 |
+| 영업 | 4.4 | 4.8 | +0.4 |
+
+자료: 사내 설문 (예시)
+```
+
+The four-column table spans the page with its caption, set as `<표 1>` above and the hoisted
+`(단위: 시간)` line. The frontmatter date prints as `2026. 9. 30.`.
+
+## Headings
+
+| Use | Not |
+|---|---|
+| 재택근무 1년의 협업 비용 | 재택근무는 협업 비용을 키웠다 |
+| Meeting time after remote work | Remote work doubled our meetings |
+| 조사 방법과 한계 | 조사에는 몇 가지 한계가 있음 |
+
+The standfirst under the title is a subtitle and follows the same rule; the argument starts in the
+first paragraph. `heading.declarative` fails a heading, title or subtitle written as a sentence.
+
+## Numbers
+
+Journal leans on prose, and figures belong in sentences or tables with their period and source. There
+is no key-figure strip and never a large number across both columns. Example data says (예시) or
+(sample).
+
+## Failure patterns
+
+- A sidebar, key-figure strip or quotation box planned on the direction card: none is drawn; plan the
+  callout alone.
+- Five-column tables in a row, each spanning the page: the columns lose their rhythm; move them to an
+  appendix part.
+- Bullet lists of single words in a column: they leave half of each column empty; write them as a
+  sentence.
+- Section numbers typed into headings, which doubles the decimal numbering.
+- Using Journal as a stand-in for a publisher's manuscript format.

package/plugins/litclaude/skills/lit-docx/references/tonalities/manual.md

@@ -0,0 +1,148 @@
+# Manual
+
+Manual is the technical guide: an installation procedure, an operating manual, an onboarding guide, a
+reference for people who look things up while their hands are busy. Its pages are built for finding and
+citing. A document-control block under the title tells the reader which document this is, who owns it
+and from when it applies; decimal section numbers let a step be cited as "4.2"; numbered steps hold one
+action each; every warning has the same quiet form, slate-blue rules above and below it and a bold
+title. The page itself stays in near-black ink with no fills, so a sheet photocopied for the workbench
+loses nothing.
+
+## When to use it
+
+Choose Manual for 가이드, 매뉴얼, 절차서, 운영 지침, setup and maintenance instructions, API or tool usage
+guides delivered as a document, and training material read step by step. It is the first candidate for
+the guide type and the third for reports. Move it up when the source holds numbered procedures, several
+warnings or cautions, reference tables of settings, codes and limits, or a revision history that a
+document-control block should carry.
+
+## When it is the wrong choice
+
+- A report of results: numbered steps and warning boxes make an analysis read like instructions. Use
+  Report.
+- A decision paper or a briefing: Brief puts the decision first; Manual puts the procedure first.
+- A text with no steps and no reference tables: the control block and the decimal numbering add
+  weight without helping anyone find anything; Report or Journal.
+- A two-page notice of a procedure change: Memo, with the change stated in its opening paragraph.
+
+## Structure
+
+Manual is the only pack with a document-control block, a sidebar and a short title in the header, so it
+differs from every other tonality in at least three structural features
+(`qa_docx.py a.docx --compare b.docx`, check `tonality.structure`).
+
+- **Page 1: title over a document-control block.** An optional label line (the `kicker=` of
+  `::: cover`, for example `설치 안내서`), the title, the subtitle in muted ink, then a two-column block
+  between two ink hairlines: 문서 / 작성 부서 / 기관 / 시행일 (English: Document / Owner / Organisation /
+  Issued). The values come from frontmatter `short_title` (or `title`), `author`, `organization` and
+  `date`, the date in the Korean form `2026. 6. 30.`. The notice follows once in small muted text. No
+  cover page; the body starts on page 1.
+- **Contents.** From about five pages, a short contents list of the h1 parts with page numbers stands
+  under the control block.
+- **Summary form.** Prose: `# 개요` / `# Overview` states scope, audience and what the reader needs
+  before starting (permissions, tools, time).
+- **Numbering.** Decimal: h1 `1`, h2 `1.1`, in plain ink at heading size. Procedures are ordered lists,
+  one action per item, the expected result in the next sentence.
+- **Components and their purpose.** Three kinds are allowed. `callout` carries a warning placed
+  immediately before the step it protects; every kind (key, warning, note) is drawn in the same single
+  style, and only about one per four pages is boxed, decision request first, then warning, then note.
+  `sidebar` holds definitions or a method note beside the text it explains; it floats right at a third
+  of the width with a hairline down its left side, and when the paragraphs beside it are shorter than
+  the box it is set full width so the next heading never starts next to it (`sidebar.overlap`).
+  `columns` sets two symptom-and-action groups of nearly equal length side by side. There is no
+  key-figure strip in this pack.
+- **Reference tables.** Settings, error codes and limits in booktabs tables with units; a long table
+  (a header and six or more body rows) may break between rows with its header repeated.
+- **Running head.** From page 2, the short title at the top left and the folio at the foot right, both
+  small and muted.
+  The header never carries the current section name: a page field showed the first section starting on
+  a page, not the one the page opens in.
+
+## Tokens
+
+Values at the pack default (density 9, variance 6), from `templates/tonalities/manual.yaml`.
+
+| Token | Value |
+|---|---|
+| Paper, margins | A4; top 25, bottom 27, left 25, right 25 mm; text block 160 mm |
+| Body | Pretendard 10.5 pt, ragged right in both languages (steps and codes read better unjustified) |
+| Line pitch | Hangul 175 % (Word multiple 1.14), Latin 133 % (0.87) |
+| Paragraph spacing | 6 pt after (5 pt English), no indent |
+| Scale | h1 14 pt (1.35x), h2 12 pt (1.15x), h3 10.5 pt bold; title 26.5 pt (2.5x) |
+| Ink | body and headings `#1A1A1A`; muted `#555555`; rules `#8C8C8C` |
+| Accent | slate blue `2E4A66`, on the callout rule and the sidebar rule only |
+| Control block | 9.5 pt, labels bold, between two 0.5 pt ink hairlines |
+| Tables | booktabs, 9.5 pt, header bold, numbers right-aligned |
+| Running head | header: short title left; footer: folio right; 8.5 pt muted |
+| Components | callout, sidebar, columns (three kinds at most) |
+| Figures | at most 0.45 of the frame height |
+| Fill | no body page under 0.35 (`fill.page`) |
+
+**Dials.** Density 7 opens the margins to 27/29/27/27 mm and the Hangul pitch to 180 %: for a guide used
+at a bench, where a looser line helps the reader find their place again. Density 10 closes the top
+margin to 24 mm for a long reference held to a page count. The type does not shrink. Variance no longer
+adds kinds or table styles.
+
+## Worked source
+
+```markdown
+::: cover kicker="설치 안내서"
+:::
+
+# 개요
+
+이 안내서는 현장 게이트웨이를 처음 설치하는 운영 담당자를 위한 것이다. 작업에는 관리자 계정과 약 40분이 필요하다.
+
+::: sidebar title="용어"
+**게이트웨이**: 센서 신호를 모아 서버로 보내는 장치
+
+**펌웨어**: 장치에 들어 있는 제어 프로그램
+:::
+
+# 설치 순서
+
+::: callout kind=warning title="전원 차단 후 작업"
+배터리를 교체하기 전에 차단기를 내리고 잔류 전압이 0 V인지 확인한다.
+:::
+
+1. 차단기를 내린다. 상태 표시등이 꺼진다.
+2. 전면 덮개의 나사 4개를 푼다.
+3. 배터리를 교체하고 덮개를 닫는다.
+
+표 1. 오류 코드와 조치 (예시)
+
+| 코드 | 증상 | 조치 |
+|---|---|---|
+| E01 | 서버 연결 실패 | 네트워크 케이블 확인 |
+| E07 | 펌웨어 불일치 | 최신 펌웨어로 갱신 |
+
+자료: 제조사 기술 문서 (예시)
+```
+
+The sidebar floats beside the overview only if the overview is longer than the box; otherwise it is set
+full width under it. The caption prints as `<표 1>`, and `출처:` would be rewritten `자료:`.
+
+## Headings
+
+| Use | Not |
+|---|---|
+| 게이트웨이 설치 순서 | 게이트웨이를 설치한다 |
+| 펌웨어 갱신 전 확인 사항 | 갱신 전에 반드시 확인하세요 |
+| Error codes and actions | Fix errors before restarting |
+
+Steps inside a list are imperatives or plain statements; the headings above them stay noun phrases.
+`heading.declarative` reads headings, the title and the subtitle, not list items.
+
+## Numbers
+
+Limits, voltages and times sit in tables with their units and a source line. A duration or a count in
+the overview is written into its sentence ("약 40분"). Example values carry (예시) or (sample).
+
+## Failure patterns
+
+- Warnings collected in a list at the end, away from the steps they protect.
+- Headings typed with their own numbers (`1.1 준비물`), which doubles the decimal numbering.
+- Steps written as paragraphs; a reader at a bench needs one action per numbered item.
+- A sidebar longer than the text beside it, or a sidebar used for content the reader must follow in
+  order; move that content into the steps.
+- Reference tables with prose cells; move the explanation to a sentence under the table.

package/plugins/litclaude/skills/lit-docx/references/tonalities/memo.md

@@ -0,0 +1,137 @@
+# Memo
+
+Memo is the short document: an internal memo, a notice, a decision request, a letter of one or two
+pages. It has no cover and no components. Page 1 opens with a small label, the subject as the title,
+and To / From / Date / Subject rows between two hairlines; the body follows at once. The pack has no
+accent colour at all: everything is near-black ink, with muted grey only for the label, the notice and
+the folio. The memo should look like something a person wrote and sent, and its authority comes from
+the clarity of the first two sentences.
+
+## When to use it
+
+Choose Memo for 메모, 공지, 안내문, 협조 요청, a short decision request, a meeting follow-up, a cover letter
+for another document, or any English or Korean text under about 900 words. It is the first candidate
+for the memo type and the second for the itemised briefing. It moves up when the brief says one or two
+pages, when the source names recipients, or when the content is a single request or a single piece of
+news.
+
+## When it is the wrong choice
+
+- More than about two pages: without parts and a title block the text becomes a wall; use Report or
+  Brief.
+- A briefing for an executive who reads numbered points and a boxed request: Brief.
+- A document with several tables or figures that need captions and a summary strip: Report.
+- A proposal asking for money: Proposal carries the cover, budget and schedule.
+
+## Structure
+
+Memo has the fewest structural features of any pack, and that is its signature: a memo block instead
+of a title block, no components, no numbering, no contents and no running head on page 1. Rendered
+from the same source, any other tonality differs from it in at least three of those features
+(`qa_docx.py a.docx --compare b.docx`, check `tonality.structure`).
+
+- **Page 1: the memo block.** A small bold label in muted ink (the `kicker=` of `::: cover`, or 메모 /
+  Memo by default), the subject as the title at about 1.8 times the body, then the recipient rows
+  between two ink hairlines. Write those rows inside `::: cover` as lines of `Key: value` pairs
+  separated by ` · `. Recognised keys: `To`, `From`, `Date`, `Subject`, `Cc`, `받는 사람`, `보내는 사람`,
+  `날짜`, `제목`, `참조`. When no date row is written, the frontmatter date is inserted after the sender
+  in the Korean form `2026. 6. 30.`. English values start with a capital. Other lines in the block
+  render as an opening paragraph under the rows. The frontmatter `notice:` prints once under the block
+  in small muted text. `variant=` on the cover is accepted and ignored.
+- **Summary form.** No summary section: the opening paragraph is the summary. State the request or the
+  news and its date in the first two sentences.
+- **Numbering.** None. Short memos often need no headings at all; two to four parts under plain
+  headings (`# 배경`, `# 요청 사항`, `# 일정`) are the most a memo carries.
+- **Components.** None. A `::: callout` keeps its content as text, its title as a bold lead line with a
+  heading's space above it (12 pt), and stdout says so; that bold line is the memo's natural way to mark the request. Key figures become a
+  plain list with the basis in brackets. Do not plan components on the direction card; the purpose
+  line for each is "none".
+- **Tables.** One booktabs table at most, `<표 1>` above, `주:` and `자료:` under it.
+- **Running head.** The folio alone at the foot, right, from page 2. Nothing in the header.
+- **Contents.** None.
+
+## Tokens
+
+Values at the pack default (density 9, variance 2), from `templates/tonalities/memo.yaml`. The pack has
+no accent: the palette is ink, muted ink and a grey rule only.
+
+| Token | Value |
+|---|---|
+| Paper, margins | A4; top 25, bottom 27, left 25, right 25 mm; text block 160 mm |
+| Body | Pretendard 10.5 pt Korean / 11 pt English; Korean justified, English ragged right |
+| Line pitch | tight spacing: Hangul 165 % (Word multiple 1.08), Latin 120 % (0.78), the low ends of A4.3 |
+| Paragraph spacing | 5 pt after (4 pt English), no indent; a paragraph after a list stands 6 pt clear of it |
+| Heading space | h1 12 pt above, 5 below; h2 10 / 4; h3 9 / 3 (other packs 22 / 9, 15 / 6, 11 / 4) |
+| Scale (Korean) | h1 12.5 pt (1.2x), h2 11.5 pt (1.1x), h3 10.5 pt bold; subject title 19 pt (1.8x) |
+| Scale (English) | h1 13, h2 12, h3 11 pt bold; subject title 20 pt |
+| Ink | body and headings `#1A1A1A`; muted `#555555`; rules `#8C8C8C` |
+| Accent | no accent |
+| Memo block | 9.5 pt Korean / 10 pt English, labels bold, between two 0.5 pt ink hairlines |
+| Tables | booktabs, 9.5 / 10 pt, header bold, numbers right-aligned; cells 2 pt above and below |
+| Running head | folio from page 2, footer right, muted |
+| Components | none |
+| Figures | at most 0.40 of the frame height |
+| Fill | no page under 0.35 except the last (`fill.page`); a memo never spills onto a second page it fills under a quarter of the frame (`memo.fit`) |
+
+A memo stays on one page when its content allows: the pack's `spacing: tight` sets the tokens above,
+and the page check `memo.fit` (qa_docx.py --layout) fails a memo that spills less than a quarter of a
+page onto page 2; a longer second page is a two-page memo, which the pack allows. When it still spills, cut the lines that spill before reaching for the dials.
+
+**Dials.** Density 7 opens the margins to 27/29/27/27 mm, for a letter that is printed and signed. Density 10 closes the top margin to 24 mm, which may pull a memo that spills three
+lines onto page 3 back to two; cutting a sentence first is usually better. Variance changes nothing:
+the pack never gains a cover or a component.
+
+## Worked source
+
+```markdown
+---
+title: 회의실 예약 방식 변경 안내
+date: 2026-10-06
+tonality: memo
+---
+
+::: cover kicker="공지"
+받는 사람: 각 팀장 · 보내는 사람: 총무팀
+참조: 경영지원실장
+:::
+
+11월 1일부터 회의실은 사내 예약 시스템으로만 예약할 수 있습니다. 팀별 고정 예약 시간은 10월 17일(금)까지 알려 주시기 바랍니다.
+
+# 변경 내용
+
+종이 예약 대장은 10월 31일에 폐지합니다. 시스템 예약은 2주 앞까지 가능하며, 고정 예약은 팀당 주 2회로 제한합니다.
+
+# 문의
+
+총무팀 내선 1234
+```
+
+The frontmatter date appears as a `날짜` row reading `2026. 10. 6.` right after the sender. No ISO date
+is left in the Korean text; the gate check `date.iso` fails one.
+
+## Headings
+
+| Use | Not |
+|---|---|
+| 회의실 예약 방식 변경 안내 | 회의실 예약 방식이 바뀝니다 |
+| 요청 사항과 기한 | 17일까지 회신해 주세요 |
+| Room booking change | We are changing room booking |
+
+Write the subject row the same way as the title. `heading.declarative` reads headings, the title and
+the subtitle; the memo rows are not read by the gate, so the subject row depends on the writer.
+
+## Numbers
+
+A memo rarely needs a key figure. A deadline, an amount or a count goes into its sentence with its unit
+and date; example values carry (예시) or (sample).
+
+## Failure patterns
+
+- A memo written with a cover page or a decorative cover variant: Memo has none and sets the memo block
+  regardless.
+- Recipient lines written as running text ("To all team leads from …"); use `Key: value` pairs so they
+  become rows.
+- A callout or key-figure strip planned on the direction card: neither is drawn.
+- Headings at every second paragraph; a memo under a page often needs none.
+- A second page holding three lines: tighten the prose before raising density; the last page is exempt
+  from `fill.page`, so this is the reader's problem, not the gate's.

package/plugins/litclaude/skills/lit-docx/references/tonalities/proposal.md

@@ -0,0 +1,140 @@
+# Proposal
+
+Proposal is the plan or proposal as a document (제안서, 기획서, 사업 계획서): something a reader is asked
+to approve, fund or join. It is the only pack with a cover page of its own, and that cover is
+typographic: a label, a large title set left in the upper third of the page, one short wine-coloured
+rule, the subtitle and a lead paragraph, with the byline, date and notice at the foot. The body that
+follows is as plain as a report's: near-black headings without numbers, booktabs tables, one decision
+box and one key-figure strip. A proposal persuades through a clear request, an honest budget and a
+schedule a reader can check; the pages carry no brochure devices.
+
+## When to use it
+
+Choose Proposal for 사업 제안서, 기획서, 계획서, a grant or budget request, a partnership proposal written
+as a document, or a project plan with costs and a schedule. It is the first candidate for the proposal
+type. It moves up when the source asks the reader to approve an amount, when it holds a budget and a
+timeline, or when the document is sent ahead of a meeting where the decision will be taken.
+
+## When it is the wrong choice
+
+- A results report with a decision at the end: Report reads as evidence, Proposal as a request.
+- A one-to-three page decision request: Brief or Memo; a cover page on a two-page document wastes a
+  page.
+- A technical procedure: Manual.
+- A document whose reader expects no cover and numbered parts (a regulator, an audit): Report.
+
+## Structure
+
+Proposal differs from the other packs in its cover page, its unnumbered sections with a centred folio,
+and its budget-led body; any other tonality rendered from the same source differs from it in at least
+three structural features (`qa_docx.py a.docx --compare b.docx`, check `tonality.structure`).
+
+- **Page 1: a typographic cover page.** The label (`kicker=`, for example `사업 제안서`), the title
+  left-aligned about a fifth of the way down the page, a short rule in the accent, the subtitle, and
+  the lead paragraph written inside `::: cover`. The byline, the date in the form `2026. 6. 30.` and the
+  frontmatter `notice:` stand at the foot of the cover. There is no colour block and no figure on the
+  cover; `variant=` is accepted and ignored. The body starts on the next page, numbered 1.
+- **Summary.** `# 제안 요약` / `# Summary` as prose: the request in one sentence, then why now. The
+  key-figure strip (cost, time, result) is set after the summary's first paragraph; figures written
+  inside the cover block are moved there automatically.
+- **Numbering.** Sections are unnumbered. Levels part by weight and the space above.
+- **Components and their purpose.** Three kinds are allowed: `keyfigures` (one strip of three
+  comparable numbers the reader will be asked to approve), `callout` (one box at most, the decision
+  asked and its date), and `columns` (two blocks of nearly equal length, such as quantitative and
+  qualitative effects). Every component needs its purpose line on the direction card.
+- **Budget and schedule.** `# 소요 예산` and `# 추진 일정` as booktabs tables, a total row in bold under
+  a thin rule, the unit hoisted to a `(단위: 백만 원)` line when every amount column shares it.
+- **Running head.** The folio alone, centred at the foot; nothing on the cover. No header.
+- **Contents.** None by default; a proposal long enough to need contents is usually a report.
+
+## Tokens
+
+Values at the pack default (density 8, variance 6), from `templates/tonalities/proposal.yaml`.
+
+| Token | Value |
+|---|---|
+| Paper, margins | A4; top 26, bottom 28, left 26, right 26 mm; text block 158 mm |
+| Body | Pretendard 10.5 pt Korean / 11 pt English; Korean justified, English ragged right |
+| Line pitch | Hangul 175 % (Word multiple 1.14), Latin 133 % (0.87) |
+| Paragraph spacing | 6 pt after (5 pt English), no indent |
+| Scale (Korean) | h1 14.5 pt (1.4x), h2 12.5 pt (1.2x), h3 10.5 pt bold; cover title 28.5 pt (2.7x) |
+| Scale (English) | h1 15.5, h2 13, h3 11 pt bold; cover title 29.5 pt |
+| Ink | body and headings `#1A1A1A`; muted `#555555`; rules `#8C8C8C` |
+| Accent | wine `6E2639`, on the cover title rule and the callout rule only |
+| Tables | booktabs, 9.5 pt Korean / 10 pt English, header bold, numbers right-aligned |
+| Key figure | h2 size, bold, in ink over an ink hairline, three per row |
+| Running head | folio centred at the foot, 8.5 / 9 pt muted; none on the cover |
+| Components | keyfigures, callout (one at most), columns |
+| Figures | at most 0.60 of the frame height |
+| Fill | no body page under 0.35 (`fill.page`) |
+
+**Dials.** Density 6 or 7 opens the margins to 27/29/27/27 mm and the Hangul pitch to 180 %, for a
+printed proposal handed over in a meeting. Density 10 closes them to 24/26/25/25 mm for a proposal held
+to a page limit by a call for proposals; the body never drops below 10.5 pt. Variance no longer adds
+kinds, table styles or cover looks.
+
+## Worked source
+
+```markdown
+::: cover kicker="사업 제안서"
+예시 기관의 창고 두 곳에 재고 자동 추적을 도입하는 계획이다. 실사 시간과 출고 오류를 함께 줄이는 것이 목표다.
+:::
+
+# 제안 요약
+
+창고 두 곳에 재고 자동 추적 장비를 도입하는 사업비 4.2억 원의 승인을 요청한다.
+
+::: keyfigures cols=3
+- **4.2억 원** 총사업비 (예시)
+  - 2027년 1-12월, 장비와 구축 포함
+- **11개월** 투자 회수 기간 (예시)
+  - 연간 절감액 4.6억 원 기준, 내부 추정
+- **38%** 재고 실사 시간 감소 (예시)
+  - 시범 창고, 2026년 3-5월 측정
+:::
+
+::: callout kind=key title="결정 요청"
+2027년 예산 편성 전, 2026. 11. 30.까지 사업 추진 여부를 결정해 주시기 바랍니다.
+:::
+
+# 소요 예산
+
+표 1. 항목별 소요 예산 (예시)
+
+| 항목 | 상반기 (백만 원) | 하반기 (백만 원) |
+|---|---|---|
+| 장비 | 180 | 60 |
+| 구축 | 70 | 50 |
+| 합계 | 250 | 110 |
+
+자료: 공급사 견적, 내부 추정 (예시)
+```
+
+## Headings
+
+| Use | Not |
+|---|---|
+| 재고 자동 추적 도입 계획 | 재고 자동 추적을 도입하면 비용이 줄어든다 |
+| 소요 예산과 회수 기간 | 11개월이면 투자금을 회수할 수 있다 |
+| Expected benefits | This plan pays for itself in a year |
+
+The title and subtitle are labels too; the persuasive sentence goes in the cover's lead paragraph and
+the first sentence of the summary. `heading.declarative` fails a heading, title or subtitle written as
+a sentence.
+
+## Numbers
+
+Key figures sit at the h2 size in the summary, never on the cover. Each carries a label and a basis
+line (period, scope, source). Estimates say (추정), (예시) or (estimate) in the label, and a payback or
+saving shows the assumption it rests on. A figure without a basis is written into a sentence.
+
+## Failure patterns
+
+- A cover holding six figures: none stays on the cover, only the first strip is drawn in the summary,
+  and the rest belong in the budget table.
+- A second callout for a risk: only one box is drawn (decision request first); write the risk as a
+  short part with its own heading.
+- Every part opened with a full-page picture: the median fill drops below 0.75 and the argument
+  disappears; one picture per part at most.
+- A budget table split over two pages (`table.split`); start it at the top of a page or shorten it.
+- Expecting each part to start on a new page: there is no forced break before an h1.