Remember why the decision made sense at the time.

Decisions age better when context and alternatives survive with them.

The problem

A decision without its alternatives and date is easy to treat as an accident, or to reverse without knowing what it was protecting.

What goes in the repository

Decision
Date
Problem
Alternatives
Rationale
Owner
Consequences
Later changes

decisions/
├── index.md
├── 2026/
│   ├── choose-okf.md
│   └── local-first.md
└── deprecated/

Why an open repository helps

Keeping the old decision, including ones you no longer follow, preserves the reason the current constraint exists.

How Okide helps

Okide keeps each decision as a file with its context, so history stays attached to the choice instead of disappearing into a thread.

Humans and agents, same files

An agent can distinguish an intentional constraint from an accident before proposing to reverse it.

OPEN BY DEFAULT

Keep the repository. Change the tools around it.

Reversing a decision is safer when the original alternatives are still in the repository. 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

ROLES

Engineering knowledge

Preserve architecture, decisions and technical context.

engineering/architecture/

Explore →

ROLES

Product knowledge

Keep the reasoning behind the roadmap.

product/decisions/

Explore →

TEAMS

Project knowledge

Give every contributor the same context.

projects/atlas/index.md

Explore →