CARLO HENNSA — SINGLE-FILE TECHNICAL DOCUMENT STYLE REFERENCE Showcase edition: 1.3 | Design guide: 1.1 | Published: 15 October 2026 Canonical URL: https://hennsa.com/style/AI_STYLE_REFERENCE.txt READ THIS FIRST — NO OTHER URL REQUIRED This one text/plain file contains everything needed to reproduce the Carlo Hennsa Technical Document Style: design rules, COMPLETE original base CSS, COMPLETE optional showcase CSS, a semantic HTML starter structure, COMPLETE navigation/print JavaScript, document-type guidance and the full Markdown style guide. If you only have access to this file, DO NOT require any other URL to generate a styled document. The linked HTML examples are optional visual references, not a prerequisite. You may embed the CSS and JS verbatim in a self-contained HTML file. For a matching PDF, render/print the HTML using A4 and background graphics. AUTHOR AND ATTRIBUTION - Default document author: Carlo Hennsa. - Formal/academic alternative only when requested: M.C. Hennsa. - Individually authored assessments: use I/my, never we/our unless directed. - This is independently authored styling inspired by a blue/gold colour family; it is NOT official institutional branding or endorsement. - Only use the user's real project facts; the examples are fictional illustrations. - Don't reuse client-specific names, Modikwa, mining assumptions or other sample claims as facts. THE NON-NEGOTIABLE VISUAL SIGNATURE - Dark navy #082A4D cover with white title, pale blue second line, thin blue/gold rule. - Navy #113A66 headings, blue #145E97 links, bright blue #1C79B7 accents. - White report surface; very light blue #E6F1F8 accents; gold #C5A355 sparingly. - Clear numbered sections, restrained evidence tables/callouts, sticky left navigation on desktop, collapsible navigation on mobile, and a Print / Save PDF button. - Segoe UI / Arial system typography, not externally hosted fonts or dependencies. - A4 print stylesheet with page counters and careful page breaks. ONE-FILE IMPLEMENTATION RECIPE 1. Write accurate, original content; choose a document type (assessment, system design, test plan, architecture decision record, or another type) that fits the request. 2. Copy the STARTER HTML from below, replacing all [placeholders] and adjusting section headings, navigation links and document metadata for the actual document. 3. Copy the COMPLETE BASE CSS from this file into the starter's
CARLO HENNSA Technical document / [Document type]
[Document type] / [Project identifier]

[Technical document]
[Supporting title]

[Two to three sentences describing purpose, audience and context.]

Prepared byCarlo Hennsa
Version[1.0]
Date[YYYY-MM-DD]
Status[Draft / For review]
01
OVERVIEW

Executive summary

Purpose and decision required

[Document-specific summary, evidence and conclusion. Do not invent facts.]

Decision needed
[The specific approval, clarification or action requested.]
02
SOURCE BASIS

Evidence and scope

Materials used and limitations

Included

[Relevant material and boundaries.]

Not verified

[Known gaps or assumptions.]

03
ASSESSMENT

Findings

Traceable items and decisions

IDItemEvidence / impactAction
F-01[Finding] [Grounded observation and consequence][Required decision]

Replace sample labels and placeholder rows with verified project content.

04
NEXT STEPS

Actions and decisions

Ownership and acceptance

  1. [Action, owner and due date or dependency]
  2. [Decision, approver and supporting evidence required]
