Give every contributor the same project context.

Projects move faster when context survives meetings, contributors and agents.

The problem

Goals, constraints and glossary terms get reassembled by each new person, and again by each new agent.

What goes in the repository

Goals
Scope
Constraints
Decisions
Glossary
Architecture
Stakeholders
Progress context

projects/
└── atlas/
    ├── index.md
    ├── brief.md
    ├── decisions/
    ├── architecture/
    └── glossary.md

Why an open repository helps

One maintained brief is a better start than a pile of meeting notes that only one person attended.

How Okide helps

Okide keeps the brief, decisions and glossary together so a new contributor opens the project instead of reconstructing it.

Humans and agents, same files

People and agents can start from the same maintained brief instead of assembling project context independently.

OPEN BY DEFAULT

Keep the repository. Change the tools around it.

The meeting ends. The project context should still be the same for the next person. Okide helps you work with the repository without turning it into an Okide-only format.

Learn about Open Knowledge Format → Download Okide — free

Related use cases

TEAMS

Decision repository

Preserve what was decided and why.

decisions/2026/

Explore →

ROLES

Engineering knowledge

Preserve architecture, decisions and technical context.

engineering/architecture/

Explore →

AGENTS

Agent handoffs

Let the next agent understand what the last one learned.

context/handoff.md

Explore →