# Founder Brief Kernel

Use this reference when founder-facing artifacts need presentation polish while
remaining grounded in repo truth.

## Truth Boundary

1. Repo code, docs, tests, and contracts prove current state.
2. Founder wiki canon shapes north-star language and future-state alignment.
3. Divergence is `current_state_vs_north_star_drift`; do not overstate
   implementation.
4. Private wiki evidence stays local-only unless the user explicitly asks for
   an internal private artifact.

## Narrative

1. Platform thesis first, runtime and trust boundary second, present-state
   honesty later.
2. Expand shortforms on first use unless universally obvious.
3. Keep shared artifacts free of prompt notes, drafting provenance, and repo
   process commentary.
4. Put source-detail inventory in references, not the narrative body.
5. State unimplemented items in a dedicated honesty section.
6. Preserve Hussh / One / Kai / Nav ontology: Hussh is platform and trust
   infrastructure, One is personal agent, Kai is finance specialist, Nav is
   privacy and consent guardian.

## Presentation

1. Prefer a few premium diagrams over many local boxes.
2. If labels are tight, rebalance the geometry before shrinking text too far.
3. Avoid dangling chapter titles and orphan headings.
4. For HTML-sourced PDFs, inspect rendered pages for fit, labels, tables,
   margins, and transitions before calling the artifact shareable.
5. Keep heading treatment consistent unless the user asks for a different
   chapter system.
