The problem
Rituals, ownership and working agreements get repeated in meetings because they were never written where the team already works.
What goes in the repository
- Rituals
- Ownership
- Communication
- Principles
- Working agreements
- Responsibilities
- Team defaults
team/ ├── index.md ├── handbook.md ├── principles.md ├── rituals/ └── ownership/
Why an open repository helps
Defaults that live in a repository can be reviewed when they change, instead of being re-explained from memory.
How Okide helps
Okide keeps the handbook close to the rest of the team’s knowledge, so a default can be edited without starting a new wiki.
Humans and agents, same files
Team assistants and new agents can begin with the same documented defaults as a new teammate.
OPEN BY DEFAULT
Keep the repository. Change the tools around it.
A default is only a default if the next person can find it. Okide helps you work with the repository without turning it into an Okide-only format.
Related use cases
TEAMS
Onboarding
Give new people and agents a path through the context.
onboarding/week-one.md
Explore →
COMPANIES
Company knowledge
Build institutional memory the organization can keep.
company/principles.md
Explore →
COMPANIES
Internal documentation
Keep documentation in portable files.
docs/index.md
Explore →