Company wiki

Knowledge base with built-in rot prevention.

## How to use

- Each article is a section in the **Articles** doc.
- Every article has an entry in the **Index** table with: title, owner, last-reviewed date, audience.
- **Outdated queue** auto-pulls articles past their review interval. Owner is on the hook to refresh.

## Suggested initial articles

### Onboarding

How a new team member spins up. The map: tools, accounts, first-week milestones.

### How we work

Cadences (standup, weekly all-hands, monthly retro). Decision-making model. How we disagree.

### Tooling

The stack. Why we picked each, what trade-offs we accept.

### Brand + voice

How we talk about ourselves. What's on-brand vs off.

### Customers

Who we serve, the segments, the hot personas.

## Cadence

Review every article quarterly. Anything past 6 months without a review goes to the **Outdated queue** for forced refresh.

Fork to next cycle

When you're done, fork the workspace for the next cycle. The new workspace will be seeded with your structure, your customizations, and this cycle's retro as your agent's first Status entry — so it picks up context-aware from where this one left off. Same template, next cycle, no manual setup.