03_Areas

Purpose

Ongoing responsibilities and standards that require continuous maintenance. Areas have no end date.

What Belongs Here

Engineering standards and best practices
Team philosophies and working principles
Infrastructure and tooling documentation
Design systems and component libraries
User research insights
Recurring responsibilities

What Does NOT Belong Here

Time-bound projects (use 02_Projects/)
General reference material (use 04_Knowledge/)
One-off documentation (use project-specific Docs/)

Area Structure

Each area gets its own folder:

Area-Name/
├── README.md            # Optional: area-specific guidance
├── Standard-Name.md     # Individual standard/philosophy
└── ...

Capture Guidelines

Capture ‘Working Philosophies’ and ‘Standards’ here to ensure long-term team alignment.

Look for:

Recurring decisions that should become standards
Team beliefs expressed in meetings
Patterns that work and should be codified
Infrastructure that needs ongoing maintenance

For AI Agents

When processing transcripts, extract:

Team philosophies (“we always…”, “our approach is…“)
Working principles and mental models
Standards that emerge from repeated decisions
Infrastructure updates and maintenance notes

Current Areas

Knowledge-Architecture - Standards for AI-native documentation