# Information architecture

<!--
The taxonomy file. Top-level concepts, how they relate, how they're
named. Mocks and architecture both look up here.
-->

## Top-level concepts

<!--
The nouns of the app. One block each.
-->

### <Concept name>

- **What it is**: <one-line definition>
- **Identifying field(s)**: <what makes one of these unique>
- **Key attributes**: <list>
- **Relationships**: <to other concepts — "has many X", "belongs to Y", "describes Z">
- **Lifecycle states**: <if it has lifecycle — draft / active / archived / etc.>

## Relationships

<!--
A small relationship diagram in plain text or list form. The shape of
the data, before any database is chosen.
-->

- <Concept A> 1—N <Concept B>
- <Concept B> N—N <Concept C> via <Concept Join>

## Vocabulary rules

<!--
Words used in two senses on the same screen will hurt. Names every
concept with one canonical word and lists synonyms to avoid.
-->

| Use | Don't use | Reason |
|---|---|---|
| <word> | <synonym> | <why we picked one> |

## Navigation top-level

<!--
The skeleton of how a user moves through the app. Not screens — the
conceptual map.
-->

- <section> → <subsection> → <subsection>