Cn Ib Memo Builder

CN IB Memo Builder

Produce a memo that lets a senior banker understand the decision, evidence, risk, and next action quickly.

Principles

1. Start with the decision or conclusion, not a chronology of work performed.
2. Distinguish confirmed fact, source statement, analysis, assumption, and open question.
3. Support material facts with stable source identifiers and precise locators.
4. Keep unresolved issues visible with owner, deadline, dependency, and consequence.
5. Preserve the user's template, defined terms, and requested sections.
6. Never manufacture a conclusion when the evidence is incomplete.

Workflow

1. Define the memo's job

Read references/memo-types.md. Confirm:

• reader and decision required;
• memo type and required length;
• reporting cut-off and transaction stage;
• approved sources and confidentiality level;
• required template, headings, and sign-offs.

If no template is supplied, start from assets/memo-template.md and remove irrelevant sections rather than filling them with generic prose.

2. Build an evidence ledger

Before drafting, assign each material source a stable ID such as [S1]. Record:

textCopy code
source_id, title, date, file_or_url, page_or_cell, owner, status

Extract facts with original wording, period, unit, scope, and caveat. Use cn-ib-source-verifier for calculation lineage or cn-ib-cross-document-check when sources disagree.

3. Create the issue structure

For each material issue, state:

• Conclusion: what the evidence currently supports;
• Facts: source-backed observations only;
• Analysis: why the facts matter to the transaction;
• Gap or risk: what remains uncertain and the consequence;
• Action: next step, owner, deadline, and closure evidence.

Do not hide a qualification in a footnote when it changes the conclusion.

4. Draft conclusion-first

Read references/drafting-style.md. Write the executive summary after the issue analysis, then move it to the front. Use tables for decisions, open items, and comparisons; use prose for reasoning that needs context.

Keep source tags close to supported statements:

textCopy code
公司截至2026年6月30日的在手订单为人民币10亿元。[S2]

Label management representations, estimates, and adviser analyses explicitly.

5. Validate the draft

Read references/source-and-review.md, then scan a Markdown draft:

bashCopy code
python3 scripts/check_memo_markdown.py memo.md --output memo-issues.csv

The script detects unresolved placeholders, missing core headings, empty sections, uncited quantitative claims, unsupported superlatives, duplicate punctuation, and broken source tags. Adjust required headings with repeated --required-heading options when the user's template differs.

6. Reviewer-ready close

Verify:

• the executive summary agrees with the detailed sections;
• dates, units, names, and transaction terms are consistent;
• every material conclusion states its evidence and limitations;
• every open item has an owner and next step;
• source definitions resolve all citations;
• the final Word/PDF rendering has been visually inspected if delivered in that format.

When revising an existing Word memo, preserve the original and use native Word tracked changes by default. Keep edits granular, retain existing revisions and comments unless instructed otherwise, and do not simulate redlines with color or strikethrough. Use a transparent revision author such as Codex when none is specified. Verify the revision markup and render all changed pages; provide a clean accepted copy only when explicitly requested.

Output contract

Deliver:

1. memo with conclusion-first executive summary;
2. issue-by-issue fact, analysis, risk, and action;
3. decision and open-item table;
4. source register with exact locators;
5. explicit assumptions, limitations, and unresolved disagreements.

Do not turn a management statement or professional inference into an unqualified fact.