Knowledge
Eighty-eight entries. No index page.
This page is the one place on the site that could have shown you a table and didn't, on purpose. Here's what's there instead, and why.
Eighty-eight things somebody bothered to write down.
Each one started as a sentence in a conversation — a fact worth keeping, a correction to something assumed wrong, a note that would otherwise have lived only in scrollback and vanished with it.
88
Knowledge entries on record
0
Of them listed on this page
That second number is a choice, not a limitation this page ran into. Building a table of eighty-eight rows pulled from one operator's actual working notes would be easy and would also be publishing someone's private business record on a marketing site. So it stays where it is — in the account it belongs to, answerable to a question, not scrollable by a stranger.
There is no standing list inside the product either.
This isn't only a decision about what to publish on this page — it describes how the tool itself works. There is no "browse knowledge" screen anywhere in StratOps, because there's no screen anywhere in StratOps. What exists is a search: you ask a question, and it comes back with what matches, or it comes back with nothing rather than the nearest unrelated entry dressed up as an answer.
Eighty-eight loose facts arranged as a list to scroll wouldn't tell you much — most of them only mean something next to the question they answer. That's the same reasoning behind the rest of the product: questions get a whole answer assembled for them; nothing gets handed back as a static page you have to page through.
A knowledge entry starts the same way everything else does.
You say something worth keeping — not a task, not a meeting, not a decision with an outcome attached, just a fact. "The vendor's contract renews in March." "That integration only works over webhook, not polling." One sentence, one approval, and it's captured against the same account everything else lives in.
It sits there until a later question surfaces it — which might be weeks later, in a completely different conversation, about a completely different thing that happens to touch it.
- CorrectionsSomething assumed true that turned out wrong, written down so it isn't re-assumed.
- Standing factsDetails that don't belong to any one meeting or deal.
- ContextThe kind of thing that would otherwise only live in a person's memory of a call.
It doesn't read a file. It reads what you said.
Search here works on the words captured in conversation — it doesn't open a PDF, a slide deck or an uploaded document and index the inside of it. If the fact you need lives inside a file and nobody ever said it out loud, this search won't find it. See the documents page for exactly where that line sits.