Docs / Concepts

The knowledge base

The knowledge base is REEZN’s picture of the concepts your organization works with and how they relate. It builds itself from the work you approve and the context you connect, and REEZN draws on it when planning new features, so each one stays grounded in what you’ve already built and decided.

The knowledge base is a Business-plan capability. On other plans it isn’t active, and features still generate normally from your definition, norms, safeguards, and connected code.

Where norms and safeguards are rules you write by hand, the knowledge base is context REEZN builds and maintains on its own. As your team approves work and connects more of your world to REEZN, it grows into a shared picture of your product’s concepts, without anyone having to curate it for it to be useful.

What it captures

The knowledge base organizes what your organization works with as concepts and the connections between them: the kind of shared mental model a long-tenured engineer carries, made explicit so every plan can draw on it.

Concepts: The things your product is built around: domain objects, services, policies, the audiences you serve, each with a short description and the names it goes by.
Connections: How those concepts relate to one another, so understanding one naturally brings the concepts around it into view.

Where it comes from

REEZN builds the knowledge base automatically from the material that already flows through your organization. It draws on:

Approved analysis documents and canvases: the concepts, approaches, and decisions in work your team has signed off on.
Norms and safeguards: your standards and hard limits, as you add or change them.
Personas: the audiences your product serves.
Documents you upload: admin-provided markdown such as architecture notes, glossaries, or domain write-ups.
Connected service repositories: the shape and vocabulary of the code REEZN reads for a service.

What it does for your plans

When REEZN drafts an analysis or a canvas, it automatically brings in the parts of the knowledge base relevant to that feature, alongside your definition, norms, safeguards, and connected code. The result is plans that speak in your product’s own terms and account for the concepts a change is likely to touch, without anyone having to remember and restate them each time.

Browsing and curating it

Admins can explore the knowledge base from the Knowledge page in the sidebar, shown as an interactive map you can navigate. Because it maintains itself, curation is about refining rather than authoring:

Explore it visually: see which concepts are central and how they connect.
Refine what’s there: sharpen a description or add the alternate names a concept goes by, and tidy up as the picture matures.
Add your own context: upload documents to seed knowledge that isn’t yet captured in features.

Curating the knowledge base is admin-only. Everyone else simply benefits from sharper, better-grounded plans.

Why this exists

The hardest part of planning a change is knowing what already exists and how it fits together: knowledge that usually lives in a few people’s heads and erodes as teams change. By building that picture automatically from work you’ve already approved and drawing on it in every new plan, REEZN lets each feature be planned against the accumulated understanding of the whole organization rather than from a blank slate.