Work public
audit-grade-rag
A compliance-grade RAG console. Bone-paper aesthetic, branch-protected mainline, bracketed citation pills auditors can read out loud.
What it is
A RAG console designed for the artifact a regulated workflow actually needs: an answer with bracketed citations to source chunks, an audit column that records every step the system took, and a UI that looks at home next to a binder of standards documents.
The problem it solves
Production RAG is usually evaluated as a chat experience. Auditors evaluate it as a paper trail. The two have different requirements.
A compliance-grade RAG has to expose, per answer: which retrieval ran, which chunks scored highest, what the rerank changed, what the model received as context, and what guardrails fired. None of that information lives in a normal chat UI.
This is an opinionated take at how that UI should look.
Design decisions worth defending
- Bone-paper palette + serif display. The console reads like a printed manifest. Mono only where data is machine-grain. Type stack is Hoefler Text / Garamond / Caslon for display, Georgia for body, JetBrains Mono for data fields.
- Inverted-black audit column with drop-cap. The audit log gets its own visual register so an auditor never confuses it with the answer.
- Bracketed citation pills. Every claim ends with
[c-12]. Clicking opens the source chunk in a side panel. The bracket convention is borrowed from academic writing and survives screen reading.
Engineering discipline
main is branch-protected with required check-full CI and enforce_admins: true. No bypass. A one-line CSS fix takes the same PR path as a feature.
Pre-commit runs biome, eslint, knip, typecheck, unit tests via lefthook. If any of those fail locally, the commit does not happen.
Stack
Bun + Hono backend. Vanilla TS frontend rendered server-side. CSS architecture split across styles-foundation.ts, styles-shell.ts, styles-components.ts, styles-evidence.ts for clean cross-module review.