Recommended position
[Concise conclusion based on evidence.]
======== END HTML STARTER ======== ======== BEGIN COMPLETE JAVASCRIPT: site.js ======== (function(){ 'use strict'; const sidebar=document.querySelector('.side'); const menu=document.querySelector('.hamburger'); if(menu&&sidebar){ const close=()=>{sidebar.classList.remove('open');menu.setAttribute('aria-expanded','false')}; menu.addEventListener('click',()=>{const open=sidebar.classList.toggle('open');menu.setAttribute('aria-expanded',String(open))}); sidebar.querySelectorAll('a').forEach(a=>a.addEventListener('click',close)); document.addEventListener('keydown',e=>{if(e.key==='Escape')close()}); } const links=[...document.querySelectorAll('.nav-item[href^="#"]')].filter(a=>a.hash); const sections=links.map(a=>document.getElementById(a.hash.slice(1))).filter(Boolean); if('IntersectionObserver' in window&§ions.length){ const observer=new IntersectionObserver(entries=>{ const shown=entries.filter(x=>x.isIntersecting).sort((a,b)=>a.boundingClientRect.top-b.boundingClientRect.top); if(shown.length){const id=shown[0].target.id;links.forEach(a=>a.classList.toggle('active',a.hash==='#'+id))} },{rootMargin:'-15% 0px -67% 0px',threshold:0}); sections.forEach(s=>observer.observe(s)); } document.querySelectorAll('[data-print]').forEach(b=>b.addEventListener('click',()=>window.print())); })(); ======== END COMPLETE JAVASCRIPT ======== ======== BEGIN COMPLETE OPTIONAL SHOWCASE CSS: showcase.css ======== /* Carlo Hennsa document showcase · extension to Carlo_Document_Theme.css Static, self-hostable; using a blue-and-gold colour family, not official branding. */ :root{--canvas:#edf2f6;--sample-accent:#145e97} body{background:var(--canvas)} .brandmark{font-size:12px;letter-spacing:.03em} .header-inner a.btn{text-decoration:none} .nav-item{transition:background .15s,color .15s} .hero-meta-note{display:flex;align-items:center;gap:9px;font-size:10px;letter-spacing:.12em;text-transform:uppercase;color:#a9cee6;font-weight:800} .hero-meta-note:before{content:"";display:block;width:24px;height:2px;background:var(--gold)} .cover .cover-meta .sample-flag{color:#f0d99c} .feature-chip{display:inline-block;font-size:10px;font-weight:750;letter-spacing:.045em;background:#eaf3f9;border:1px solid #d1e3ee;color:var(--navy);padding:4px 9px;border-radius:3px;margin:0 4px 6px 0} .mini-cards{display:grid;grid-template-columns:repeat(3,minmax(0,1fr));gap:13px;margin:19px 0} .mini-card{min-width:0;border:1px solid var(--line);background:#fff;padding:19px 20px;border-top:4px solid var(--blue)} .mini-card:nth-child(2){border-top-color:var(--bright)}.mini-card:nth-child(3){border-top-color:var(--gold)} .mini-card .eyebrow{color:var(--blue);text-transform:uppercase;font-size:10px;font-weight:800;letter-spacing:.12em} .mini-card h3{margin:12px 0 8px;font-size:18px}.mini-card p{font-size:12px;color:var(--muted);margin:0 0 14px}.mini-card a{text-decoration:none;font-size:12px;font-weight:800} .mini-card a:hover{text-decoration:underline} .palette{display:grid;grid-template-columns:repeat(6,1fr);gap:9px;margin:22px 0} .swatch{border:1px solid var(--line);background:#fff;overflow:hidden}.swatch-color{height:58px}.swatch .meta{padding:9px;font-size:10px;font-family:Consolas,monospace;color:var(--muted)}.swatch .meta strong{display:block;font-family:'Segoe UI',Arial,sans-serif;color:var(--navy2);font-size:10px} .sample-kicker{font-size:10px;text-transform:uppercase;font-weight:800;letter-spacing:.15em;color:var(--blue)} .link-row{display:flex;flex-wrap:wrap;gap:9px;margin:21px 0 0}.link-row a{text-decoration:none} .link-row a.btn{display:inline-flex;align-items:center;gap:7px} .hero-sub{color:#cfe2f0!important} .block-title{font-size:20px;margin:21px 0 12px;color:var(--navy2)} .flow-diagram{display:grid;grid-template-columns:repeat(4,minmax(0,1fr));align-items:center;gap:16px;margin:18px 0} .flow-node{background:#f6fafd;border:1px solid #bfd5e5;min-height:125px;padding:16px 12px;position:relative} .flow-node b{font-size:13px;color:var(--navy2)}.flow-node small{display:block;color:var(--muted);font-size:11px;margin-top:9px;line-height:1.5} .flow-node:not(:last-child):after{content:'→';position:absolute;right:-17px;top:42%;font-size:20px;color:var(--blue);z-index:1} .flow-node.emphasis{background:var(--navy);border-color:var(--navy);color:white}.flow-node.emphasis b{color:white}.flow-node.emphasis small{color:#d6e7f2} .kv-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:12px}.kv{padding:16px;border:1px solid var(--line);background:#f9fbfd}.kv small{display:block;color:var(--blue);font-size:9px;letter-spacing:.12em;font-weight:800;text-transform:uppercase}.kv strong{display:block;margin-top:5px;font-size:14px;color:var(--navy2)}.kv p{font-size:11px;margin:5px 0 0} .status-tags{display:flex;flex-wrap:wrap;gap:8px;margin:12px 0}.status-tag{font-size:10px;font-weight:800;letter-spacing:.04em;padding:5px 10px;border-radius:3px;border:1px solid #d5e5ee;background:#eef6fb;color:var(--navy)}.status-tag.gold{color:#795c22;border-color:#ebdbb2;background:#f9f3e5}.status-tag.red{color:var(--red);background:var(--red-bg);border-color:#e8c7ce} .code-panel{background:#102e49;color:#e0edf6;padding:18px 21px;margin:18px 0;overflow-x:auto;border-left:4px solid var(--gold)}.code-panel pre{margin:0;font-family:Consolas,'Courier New',monospace;font-size:11px;line-height:1.75;white-space:pre} .a4-footer-note{font-size:11px;color:var(--muted)} .sample-label{display:inline-block;background:#f9efda;color:#785e28;border:1px solid #dbca9c;padding:5px 8px;font-size:10px;font-weight:800;letter-spacing:.09em;text-transform:uppercase;border-radius:2px} .showcase-head{display:flex;align-items:center;justify-content:space-between;gap:20px;margin-bottom:18px}.showcase-head h3{margin:0;font-size:20px} .doc-section p.lead{font-size:16px;line-height:1.72;max-width:760px} .adr-heading{display:flex;align-items:center;justify-content:space-between;gap:16px;border:1px solid var(--line);padding:16px;margin:13px 0 23px} .adr-heading strong{font-size:18px;color:var(--navy2)}.adr-heading small{font-size:11px;color:var(--muted)} .site-legal{font-size:11px;color:var(--muted);line-height:1.6;margin:0} @media(max-width:1100px){.palette{grid-template-columns:repeat(3,1fr)}.mini-cards{grid-template-columns:1fr}.flow-diagram{grid-template-columns:repeat(2,1fr)}.flow-node:after{display:none}} @media(max-width:760px){.palette{grid-template-columns:repeat(2,1fr)}.flow-diagram,.kv-grid{grid-template-columns:1fr}.header-actions .btn.secondary-action{display:none}.hero-meta-note{font-size:9px}.mini-cards{grid-template-columns:1fr}} @page{size:A4;margin:17mm 16mm 17mm 16mm;@bottom-left{content:'Carlo Hennsa | Illustrative document';font:8px Arial;color:#6e8191}@bottom-right{content:counter(page);font:9px Arial;color:#4a718a}} @media print{ .header,.top-rule,.side,.no-print{display:none!important} .cover{min-height:268mm!important;margin:-17mm -16mm 9mm!important;padding:25mm 21mm 18mm!important;page-break-after:always} .cover h1{font-size:42px!important}.cover-desc{font-size:15px!important}.cover-meta{margin-top:42px!important} .doc-section{padding:11px 0 16px!important} .flow-diagram{grid-template-columns:repeat(4,minmax(0,1fr))}.flow-node{min-height:110px;padding:9px}.flow-node small{font-size:8px}.flow-node b{font-size:10px}.flow-node:after{display:none} .palette{grid-template-columns:repeat(6,1fr)}.mini-cards{grid-template-columns:repeat(3,1fr)} .kv-grid{grid-template-columns:repeat(2,1fr)}.note,.mini-card,.kv,.adr-heading,.code-panel,.flow-node{break-inside:avoid-page} .code-panel pre{white-space:pre-wrap;font-size:8px} .issues-table{min-width:0} .footer{display:none!important} a[href]:after{content:none!important} } /* v1.1: Four example cards and test-plan matrix */ .mini-cards{grid-template-columns:repeat(2,minmax(0,1fr))} .doc-section .issues-table td{overflow-wrap:anywhere} @media(max-width:760px){.mini-cards{grid-template-columns:1fr}} @media print{.mini-cards{grid-template-columns:repeat(2,minmax(0,1fr))}.issues-table td,.issues-table th{overflow-wrap:anywhere}} ======== END COMPLETE SHOWCASE CSS ======== ======== BEGIN FULL STYLE GUIDE: Carlo_Document_Style_Guide.md ======== # Carlo Hennsa | Technical Document Style Version 1.1 · 13 October 2026 ## Purpose Use this as the default visual reference for technical reports, discovery reviews, proposals, feasibility assessments, stakeholder decision documents and architecture handovers across any project, unless a different client-approved brand is required. **Reference implementation:** `examples/technical-review.html`. This is an **independent blue editorial theme**, not an official document and not intended to imply sponsorship or affiliation. Do not add client logos, seals or official letterhead without authorization. ## Brand palette | Design token | Hex | Typical use | |---|---|---| | Navy | `#113A66` | Navigation emphasis, headings, selected states | | Deep navy | `#082A4D` | Title cover and high-contrast table headers | | Blue | `#145E97` | Links, section numbers, overlines | | Bright blue | `#1C79B7` | Highlight accents and navigation state | | Light sky | `#E6F1F8` | Light-blue emphasis panels | | Off-white blue | `#F2F7FA` | Subtle section backgrounds | | White | `#FFFFFF` | Report surface | | Primary text | `#243647` | Main paragraphs | | Muted text | `#647687` | Supporting text and metadata | | Rules and borders | `#DBE5EC` | Tables, separators and controls | | Gold accent | `#C5A355` | Restrained visual punctuation, no broad gold fills | | Risk red | `#9F4451` | High-severity callouts and labels | | Pale risk red | `#FAEFF1` | High-severity label backgrounds | CSS variables, all responsive layout rules and print styles are included in `Carlo_Document_Theme.css`. ## Layout conventions 1. **A substantial dark-navy title cover**, with a large white title, pale-blue emphasis, a discreet oversized chapter number and a narrow gold/blue accent bar. 2. **Sticky narrow top bar** with a neutral document symbol, type label and a Print / Save PDF control. 3. **Persistent left contents navigation** on desktop, collapsible on mobile; every major section is numbered and has an anchor. 4. **White paper-like main surface**, spacious margins, clear sectional breaks and strong editorial typography. Use Segoe UI / Arial for a self-contained report without additional font requirements. 5. **Compact evidence components**: decision/issue tables, two-column comparison panels, question lists, numbered steps and diagrams only when they add information. 6. **Colour is functional**. Use blue for hierarchy, gold sparingly for focus, and muted red for actionable risk. Avoid decorative colour boxes around conclusions. 7. **Independent, direct tone**: clearly distinguish verified facts, document claims, assumptions and professional assessment. For personally authored correspondence, use **I / my**, not we / our. Keep decision ownership explicit. 8. **Author identity**: in formal technical documents, identify the author as **Carlo Hennsa** (default) or **M.C. Hennsa** (formal or academic-style alternative). Never shorten the author credit, cover byline, document control or signature to just “Carlo”. 9. **A4 print-ready** with page counters, repeated table headers where appropriate, consistent typography and sensible page breaks. ## Author naming and voice - **Default name:** Carlo Hennsa. - **Optional formal/academic byline:** M.C. Hennsa. - Apply this consistently to title pages, author metadata, headers/footers, prepared-by fields, approval/signature blocks, and document properties when supported. - When writing a personal technical assessment, use first-person singular where necessary (I, my). Do not use “we” or imply a team or employer authored the document unless explicitly instructed. - The *style name* “Carlo Technical Document Style” is only a shorthand for this design and is not an acceptable replacement for the full author name. ## Recommended content structure - Cover: document title, project, author, date, version, audience and purpose. - Executive position: the conclusion and what decision is required. - Evidence base: which documents, versions and observations support it. - Findings: a numbered and severity-ranked issue/decision register. - Detail: one section per functional theme, each with specific questions or actions. - Delivery or implementation implications: dependencies, constraints, risks and assumptions. - Recommended actions: owners and concrete next decisions. - Document control: version history and prepared-by attribution. No need to force all these sections into short documents. Preserve the hierarchy and style, but match length to substance. ## Reuse in future projects In a new conversation or project, say: > Use my Carlo Technical Document Style, based on the attached `Carlo_Document_Style_Guide.md`, with a navy cover, numbered sections, side navigation, compact issue tables, restrained blue and gold colours, and A4 PDF export. Credit the author as **Carlo Hennsa** (or **M.C. Hennsa** when specifically requested), and use **I / my** for personal assessments. Keep the guide in a central personal document/template repository or attach it to projects that need it. ChatGPT Memory may help recover the preference when available, but the guide and stylesheet are a more dependable, version-controlled reference. ## Production checks - Use fully self-contained HTML if it must render offline, with CSS and any JavaScript embedded or distributed beside the HTML and no externally loaded images/fonts. - Check at desktop and mobile widths; hyperlinks, navigation, and print buttons must work. - Export a matching PDF with A4 pages, backgrounds enabled and page-break rules. Confirm that content is not clipped or split awkwardly. - Check signature and perspective before distribution: author name “Carlo Hennsa” or “M.C. Hennsa”, no solitary “Carlo” as the author, and no accidental plural first-person voice. - Revise title, content, dates, document IDs and section labels for each project; do not reuse project-specific details as generic placeholders. ======== END FULL STYLE GUIDE ======== ======== BEGIN AI IMPLEMENTATION NOTES: ai-style-guide.md ======== # Carlo Hennsa Technical Document Style — AI implementation notes Style guide: 1.1, showcase: 1.3. Last updated: 15 October 2026. ## Single URL for AI systems Read `https://hennsa.com/style/AI_STYLE_REFERENCE.txt` first. It is sufficient by itself: design rules, complete CSS, reusable HTML starter, menu/print script and A4 PDF guidance. Individual files and HTML examples are optional. ## Intended use Create reports, technical assessments, system designs, test plans and decision records in Carlo Hennsa's consistent editorial style. The fictional example contents are **not** authoritative facts or reusable requirements. ## Author / voice - Default author name **Carlo Hennsa**, alternatively **M.C. Hennsa** when explicitly requested. - Independent personal reports: **I / my**, never “we / our” unless the user explicitly represents a team. - Do not imply official affiliation. Theme is inspired by a blue/gold colour family, without official branding. ## Design rules 1. Deep navy `#082A4D` document cover; navy `#113A66` main heading; blue `#145E97` links; bright blue `#1C79B7` highlights; sky `#E6F1F8` surfaces; gold `#C5A355` restrained accents. 2. Semantic, accessible HTML headings and anchors; two-column layout with left sticky section navigation on desktop and a mobile menu. 3. Numbered content sections, spacious white document surface, dense but readable tables, compact evidence callouts. 4. Segoe UI / Arial system fonts. No external fonts, CDNs, JavaScript libraries or image dependencies. 5. A4 print stylesheet with page numbers; export matching PDF from HTML using a browser with backgrounds enabled. Always check generated pages. 6. Clearly distinguish document-backed evidence, assumptions, illustrations and recommendations. Do not reuse fictional example content as if it is verified. 7. Make responsive layout and print both first-class. Do not merely screenshot the HTML for a PDF. ## Source files - Full style guide: `downloads/Carlo_Document_Style_Guide.md` - Primary CSS: `assets/Carlo_Document_Theme.css` - Showcase CSS additions: `assets/showcase.css` - Basic navigation/print script: `assets/site.js` - Machine-readable manifest: `style-manifest.json` ## Examples - `examples/technical-review.html` + `downloads/technical-review.pdf`: evidence and issue assessment - `examples/system-design.html` + `downloads/system-design.pdf`: architecture and interfaces - `examples/decision-record.html` + `downloads/decision-record.pdf`: focused architecture decision - `examples/test-plan.html` + `downloads/test-plan.pdf` + `downloads/test-plan.md`: test strategy, cases and gates ## AI workflow 1. Read this file and the complete Markdown style guide. 2. Read the CSS design tokens and select the most relevant HTML example. 3. Draft the requested content based on the user's actual information, not fictional examples. 4. Build an accessible responsive HTML document using the shared stylesheet; generate PDF if requested. 5. Check names, scope, tables, page breaks, colour contrast and links; clearly label assumptions. ## Retrieval requirements A web-capable model can fetch these static URLs if the public host serves them without authentication or bot challenges. `llms.txt` is a useful convention, **not a guarantee** that every assistant will discover or follow it. For reliable reuse, give the model the full public URL to `llms.txt` and preferably also the URL to the style guide or attach the files when web access is unavailable. ## Content-type compatibility (showcase v1.2) Some AI browsing tools reject `text/css`, `text/markdown`, or files they classify as downloads. In that case, fetch the **exact plain-text copies** using `.txt` paths: - `https://hennsa.com/style/AI_STYLE_REFERENCE.txt` — combined, easiest one-request reference. - `https://hennsa.com/style/assets/Carlo_Document_Theme.css.txt` — same bytes as original CSS. - `https://hennsa.com/style/assets/showcase.css.txt` — same bytes as example CSS. - `https://hennsa.com/style/downloads/Carlo_Document_Style_Guide.md.txt` — same bytes as Markdown guide. - `https://hennsa.com/style/downloads/test-plan.md.txt` — same bytes as Markdown example. `llms.txt` lists the mirrors **first**. The original `.css` and `.md` files remain available for browsers and developers. A web-capable AI must still be able to fetch the public URL and receive a usable response. ======== END AI IMPLEMENTATION NOTES ======== OPTIONAL LINKS (NOT REQUIRED FOR DOCUMENT GENERATION) - Technical assessment: https://hennsa.com/style/examples/technical-review.html - System design: https://hennsa.com/style/examples/system-design.html - Decision record: https://hennsa.com/style/examples/decision-record.html - Integrated test plan: https://hennsa.com/style/examples/test-plan.html - Plain-text index: https://hennsa.com/style/llms.txt END OF SINGLE-FILE STYLE REFERENCE