Handbook and documents

The handbook explains the company's purpose, policies, processes, and durable knowledge. Its documents give people and agents context that does not belong in live business records or executable tools.

Keep context close to the work

Put a policy beside the tool it constrains. Put a playbook beside the loop that follows it. Link a decision to the change it caused. This keeps context discoverable and gives an agent a useful boundary instead of a giant undifferentiated prompt.

Documents are the primitive

A document is an independent piece of source-owned content. The handbook is a curated collection and navigation over documents, not a second content type. A folder can provide the default tree while an explicit navigation file controls order when needed.

Source path, ownership, audience, and version are more important than a proprietary editor. Semantic relationships such as related, supersedes, or applies to stay separate from navigation.

Knowledge is not authority

A document can explain a decision; it cannot grant permission to make one. Authorization belongs to the actor, tool, and policy that govern the action. Agents should cite the context they used and stop when the context is missing or contradictory.