schema_version: 1 doc_id: fin_lookbooks_readme doc_kind: index title: FIN Lookbooks — Index slug: fin-lookbooks-readme source_attribution:
- author:claude_orchestrator lifecycle_status: active created_at: 2026-05-18T00:00:00Z updated_at: 2026-05-18T00:00:00Z maintained_by: rob visibility: company data_plane: universal_intelligence tags: [lookbooks, explainers, marketing, non_technical]
FIN Lookbooks
Polished, interactive explainer artifacts intended for non-technical audiences — prospects, investors, anchor tenants, executives, journalists, federal partners.
Each lookbook is a self-contained HTML file that opens in any browser. No build step.
Inventory
| Lookbook | Audience | Topic | File |
|---|---|---|---|
| FIN Intranet System — A Living Knowledge Layer | Non-technical | What FIN Central + tenant intranet is, how it works, why it matters, the novelty of being an agent-native enterprise OS. Interactive markdown viewer with human-view ↔ agent-view toggle; animated 3-rung taproot diagram; fusion-lens demo. | fin-intranet-system-lookbook-2026-05-18.html |
How to share
- Local preview:
open docs/lookbooks/fin-intranet-system-lookbook-2026-05-18.html - Hosted preview: add to a GitHub Pages site at
lookbooks.fintail.net/<file>(gated) - PDF export: print → save as PDF (page break hints in
@media printstyles where present)
Design conventions
All FIN lookbooks share:
- Font pairing: Fraunces (display, variable serif) + DM Sans (body) + JetBrains Mono (code)
- Color palette: deep sage / clay / brass on warm cream paper; ink near-black with warmth
- Animation: scroll-triggered reveals, restrained, purposeful
- Inline-everything: no external assets except Google Fonts CSS
Audience contract
Lookbooks are written for an audience that knows enterprise software but does NOT know FIN’s architecture. They:
- Lead with the problem framing the audience already feels
- Show, never just describe (interactive demos beat prose)
- Cite proof (real metrics, real document examples)
- End with a clear point of view (“the novelty”)
They are NOT engineering specs. They are NOT operational handbooks. For those, see:
docs/architecture/— projection architecture familydocs/engineering/— system specsdocs/processes/— execution programs
Adding a new lookbook
- Create a new HTML file in this folder named
<topic-slug>-<YYYY-MM-DD>.html - Follow the design conventions in the existing lookbook
- Add an entry to the table above
- Open PR with screenshots in the description