The problem
Architecture, conventions and the reasons behind them drift into tickets, chats and people. The repository of code remains. The repository of intent often does not.
What goes in the repository
- Architecture
- ADRs
- Conventions
- Dependencies
- System boundaries
- Operational constraints
- Migration context
- Technical lessons
engineering/ ├── index.md ├── architecture/ ├── decisions/ ├── conventions/ ├── systems/ └── migrations/
Why an open repository helps
A knowledge repository can hold the constraints and intent that a diff will never fully show.
How Okide helps
Okide is where that engineering context stays editable and reviewable, next to the decisions agents should read before they change code.
Humans and agents, same files
Coding agents become more useful when they understand constraints and architectural intent before editing code.
OPEN BY DEFAULT
Keep the repository. Change the tools around it.
The codebase explains behavior. The knowledge repository can explain the constraint. Okide helps you work with the repository without turning it into an Okide-only format.