Project Architecture Cards
Curate the patterns that best express a project's architectural identity
Open Documentation → Documentation cards to assign a small set of Architecture Cards to the project itself.
The project page is intentionally selective: choose the two or three cards that best explain the architecture's dominant patterns, constraints, or review posture. Element-, Relationship-, and Workflow-level assignments can provide more specific context elsewhere.
Assign Cards
Browse by series, inspect a card's intent and tradeoffs, and assign it only when project evidence supports the pattern. Remove a card when the design or evidence changes.
Archie and background analysis can suggest card assignments or removals. Those suggestions enter Decisions and should be reviewed before they change the project's card set.
Use Cards Well
- Treat a card as shared vocabulary, not proof that an implementation is correct.
- Record project-specific consequences in an Architecture Document or Handbook decision.
- Prefer a few meaningful cards over a long uncurated list.
- Revisit assignments after major version changes.