## Reference images

Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language.

- Component: https://kage-design-assets.t3.tigrisfiles.io/components/cognitions-swe-2/e9966f12-655e-494e-9580-e5330b0ddc92-1789365708-9.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/cognitions-swe-2/e9966f12-655e-494e-9580-e5330b0ddc92-1789365639098-full.webp
- Component on Kage: https://kage.design/component/cognitions-swe-2-footer

## Before you start
Ask what the user's product, audience, and brand are, then apply the principles below to create an original references and appendix ending.

Build the closing section of a technical article with a references list and one or more appendices. Keep it scholarly and navigable while retaining the same reading-column rhythm as the body.

### Design language
- Layout: references heading and numbered list first; appendices follow with clear headings, paragraphs, and optional display equations. Keep the column consistent with the article.
- Typography: references 11–13px with 1.45 line-height, appendix headings 22–28px, body 14–16px, equations 16–20px.
- Spacing: 28–40px before References, 8–12px between citations, and 32–48px before each appendix.
- Colour: background `#f8f8f6`, text `#202020`, muted metadata `#777777`, links `#3517e8`, hairlines `#e4e4df`.
- Borders and radius: avoid cards; use only subtle section rules where needed; square corners.
- Interaction: citation links should jump to sources or anchors; appendix headings can be deep-linkable; maintain visible focus states.

### Never
- Never reuse logos, product names, copy, illustrations, or imagery from the reference.
- Never fabricate citations or present placeholder references as final content.
- Never let the references become an unrelated footer navigation.