Write down what must hold.
Record the purpose, contracts, and constraints that give a project its identity. Organize them into layers your team can navigate.
From shared context to a considered change.
Ribo keeps the decisions behind your software accessible to people and agents—and gives the team a place to respond when those decisions need to evolve.
The Ribo workflow
Bring context into the work.
Give compatible agents scoped access through MCP, so they can find the identity relevant to the task at hand.
Surface what is unclear.
A question or finding can become a signal, connected to the context and to a proposal for addressing it.
Decide how the identity evolves.
People review proposed changes against current versions and policies. The decision and its history stay with the system.
An illustrative example
A question is part of the work.
A payments agent reads that charges must be idempotent, but finds the refund behavior unclear.
From question to decision
Keep the why connected to what changes.
The question is recorded as a signal. A proposal captures a possible update. Reviewers decide whether it should become part of the shared identity.
Explore the product ↗