Knowledge Base
Everything RunOlga knows about the organization and its people: the ground truth Olga reasons from.
Phase 1 + roadmap
The Knowledge Base is everything RunOlga knows about the organization: its Vision, its seats and accountabilities, its Priorities, Issues, Processes, and Metrics, and — on the roadmap — what it knows about its people. It is the substrate Olga grounds every answer in. When Olga tells you something, it comes from here, not from her own invention.
What the Knowledge Base is
The Knowledge Base is the organization's accumulated knowledge, held in one place. It is not a separate document you write; it is the sum of the records the leadership team already keeps:
- The Vision — Core Values, Core Focus, the longer-range targets, and the near-term plan.
- The Accountability Chart — the seats and what each is accountable for.
- The Priorities and Tasks the team is working this quarter.
- The open Issues, the documented Processes, and the Metrics on the Scorecard.
Every record the organization captures becomes part of what Olga can reason from. That is the point: the more the organization writes down, the more grounded and useful Olga's answers become.
The Knowledge Base in Phase 1
In Phase 1, the organization's content is Olga's knowledge base. There is no separate, managed Knowledge Base feature to populate — the records the team keeps are the knowledge, and Olga reads directly from them.
Two stores hold that knowledge, and Olga grounds every answer in them:
| Store | What it holds |
|---|---|
| Instance Store (Layer 2) | The organization's content: its Vision, seats, Priorities, Issues, Processes, Metrics, and Tasks. Different for every organization. |
| Live Context Store | Current operational state, updated in near-real-time as people work in RunOlga. |
When you ask Olga a question, she retrieves the relevant records from these two stores and answers from what she finds. She does not speculate and she does not fabricate facts about the organization. When she does not have the answer in her knowledge, she says so plainly. For how this composition works across all three layers — including her methodology layer — see how Olga works.
Every answer carries provenance: a record of which store it came from and which records were accessed. That makes Olga's knowledge traceable, not a black box. See grounding and confirmation for how grounding and provenance are enforced.
You: What are our Priorities this quarter?
Olga: Here are the three Priorities on record for this quarter, each with its owner and target date.
This is retrieval, scoped to what you have permission to see. Olga reflects the knowledge back; she does not interpret it, rank it, or tell you what to do about it.
People knowledge
On the roadmap, the Knowledge Base extends beyond the operating records to what the organization knows about its people — a managed body of knowledge that supports people reviews and 1-on-1s and informs how leaders work with their seats.
With that knowledge in place, the intent is for Olga to help leaders prepare for decisions, issues, and reviews — to help the user decide based on the guidance the organization has captured. That is roadmap work, not Phase 1.
In Phase 1, Olga does not advise, recommend, or decide. She prepares, proposes, surfaces, and captures — and stops there. She has no managed people-knowledge base to draw on and offers no guidance from one. For exactly where the line sits between what Olga does today and what is on the roadmap, see Scope and roadmap.