# 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.