# Project Identity — [Your Project Name]

## What This Project Is

*One paragraph: what the project does, who it's for, what technology
stack it uses.*

## Core Principles

*3-5 principles that guide design decisions. These help cabinet members
calibrate their findings — a finding that violates a principle is more
significant than one that doesn't.*

## User Context

*Who uses this system. Reference ~/.claude/CLAUDE.md for user identity
that carries across all projects. Add project-specific user context here
(e.g., "primary user is the sole developer" or "used by a 3-person team").*

## Design Philosophy

*Optional — fill this in if your project has UI and you've adopted
information-design or ui-experimentalist cabinet members. These
principles govern how the UI should look and feel — operationalized
decision procedures, not generic advice.*

*Include:*
- *Design principles specific to this project (e.g., "information
  density over whitespace" for data-heavy tools, "minimal chrome" for
  writing tools)*
- *Design vocabulary — named patterns the team uses in design arguments
  (e.g., Tufte's data-ink ratio, Shneiderman's overview-first mantra)*
- *Design exemplars — reference tools or works that inform design
  decisions (e.g., "Things 3 for spatial clarity, Linear for density")*
- *Innovation license — when and how the team can deviate from
  established patterns*

## Principle Catalog

*Optional — fill this in if your project has adopted user-advocate.
Maps where the project's principles live so the user-advocate can
trace any design decision back to its foundation.*

*Include:*
- *Core principles and their source files*
- *Architectural principles (scattered across docs, memory, commits)*
- *Key design decisions and their rationale*
- *Teaching modes the user-advocate should use (contextual, explanatory,
  evolutionary, socratic)*

## Strategic Direction

*Optional — fill this in if your project has adopted goal-alignment
or vision cabinet members.*

*Include:*
- *Current horizons — what the project is, what it's becoming, what it
  could be*
- *Generalizability questions — what's project-specific vs. portable*
- *Technology horizon scanning targets — what domains to actively
  research*
- *Operational details for goal-alignment — how to query current
  priorities, feedback temporal urgency model*
