AI output looks broken when pasted into Google Docs

You're going to build my company's DOCUMENT STANDARDS BLOCK: a reusable instruction block I'll paste into any AI chat that produces documents destined for Google Docs.

Interview me first, one question at a time. Wherever I don't know an answer, propose a sensible default and move on:
1. What does the company do, and which 3 to 5 document types do we produce most (proposals, reports, SOWs, memos)?
2. I'll paste whatever exists: brand guidelines, a well-formatted example document, a style guide. If nothing exists, ask what fonts and colours our website uses and derive from that.
3. How do our documents open, straight in or summary first? What sections do readers expect, in what order?
4. Voice: formal or plain English? First person singular or plural? Words we'd never use?
5. Conventions: date format, currency, units, numbers as words or digits?
6. What annoys us most about AI-produced documents today?

Then output my DOCUMENT STANDARDS BLOCK as one copy-paste block containing: (a) two lines of company context, (b) typography mapped to Google Docs named styles, one # title maps to Title, ## to Heading 1, ### to Heading 2, (c) structure rules per document type, (d) voice rules including banned words, (e) table and number conventions, (f) a closing self-audit instruction that makes any AI check compliance before output and append "Standards check: pass" or list violations.

Keep the block under 400 words so it fits any project-instructions field. After you output it, tell me the three highest-risk ways an AI will still break our formatting and how the block prevents each.

CONTEXT: Fenwick & Cole is a boutique management consultancy advising mid-market retail and consumer brands on operations and growth. Documents we produce: client proposals, engagement reports, statements of work, board memos.

TYPOGRAPHY (these map to our Google Docs named styles): one # is our Title (Fraunces, 28pt, navy #12233A). ## is Heading 1 (Fraunces, 18pt, navy). ### is Heading 2 (Inter, 13pt, semibold). Body is Inter, 11pt, 1.4 line spacing, charcoal #2B2B2B. Never skip a heading level; never fake a heading with bold text.

STRUCTURE: every client document opens with a one-paragraph summary under a heading named "In short". Sections then run in this order: Context, Findings, Recommendations, Next steps, Commercials. Recommendations are always a numbered list. Anything longer than one page of detail goes in an appendix.

VOICE: first person plural, plain English, short sentences, no hedging. Banned words: leverage, synergy, robust, seamless, delve, landscape. Dates as 4 July 2026. Currency as £4,000. Numbers under ten in words, ten and above in digits.

TABLES: used only for pricing and option comparisons; maximum four columns; header row bold; no long prose in cells, use a list instead.

OUTPUT RULES for every document you produce for me:
1. Standard Markdown only, strictly mapped: one # for the Title, ## for sections, ### for subsections.
2. Follow the structure above without being asked: summary first, sections in house order, numbered recommendations.
3. Match the voice rules exactly; if a sentence wouldn't survive our style, rewrite it before showing me.
4. Blank line between paragraphs and around lists and tables. Bold only for defined key terms. No emojis, no horizontal rules, no footnotes, no filler commentary inside the document.
5. Before you output, silently audit against this whole block and fix violations. Then append one line after the document: "Standards check: pass", or list what you couldn't comply with and why.