HAAM Documentation
The public operating record for how HAAM designs and builds durable digital systems.
HAAM documentation records the principles, standards, and decisions behind our work. It exists to make quality repeatable, criticism useful, and institutional knowledge durable.
A documented standard can outlive the person who first established it.
The library
| Area | What it governs | Status |
|---|---|---|
| Foundations | Purpose, judgment, and the hierarchy of decisions | Foundation |
| Design system | Tokens, components, patterns, and governance | Foundation |
| Accessibility | Inclusive interaction and conformance | Foundation |
| Performance | Speed, resilience, and computational restraint | Foundation |
| Content | Voice, structure, evidence, and editorial quality | Foundation |
How to use these documents
Read the foundations first when beginning a new project. Use the specialist sections during design, implementation, and review. When a project makes a decision that should become repeatable, record it here rather than leaving it in a meeting, message, or individual memory.
These pages are living standards. Their language may evolve, but changes should preserve the underlying aim: digital work that remains clear, accessible, fast, and trustworthy over time.
Documentation principles
- State the reason. A rule without a reason becomes ritual.
- Prefer durable guidance. Document principles before documenting temporary interfaces.
- Show evidence. Standards should be supported by examples, measurements, or observed consequences.
- Name exceptions. A useful system explains when judgment should override the default.
- Keep a public record. Important decisions should remain discoverable after a project ends.