@litfamily/litopencode 1.0.16 → 1.0.17

package/skills/lit-docx/references/examples/09-brief-en.md

@@ -0,0 +1,64 @@
+---
+title: Sunday opening at four more branch libraries
+subtitle: Case for a six-month trial from January 2027
+author: Library Services Manager
+organization: Brookmere sample borough
+date: 2026-10-19
+short_title: Sunday opening trial
+notice: "Sample brief: the borough, branches, visit counts and costs are invented examples."
+tonality: Brief
+---
+
+::: cover kicker="Decision brief"
+:::
+
+::: callout kind=key title="Decision requested"
+Approve a six-month trial of Sunday opening, 12:00 to 16:00, at Eastfield, Kings Row, Millbrook and Thorne branches from 4 January 2027, at a cost of £19,600 from the libraries modernisation budget.
+:::
+
+# Summary
+
+Three of the borough's seven branches already open on Sundays, and they are busy. They averaged 310 visits each Sunday afternoon in the year to September 2026, which is more per opening hour than any weekday evening.
+
+Families and shift workers are the main Sunday users. In the 2026 user survey, 44 % of Sunday visitors said they could not come on any other day, against 19 % of weekday visitors.
+
+The trial costs £19,600 for twenty-six Sundays. Almost all of it is staff time: two members of staff per branch for four hours, paid at the weekend rate.
+
+We will judge the trial on visits per opening hour. If the four branches reach two thirds of the current Sunday average by the end of June, we will propose permanent Sunday opening in the 2027/28 budget.
+
+# Current Sunday use
+
+Table 1. Visits per Sunday afternoon and per opening hour (weekday: evening hours) at the three Sunday branches, October 2025 to September 2026
+
+| Branch | Sunday visits | Per hour, Sunday | Per hour, weekday |
+|---|---:|---:|---:|
+| Central | 420 | 105 | 71 |
+| Harbour Road | 280 | 70 | 48 |
+| Westgate | 230 | 58 | 39 |
+| Average | 310 | 78 | 53 |
+
+Source: Door counter data, library management system (sample).
+
+The four trial branches were chosen because they are the furthest from an existing Sunday branch. Residents of Eastfield and Thorne currently need two buses to reach Central on a Sunday.
+
+# Cost and staffing
+
+Table 2. Trial cost for twenty-six Sundays
+
+| Item | Basis | Cost (£) |
+|---|---|---:|
+| Staff time | 2 staff × 4 h × 26 Sundays × 4 branches × £18.50 | 15,392 |
+| Heating, lighting and security | £40 per branch per Sunday | 4,160 |
+| Total | Rounded to £19,600 in the request | 19,552 |
+
+Staff will work Sundays by volunteer rota first. The union branch has agreed the rota terms, and fourteen staff have already put their names forward, enough to cover all four branches without compulsory shifts.
+
+# Risks
+
+Turnout may be slow in the first weeks while residents learn about the change. Leaflets go to every household in the four catchment areas in December, and each branch will promote Sunday opening at its weekday story sessions.
+
+A wet winter would depress visits at all branches. To keep the comparison fair, results will be read against the three existing Sunday branches over the same weeks, not against last year.
+
+# Next steps
+
+With approval by 31 October, the rota closes on 21 November and the four branches publish their Sunday hours in the December newsletter. A mid-trial report on visits per opening hour goes to the libraries board in April 2027, and the final report with the budget proposal in July.

package/skills/lit-docx/references/page-composition.md

