Keep important rules versioned and reviewable.

A policy is only useful when people can find the current version and understand where it came from.

The problem

Policies without effective dates, owners and a record of approved changes are difficult to trust, and easy to confuse with an older copy.

What goes in the repository

Policies
Procedures
Effective dates
Ownership
Approved changes
Supporting sources
Deprecated versions

policies/
├── index.md
├── security.md
├── finance/
├── people/
└── deprecated/

Why an open repository helps

Versioned policy keeps the current rule and the history of how it got there. Deleting the old text deletes the trail.

How Okide helps

Okide keeps the current policy and its deprecated predecessors in the repository, where a change can be reviewed like any other.

Humans and agents, same files

Policy-aware agents can reference maintained source material rather than treating model knowledge as organizational policy.

OPEN BY DEFAULT

Keep the repository. Change the tools around it.

The current rule matters. So does the ability to see what it replaced. 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

Operations knowledge

Document how the work actually runs.

operations/processes/

Explore →

COMPANIES

Company knowledge

Build institutional memory the organization can keep.

company/principles.md

Explore →

TEAMS

Runbooks

Keep operational knowledge readable and current.

runbooks/api-outage.md

Explore →