Home / Use cases
What belongs in a knowledge repository?
If knowledge matters enough to keep, share or give to an agent, it can live in a repository.
Okide keeps that knowledge in open Markdown files, adds structure with Open Knowledge Format and lets humans and agents work from the same versioned source.
PERSONAL
Personal
Knowledge that belongs to you, not to an app.
PERSONAL
Personal knowledge
Keep durable knowledge outside any single app.
knowledge/index.md
Explore →
PERSONAL
Research
Keep sources, findings and conclusions connected.
research/sources/
Explore →
PERSONAL
Professional knowledge
Turn years of judgment into reusable context.
craft/patterns/
Explore →
PERSONAL
Consulting
Structure client knowledge while keeping your method reusable.
clients/acme/index.md
Explore →
PERSONAL
Learning
Turn notes into connected knowledge that compounds.
learning/concepts/
Explore →
PERSONAL
Writing
Keep sources, reasoning and drafts in one history.
writing/drafts/
Explore →
ROLES
Roles
The context that makes you good at the job.
ROLES
Engineering knowledge
Preserve architecture, decisions and technical context.
engineering/architecture/
Explore →
ROLES
Product knowledge
Keep the reasoning behind the roadmap.
product/decisions/
Explore →
ROLES
Design knowledge
Preserve principles, research and design decisions.
design/principles/
Explore →
ROLES
Sales knowledge
Turn market conversations into reusable insight.
sales/objections/
Explore →
ROLES
Operations knowledge
Document how the work actually runs.
operations/processes/
Explore →
ROLES
Domain expertise
Capture the knowledge that makes an expert expert.
domain/concepts/
Explore →
TEAMS
Teams
What a group needs to stop re-explaining.
TEAMS
Team handbook
Write down the defaults so the team stops re-explaining them.
team/handbook.md
Explore →
TEAMS
Decision repository
Preserve what was decided and why.
decisions/2026/
Explore →
TEAMS
Project knowledge
Give every contributor the same context.
projects/atlas/index.md
Explore →
TEAMS
Runbooks
Keep operational knowledge readable and current.
runbooks/api-outage.md
Explore →
TEAMS
Onboarding
Give new people and agents a path through the context.
onboarding/week-one.md
Explore →
TEAMS
Shared research
Make findings accumulate across the team.
research/findings/
Explore →
COMPANIES
Companies
The knowledge the organization depends on.
COMPANIES
Company knowledge
Build institutional memory the organization can keep.
company/principles.md
Explore →
COMPANIES
Product portfolio
Structure knowledge across multiple products.
products/index.md
Explore →
COMPANIES
Customer knowledge
Turn customer conversations into reusable context.
customers/segments/
Explore →
COMPANIES
Internal documentation
Keep documentation in portable files.
docs/index.md
Explore →
COMPANIES
Policies & procedures
Keep important rules versioned and reviewable.
policies/security.md
Explore →
COMPANIES
AI-ready company context
Give different agents one maintained company context layer.
context/index.md
Explore →
AGENTS
Agents
The same repository, read by your tools.
AGENTS
Coding agents
Give agents the context the code cannot explain.
engineering/conventions.md
Explore →
AGENTS
Research agents
Give research agents memory you can inspect.
research/findings/
Explore →
AGENTS
Internal assistants
Ground answers in knowledge your team can fix.
company/faq.md
Explore →
AGENTS
Agent handoffs
Let the next agent understand what the last one learned.
context/handoff.md
Explore →
AGENTS
Multi-agent systems
Give many agents one shared knowledge layer.
knowledge/index.md
Explore →
AGENTS
Agent-generated knowledge
Make generated knowledge reviewable, editable and reversible.
knowledge/generated/
Explore →
Start with a repository.
Pick the knowledge you already have. Keep it in files you can read, version and hand to an agent.