Keep multiple products understandable without one giant document.

Each product can own its context while the portfolio keeps a shared structure.

The problem

Portfolio strategy, shared capabilities and product-level decisions collapse into one document, or scatter so far apart that nobody can see the relationship.

What goes in the repository

Portfolio strategy
Product context
Dependencies
Shared capabilities
Positioning
Product-level decisions
Ownership

products/
├── index.md
├── platform/
│   └── index.md
├── analytics/
│   └── index.md
└── agents/
    └── index.md

Why an open repository helps

A directory of products lets someone start at the portfolio and open only the product that matters.

How Okide helps

Okide keeps each product’s index in the same repository, so the portfolio stays browsable without becoming one file.

Humans and agents, same files

Agents can navigate from company-level context into the product relevant to the task instead of receiving every product at once.

OPEN BY DEFAULT

Keep the repository. Change the tools around it.

More products should mean clearer structure, not a longer document. 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

Product knowledge

Keep the reasoning behind the roadmap.

product/decisions/

Explore →

COMPANIES

Company knowledge

Build institutional memory the organization can keep.

company/principles.md

Explore →

COMPANIES

Customer knowledge

Turn customer conversations into reusable context.

customers/segments/

Explore →