@@ -0,0 +1,306 @@
+# Page composition
+
+This file describes the page every tonality builds and what the author controls from the Markdown
+source: the A4 frame and its margins, the typeface and type sizes, colour, tables, Korean writing
+conventions, leading, line breaking in Word, pagination, and the running head. Most of these are fixed
+by the pack and applied by the converter; the author's part is to write a source that the fixed page
+can carry without forcing it.
+
+The look all six packs share is restraint. Black-ink text and headings, headings only a step or two
+larger than the body, tables drawn with three rules, one accent colour at most, no tinted panels, no
+decorative numerals. A document built this way is read for its content, and the few elements that do
+stand out (a decision box, a key-figure strip) are noticed because nothing else competes with them.
+
+## The frame
+
+Every pack sets A4 (210 × 297 mm). The margins come from the density dial; at the density most packs use
+(9) they are 25 mm at the top and sides and 27 mm at the bottom. The sides never drop below 25 mm and the
+bottom is never smaller than the top, so the text block is 160 mm wide at most: about 40 to 45 Hangul
+syllables or 75 to 85 Latin characters per line at 10.5 pt. The header and footer sit 12 mm from the
+paper edge at most.
+
+Journal sets the body in two columns 6 mm apart. A table with more than three columns in a Journal body
+is lifted out into a full-width band, together with its caption, and the columns resume underneath; a
+table of three columns or fewer stays inside its column at the column's width.
+
+## Typeface and sizes
+
+Pretendard is the face for Hangul, Latin and headings in every pack except Journal, which sets Latin body
+text in Times New Roman and keeps Pretendard for Hangul and headings. The converter writes the face
+names into the document defaults, every style, the theme fonts and the list glyphs, so a renderer has no
+default face to fall back on. Do not ask for another face in a tonality document; a typeface requirement
+from the user is a reason to use the publisher path or a supplied template.
+
+Body text is 10.5 pt (11 pt for English Memo and English Proposal) and never smaller. The other sizes
+are derived from it, rounded to the half point:
+
+| Element | Report | Brief | Manual | Proposal | Memo | Journal |
+|---|---|---|---|---|---|---|
+| Body (Korean) | 10.5 | 10.5 | 10.5 | 10.5 | 10.5 | 10.5 |
+| h1 | 14.5 | 13.5 | 14 | 14.5 | 12.5 | 13.5 |
+| h2 | 12.5 | 12 | 12 | 12.5 | 11.5 | 12 |
+| h3 | 10.5 bold | 10.5 bold | 10.5 bold | 10.5 bold | 10.5 bold | 10.5 bold |
+| Title | 26.5 | 26.5 | 26.5 | 28.5 | 19 | 26.5 |
+
+English Proposal steps up from its 11 pt body (h1 15.5, h2 13, title 29.5) and English Memo likewise
+(h1 13, h2 12, title 20). Table text is 9.5 pt, note and source lines 9 pt and the running head 8.5 pt
+(10, 9.5 and 9 pt under an 11 pt body); a key figure takes the h2 size. A title that would need a fourth line, or that holds a word wider than the
+measure, is stepped down a point at a time until it fits in three lines.
+
+## Headings
+
+Headings are bold, left-aligned and in the body ink. Levels differ by size, weight and the space around
+them, never by colour, underline or a box. Space above is about twice the space below (h1 22 pt above and
+9 pt below, h2 15 and 6, h3 11 and 4), and every heading keeps with the paragraph that follows it. The only
+rule a heading carries is the Brief's full-width hairline above each h1, which stands in for a section
+number.
+
+Use at most three levels. Open every h1 section with at least one paragraph before its first h2, so two
+headings never stand back to back; the converter does not insert that paragraph for you.
+
+Numbers, where the pack uses them, are added by the converter in plain ink at the heading's own size.
+Do not type them in the source.
+
+- Korean Report: `Ⅰ.` for h1, `1.` for h2, `가.` for h3, each followed by one space.
+- English Report, Manual and Journal: `1`, `1.1`, `1.1.1`, followed by a tab, with the heading texts of a
+  level aligned on one line however wide the widest number is.
+- Brief, Proposal and Memo: no numbers.
+- A back-matter heading (References, Acknowledgements, 참고문헌, 감사의 글) is never numbered.
+
+A heading, the title and the subtitle are noun-phrase labels. The gate's `heading.declarative` check
+fails a Korean label whose last word ends like a sentence (-다, -니다, -요, -죠, or a nominalised claim
+such as -함, -됨, -있음) and an English label that ends with a full stop or contains an auxiliary (is,
+are, has, will, can, does) or one of a list of finite verbs. That list includes words that are also nouns:
+works, needs, leads, shows, cuts, pays, takes, saves, matters, drops. "Staffing needs" fails; "Staffing
+requirements" passes. The finding goes in the first sentence under the heading, not in the heading.
+
+## Colour
+
+Each pack has a three-value ink palette: text #1A1A1A, muted #555555 for note lines and the running
+head, line #8C8C8C for hairlines. Every style in the document is set to the ink, including the heading
+styles the build does not use, so a reader who applies Heading 5 later still gets black text. Hyperlinks
+are recoloured to the ink.
+
+Four packs declare one accent and name at most two places for it:
+
+| Pack | Accent | Places |
+|---|---|---|
+| Report | #1F3A5F | title rule, callout rules |
+| Brief | #2D5A47 | title rule, callout rules |
+| Manual | #2E4A66 | callout rules, sidebar rule |
+| Proposal | #6E2639 | cover rule, callout rules |
+| Memo | none | none |
+| Journal | none | none |
+
+The accent is never used on text, fills or headings. The gate's restraint checks fail a tonality
+document that has more than one hue outside the ink, an accent on more than two kinds of element, a
+coloured heading (`heading.ink`), an h1 more than 1.5 times the body (`heading.ratio`), a shaded data
+table cell (`table.fill`), or a coloured or shaded notice in a page header (`furniture.chip`). These
+are produced only by hand edits or a custom template; a source converted with a pack does not trigger
+them.
+
+## Paragraphs and alignment
+
+Paragraphs are separated by space (6 pt after a Korean paragraph, 5 pt after an English one) and never
+also by a first-line indent. Korean body text is justified in Report, Brief, Proposal and Memo, with
+kinsoku on so a closing bracket or full stop never starts a line. Manual and Journal set Korean ragged
+right. English text is ragged right in every pack.
+
+## Leading
+
+The body line pitch is a percentage of the body size: 175 % for Korean and 133 % for English at the
+density most packs use, rising to 185 % and 140 % at low density. The converter writes it to Word as a
+line-spacing multiple, and the multiple is not the percentage divided by 100.
+
+A single line in Word is not 1.0 em. Measured on rendered pages, Pretendard's single line is about
+1.55 em in Word and 1.51 em in LibreOffice; the converter uses the mean, 1.53 em. Times New Roman's is
+about 1.15 em. The multiple is the pitch divided by that single-line height:
+
+- Korean body at density 9: 1.75 / 1.53 = Multiple 1.14.
+- English body in Pretendard at density 9: 1.33 / 1.53 = Multiple 0.87.
+- English body in Journal (Times New Roman) at density 9: 1.33 / 1.15 = Multiple 1.16.
+
+The habit of setting "1.6 line spacing" for Korean text produces a 245 % pitch with Pretendard, which is
+why documents set that way look loose and run long. Headings use a 130 % pitch, captions, table cells and
+note lines 140 %. When editing a converted document by hand, leave the paragraph spacing alone.
+
+## Line breaking in Word
+
+The converter marks the document Korean (`ko-KR` as the East Asian language of the defaults) and sets
+`wordWrap` and `kinsoku` on in the Normal style. With these, Word wraps Hangul between words (어절) as a
+Korean reader expects. LibreOffice ignores the setting and breaks Hangul between syllables whatever the
+document says, so a page rendered through LibreOffice for checking shows syllable breaks that Word will
+not show. Do not rewrite body text to move those breaks.
+
+Titles, subtitles and headings are a different case: the converter breaks the title between words
+itself, in the fewest and most even lines that fit, and the gate's `heading.wrap` check fails any
+heading or title that a rendered page breaks inside a word. A heading that keeps failing is too long for
+its column; shorten the label.
+
+## Tables
+
+Every tonality draws booktabs: a 1 pt rule above and below the table, a 0.5 pt rule under the header row,
+no vertical rules, no inner horizontal rules, no fills. The header row is bold ink. A last row whose first
+cell is 합계, 총계, 소계, 계, Total or Sum is bold under its own 0.5 pt rule. Cells have 3.5 pt padding above
+and below and 5 pt at the sides.
+
+A column whose body cells are all numbers is right-aligned in tabular figures. The test is strict: a cell
+may hold a sign, digits with commas or points, an optional bracketed note, and a short unit after the
+number (%, %p, 배, a Hangul unit of up to three syllables, or a Latin unit of up to three letters). A
+currency symbol in front (£15,392, ₩2,000, $40) or free text in one cell makes the whole column text, and
+the publisher-style audit then reports the numbers as misaligned. Put the currency or unit in the header
+cell instead: `Cost (£)`, `금액 (만 원)`. A dash or an empty cell is allowed in a numeric column.
+
+No column is made narrower than its longest word plus padding; the room is taken from the widest column.
+Keep cell text short. A table is evidence, not prose: if a cell needs two sentences, the content belongs
+in the text above the table.
+
+## Korean conventions
+
+These apply on every path, including publisher profiles:
+
+- **Captions.** A table caption stands above its table as `<표 1> 제목`, a figure caption as `[그림 1] 제목`.
+  Write `표 1. 제목` or `그림 1. 제목` in the source and the converter sets the bracket form with a bold
+  label.
+- **Units.** When every header cell after the first ends in the same unit in brackets, for example
+  `2025년 (건)` and `2026년 (건)`, the unit moves out of the cells into one line `(단위: 건)` right-aligned
+  above the table. Mixed units stay in the cells; that is correct, not a fault.
+- **Notes and sources.** Below the table, `주:` first and `자료:` after it, each its own paragraph, at note
+  size. A source written `출처:` is rewritten as `자료:`.
+- **Dates.** `2025. 1. 2.` or `2025년 1월 2일` in the text; never `2025-01-02`. The converter rewrites ISO
+  dates in the Korean body and formats the frontmatter `date:`, but not dates inside other frontmatter
+  fields (subtitle, notice, abstract), so write those the Korean way yourself. Do not start a line with
+  a hand-written date such as `2026. 3. 2.`: Markdown reads a line that opens with a number and a full
+  stop as a numbered list. The gate's `date.iso` check fails any ISO date left in a Korean document.
+- **Lists.** Write Markdown `-` lists; the converter draws them with an en dash at every level in Korean
+  documents. A government-style `○` line typed as text is acceptable inside a 개조식 passage. A list of one
+  item is set as a plain paragraph without a symbol. Numbered lists restart at 1 after any break.
+- **No glyph markers.** No filled or hollow squares, arrowheads, check marks or emoji in headings, list
+  heads or table cells.
+- **Emphasis.** Hangul is emphasised by weight only. The converter removes italic from any run that holds
+  Hangul. Use bold sparingly: a bold keyword in every sentence reads as machine-made.
+- **Numbers and units.** Choose one spacing style for numbers and units and keep it (`12kW` or `12 kW`).
+  A number written with a space before an SI unit is held together with a no-break space. A hyphen between
+  two digits becomes an en dash (1–3); a spaced hyphen between words becomes an em dash, which the prose
+  lint then reports, so use a comma or a full stop instead.
+
+## Pagination
+
+The converter never forces a page break before a heading. It keeps each heading with its next paragraph,
+keeps a short paragraph (under 60 characters) after a heading with the paragraph after that, turns widow
+and orphan control on, and keeps a closing paragraph of up to about four lines with the block before it,
+so the last page never holds one orphaned paragraph. A component box does not split across pages, and a
+box under a paragraph or list item stands 6 pt clear of it.
+
+**Lists and headings.** A list of up to six items keeps together: every item but the last keeps with the
+next, and a lead-in of a line or two right before it ("다음 단계는 아래와 같다.") keeps with the list. In
+a two-column body a list of five or six items may break once: the lead-in keeps with the first two items
+and the last two stay together, so the block no longer jumps to the next column and leaves a third of a
+column empty. The last section of a single-column document, with no table or picture and about twelve
+lines or fewer, keeps whole, so its paragraph goes to the last page with its list. In
+a single-column body a heading keeps its short lead sentence (about 200 characters) with a table of up to
+eight body rows it opens, caption and unit line included, so the heading and its sentence never wait at
+a page foot while the table starts the next page.
+
+**Short documents.** A source of about one page (the converter's estimate) is set with tight spacing in
+any tonality, as a memo is, so it does not spill a few lines onto a second page. A section that opens
+under a hairline right after a ruled box draws no second rule.
+
+**Tables.** A table whose estimated height fits in 0.9 of the frame is kept on one page with its caption,
+unit line and note lines. A long table, meaning a header plus six or more body rows, may break between
+rows with the header row repeated, but only where a quarter of the frame or more is left: the header
+stays with at least three body rows (or rows worth a quarter of the frame), and the last three body rows
+stay together. Any other split fails the gate's `table.split` check.
+
+Table columns: no column is narrower than its longest word, and a text column whose cells wrap while the
+others hold their longest cell with room to spare takes that room; a header may take two lines, and no
+column gives up room below its own longest data cell. Negative figures in tables take the minus sign
+(−), Korean tables too. A sentence right above a table without a caption keeps 6 pt under itself. Under a
+publisher profile the paragraph after a table stands three quarters of a body line clear, a paragraph
+after a list 6 pt, and a list of up to six items keeps together. A table too tall for a page in any
+case should be cut down to the rows the text discusses, with the full data in an appendix or a workbook.
+
+**Figures.** A picture is scaled to the text width and to a share of the frame height set by the pack
+(Proposal 60 %, Report and Manual 45 %, Brief, Memo and Journal 40 %), and keeps with its caption. A
+figure caption on another page than its picture fails `figure.split`.
+
+**Fill.** No body page may be filled to less than 0.35 of its frame; the cover and the last page are
+exempt. A short page almost always comes from a large table or figure that could not fit in the space
+left and moved whole to the next page. The fixes, in order: put a lead sentence or the paragraph that
+discusses the table above it, move the table below the next paragraph, or shorten the table.
+
+## Running heads and folios
+
+The running head is set at 8.5 pt in the muted ink, regular weight, with the short title on one side and
+the folio on the other, or the folio alone. It never appears on the page that carries the title block or
+on a cover page. The folio is the page number alone, never "page / total". The short title is the
+frontmatter `short_title`, or the title cut at a word boundary near 40 characters; give every document of
+more than two pages a `short_title`.
+
+| Pack | Header | Footer |
+|---|---|---|
+| Report | none | short title left, folio right |
+| Brief | none | folio right |
+| Manual | short title | folio right |
+| Proposal | none | folio centred, starting at 1 after the cover |
+| Memo | none | folio right |
+| Journal | short title left, folio right | none |
+
+## The sample-data notice
+
+When the content is invented or illustrative, the frontmatter `notice:` states it once, in ink, at the
+furniture size: under the title rule on a masthead, under the memo or control block, or at the foot of a
+cover page. It is never repeated in page headers in a tonality document. Write it as a plain statement
+("예시 데이터. 회사, 금액, 수치는 모두 가정이다." / "Sample report. The council, figures and costs are
+invented examples.") and keep invented values realistic. Never leave a bracketed blank, a to-be-decided
+marker, a run of capital X, doubled circles or a line of underscores in the source: the gate's content
+check fails on any of them, and it also treats any short bracketed text without a digit, such as a
+bracketed company name, as a blank.
+
+## What the gate checks
+
+`python3 <skill>/run.py qa draft.docx --source draft.md` runs the checks that read the Word file and the
+source: file integrity, missing headings and blanks, prose lint on the source, and the structural and
+restraint checks. Adding `--layout` renders the document through LibreOffice and adds the page checks.
+The JSON report's `failure_reasons` lists what failed; `lint.prose`, `lint.design` and `output.findings`
+hold the details.
+
+| Check | Needs `--layout` | Usual cause | Fix in the source |
+|---|---|---|---|
+| `heading.declarative` | no | a heading written as a claim | rewrite as a noun phrase; move the claim into the first sentence |
+| `heading.order` | no | an h3 straight under an h1, or a document opening at h3 | add the missing level or promote the heading |
+| `date.iso` | no | an ISO date in a frontmatter text field or a table cell | write `2026. 10. 5.` |
+| `component.budget` | no | a fourth component kind, a second key-figure strip | drop the component without a purpose line |
+| `fill.page` | yes | a large table or figure pushed to the next page | lead sentence above it, or move it below the next paragraph |
+| `heading.stranded` | yes | a heading over a table or figure that moved | a short lead sentence under the heading |
+| `heading.wrap`, `title.lines` | yes | a label too long for its measure | shorten the label; move detail to the subtitle |
+| `table.split` | yes | a table that fits a page split anyway, or a caption apart from its table | lead sentence above, or shorten the table |
+| `figure.split` | yes | picture and caption on different pages | make the picture smaller in its source |
+| `sidebar.overlap` | yes | too little text after a floating sidebar | add the paragraphs that belong there, or place the sidebar earlier |
+| `component.variety` | yes | four or more pages and fewer than two component kinds | add a component the direction card justifies, or tighten to three pages |
+| `cover.block` | yes | a filled shape over a quarter of the cover | a hand edit or template; rebuild from the source |
+| `memo.fit` | yes | a memo spilling a few lines onto page 2 (under a quarter of the frame) | cut the lines that spill; the Memo pack's tight spacing already applies |
+| `page.spill` | yes | page 2 of a two-page document under 0.4 of the frame, or a last page under an eighth | set the source on one page, give page 2 a whole section, or move the closing box earlier |
+| `list.split` | yes | a list of up to six items over two pages or columns (one break of a five- or six-item list in a column, two items or more each side, is allowed) | keep the lead-in short; split a long list into two with a sentence between |
+| `heading.apart` | yes | a heading and its lead sentence at a page foot, the table they open on the next page | a shorter lead, or the sentence under the table |
+| `heading.column` | yes | in a two-column body a heading at the foot of a column, its first lines in the next column | the converter spans a `자료:` or `Source:` line with its page-wide table; otherwise a shorter paragraph before the heading |
+| `columns.balance` | yes | in a two-column body a column stopping a quarter of the frame short beside one that runs to the foot, or a last page with one column under half the depth of the other | the converter closes the columns with a continuous break and lets a five- or six-item list break once; otherwise move a long block |
+| `notice.dash` | no | a notice written `예시 데이터 — …` | write `예시 데이터: …` (quote the value in the frontmatter) |
+
+For `component.variety`, the page-1 block counts as a kind when it is a cover page, a memo block, a
+control block or the title page of a two-column Journal, and a Journal's two-column body counts as
+columns. A four-page Report with a masthead therefore needs two of callout, key figures and columns.
+
+The prose lint reads the source per h1 section. The rules most often hit by a fresh draft:
+
+- sentence lengths that vary too little within a section of four or more sentences and 80 or more words
+  (mix short and long sentences);
+- a spaced hyphen between words, or two em dashes in one section;
+- in Korean, three or more of 하였다, 되었다, 할 수 있다 and similar endings in one section, translationese
+  (에 있어서, 살펴보면), and loanwords such as 리뷰 and 리서치;
+- in English, stock words (delve, furthermore, moreover, leverage, robust, comprehensive), two hedges in
+  one sentence (perhaps, potentially, could, might), and three or more intensifiers (very, highly,
+  extremely) in one section.
+
+Section names Introduction, Methods, Results and Discussion pull in manuscript rules (citations, passive
+voice); a report does not need those names.

package/skills/lit-docx/references/tonalities/brief.md

@@ -0,0 +1,104 @@
+# Brief
+
+Pack: `templates/tonalities/brief.yaml` · dials density 9, variance 3 · accent #2D5A47 on the title rule
+and callout rule.
+
+## Purpose
+
+A Brief puts a decision in front of someone who will read the first page and perhaps the second. It runs
+one to three pages and is built conclusion first: the decision request stands directly under the title
+block, then a summary of three or four numbered points, then the supporting sections. Korean 검토 보고,
+현황 보고 and decision papers for a committee fit here, as do English decision briefs and options papers.
+
+## Wrong for
+
+- More than three pages of material, or four or more tables that all matter: use a Report and keep the
+  decision callout.
+- A notice that asks for no decision: use a Memo.
+- A step-by-step procedure: use a Manual.
+- A project funding request with budget and schedule detail: use a Proposal.
+
+## Structure
+
+| Feature | What the pack sets |
+|---|---|
+| Page 1 | compact masthead: series line, title, subtitle, byline, rule, notice; then the first `kind=key` callout, moved to the top by the converter wherever it stands in the source |
+| Summary | the paragraphs of the first h1 become numbered points ① to ④, each opening with its first sentence in bold |
+| Numbering | none; each h1 opens under a full-width ink hairline |
+| Components | callout (one box at most), columns |
+| Running head | footer: folio right; none on page 1 |
+| Contents | never |
+
+The summary treatment is automatic. The converter takes the plain paragraphs under the first h1, up to
+four, prefixes ①, ②, ③, ④ and sets the first sentence of each in bold: everything up to the first `다.`,
+or the first full stop, question mark or exclamation mark followed by a space. Lists, tables and
+components in that section are left as they are. A fifth paragraph is left without a number.
+
+## Type scale
+
+Body 10.5 pt, h1 13.5 pt, h2 12 pt, h3 10.5 pt bold, title 26.5 pt. Korean justified. The h1 hairline is
+0.5 pt in ink with 6 pt of space between the rule and the heading text.
+
+## Components
+
+- **Callout.** One `kind=key` box holding the decision request: who decides, what exactly, by when, at
+  what cost. The pack caps callouts at one; any other callout is set as text with its title in bold.
+- **Columns.** Two balanced blocks for options compared side by side. Each block opens with a bold label
+  ("방안 A.", "Option B.") and states scope, cost and effect in the same order.
+
+Key figures and sidebars are not drawn: the strip would compete with the numbered points, and the points
+already carry the numbers.
+
+## Writing the source
+
+- Write the decision callout first or last; it ends up at the top either way. Phrase it as a request with
+  the amount and the date.
+- Make the first h1 the summary. Write three or four paragraphs. The first sentence of each must work
+  alone in bold: a complete finding with its number. The rest of the paragraph supports it.
+- Keep the first sentence free of decimal points before its end if possible; the bold lead stops at the
+  first full stop followed by a space, which a decimal is not, but an abbreviation such as "approx. 40"
+  is.
+- Use one table at most for the current state, and keep it under eight rows.
+- Close with risks and their mitigations. A Brief has no conclusion section: the conclusion is at the top.
+
+## Source fragment
+
+```markdown
+---
+title: 사옥 주차장 유료화 검토
+subtitle: 월 정기권 도입과 방문객 무료 시간 조정
+author: 예시 공사 총무부
+organization: 예시 공사(가상 기관)
+date: 2026-11-03
+notice: 예시 데이터. 기관, 주차면 수, 요금은 모두 가정이다.
+tonality: Brief
+---
+
+::: cover kicker="검토 보고"
+:::
+
+# 요약
+
+직원 차량에 월 3만 원의 정기권을 도입하면 출근 시간대 만차 시각이 8시 40분에서 9시 20분으로 늦춰진다.
+대중교통 지원금 신청자가 늘어 정기권 구매 차량이 등록 차량의 70% 수준에 머물 것으로 보았다.
+
+방문객 무료 시간은 2시간에서 1시간으로 줄인다. 민원 상담 평균 체류 시간이 48분이어서 대부분의
+방문객은 영향을 받지 않는다.
+
+연간 순수입은 약 1억 2천만 원이다. 정기권 수입에서 주차 관제 장비 임차료와 관리 인건비를 뺀 값이다.
+
+::: callout kind=key title="결정 요청"
+2027년 1월부터 직원 월 정기권(3만 원)과 방문객 무료 1시간 기준을 시행하는 방안을 승인해 주시기 바랍니다.
+:::
+```
+
+On the page the callout stands first under the title rule, followed by the hairline and the 요약 heading,
+then three points ① ② ③ with their first sentences in bold.
+
+## Before delivery
+
+- The rendered document is three pages or fewer. If it is longer, the direction was wrong.
+- Each numbered point's bold sentence states a finding, not a topic ("비용" is a topic; "연간 순수입은 약
+  1억 2천만 원이다." is a finding).
+- The decision callout names the amount, the start date and who must approve.
+- Numbers in the points match the table and the option blocks.

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

@@ -0,0 +1,101 @@
+# Journal
+
+Pack: `templates/tonalities/journal.yaml` · dials density 9, variance 6 · no accent.
+
+## Purpose
+
+Journal is for long-form reading at a desk: a white paper, an essay, a newsletter feature, a research
+summary written for practitioners or a committee rather than for a named journal. The body is set in two
+columns with a title block that carries the byline, an abstract and keywords, close in feel to a
+publisher's article page but built by the tonality engine. The reader goes through the argument in order.
+
+A manuscript for submission to a named journal is not a Journal tonality document. It goes down the
+publisher path: `--publisher elsevier` (or acs, ieee, nature) for conversion and `--publisher elsevier
+--kind manuscript` for the gate.
+
+## Wrong for
+
+- A submission to a named journal: use the publisher profile.
+- Many wide tables: two columns cut a table of four or more columns out into full-width bands, and a
+  document made mostly of bands reads badly. Use a Report.
+- A decision document: use a Brief.
+
+## Structure
+
+| Feature | What the pack sets |
+|---|---|
+| Page 1 | masthead: series line (kicker and date), title, subtitle, byline, affiliations and corresponding address when given, a rule in ink, the notice, then the abstract and keywords from the frontmatter; the two-column body starts under it on the same page |
+| Summary | the frontmatter abstract, set under the label 초록 / Abstract |
+| Numbering | 1 / 1.1 / 1.1.1, for cross-references in the text ("see section 3") |
+| Components | callout only; the two-column body counts as columns for the gate |
+| Running head | header: short title left, folio right; none on page 1 |
+| Contents | never |
+
+## Type scale
+
+Body 10.5 pt; Latin body text in Times New Roman, Hangul and all headings in Pretendard. h1 13.5 pt, h2
+12 pt, h3 10.5 pt bold, title 26.5 pt. Ragged right in both languages, which avoids wide word spaces in a
+narrow column. Columns are 6 mm apart; figures are held to 40 % of the frame height.
+
+The English body leading in Times New Roman is 133 % at density 9, written to Word as Multiple 1.16,
+because Times New Roman's single line is about 1.15 em where Pretendard's is 1.53 em.
+
+## Components
+
+- **Callout.** One `kind=note` box for a reading aid, such as how to read a measurement or a definition
+  the argument depends on. The box takes the column width.
+- **Tables.** Three columns or fewer stay inside the column at its width; four or more span both columns
+  with their caption. Prefer narrow tables.
+- No key figures, no sidebar, no extra `columns` block: the page is already two columns.
+
+## Writing the source
+
+- Put the abstract in the frontmatter as `abstract:` (one paragraph, quoted) and the keywords as a list
+  `keywords: [a, b, c]`. Do not repeat the abstract as a body section.
+- Use `author:` for a team or a single byline. `authors:` as a list of names and `affiliations:` as a
+  numbered mapping are also printed, the affiliations at note size under the byline.
+- Write in sections with clear noun-phrase headings. Avoid the names Introduction, Methods, Results and
+  Discussion unless the document really is an article in that form; the prose lint applies manuscript
+  rules (citation density, passive voice) to sections with those names.
+- Keep paragraphs moderate in length; a two-column page shows a long paragraph as a wall.
+- Number tables and refer to them by number; the converter keeps each caption with its table.
+
+## Source fragment
+
+```markdown
+---
+title: 오래된 학교 건물의 겨울철 실내 공기
+subtitle: 환기 횟수와 이산화탄소 농도 측정 요약
+author: 예시 교육청 시설연구팀
+organization: 예시 교육청(가상 기관)
+date: 2026-12-10
+short_title: 학교 건물 겨울철 실내 공기
+abstract: "초등학교 교실 18곳에서 2025년 겨울 8주 동안 이산화탄소 농도를 측정했다. 쉬는 시간마다 창문을 연 교실은 수업 중 평균 1,050ppm을 유지했고, 창문을 열지 않은 교실은 2,300ppm까지 올랐다."
+keywords: [실내 공기, 이산화탄소, 교실 환기, 학교 시설]
+notice: 예시 연구 요약. 기관, 교실, 측정값은 모두 가정이다.
+tonality: Journal
+---
+
+# 측정 배경
+
+겨울철 교실은 난방 효율 때문에 창문을 닫아 두는 시간이 길다. 이 글은 환기 습관에 따라 수업 중
+이산화탄소 농도가 얼마나 달라지는지를 정리한다.
+
+## 측정 교실
+
+표 1. 측정 교실 구성
+
+| 구분 | 교실 수 (곳) | 평균 면적 (m²) |
+|---|---:|---:|
+| 1990년대 준공 | 10 | 66 |
+| 2000년대 준공 | 8 | 68 |
+```
+
+The h1 prints as `1 측정 배경`; the table has three columns and stays inside the left column.
+
+## Before delivery
+
+- The abstract states the finding with its numbers; the body does not open by repeating it.
+- Cross-references match the printed section numbers.
+- No table wider than three columns unless it must be; each wide table becomes a full-width band.
+- The qa run passes; with `--layout`, check that no band leaves a column nearly empty above it.