Branches
Give every situation its context.
Organize knowledge by client, project area or decision stream. Branches keep related records together inside one project.
01
A partition for a real piece of work.
Create a branch for a client or initiative and file related knowledge there. A branch is an organizational partition; it is not a substitute for project permissions.
Client context
Group the decisions and commitments for one account.
Project work
Keep research, delivery and operations organized.
Shared knowledge
Maintain common records in the appropriate shared scope.
02
Make the read scope explicit.
Use an explicit branch when the question concerns one situation. Inspect the scope reported by recall; unscoped reads can span branches within the authorized workspace.
- Name branches after recognizable work
- Review the selected project before writing
- Use project access controls for authorization
- Keep source and revision details with decisions
Keep exploring
See what context makes possible.