Your knowledge base¶

Every agent run starts from what your workspace knows. An agent with no context writes plausible marketing copy about a product it has never seen. An agent that knows your positioning, your customers and your house style writes something you can actually ship.

Context is also the only part of Questo that compounds. A task is spent once. A tenet you sharpen today improves every run for as long as it stays true.

The knowledge base has five tabs, and they answer different questions.

Tenets: what is true about your business¶

Tenets are the eight standing facts about your company:

There are always exactly eight. You cannot add a ninth or delete one, because every agent run reads all of them and a stable set keeps that reliable. What you can do is edit any of them, at any time, and an empty tenet is a legitimate state if you genuinely do not have a view yet.

Onboarding fills in the first three (product, positioning, targeting) from your answers. Read them before you do anything else. They were drafted from a short conversation, and the wording is usually close but rarely exact.

Each tenet also carries a definition: scaffolding that explains what belongs in that tenet, which you can adapt to how your team thinks. The definition is the prompt; the text is your answer.

Tenets can be shared publicly by link, which is useful for handing your positioning to an agency or a contractor.

Competitors and personas¶

Two tenets talk about things with names of their own. Positioning is about the competitors you are measured against; Targeting is about the people in a deal. Each of those is a record with its own document, shown in a table between the tenet's title and its body. The tenet stays short: it summarizes and links to each record, and the detail lives in the record's document.

• A competitor is a battlecard. It notes what kind of alternative it is (direct: a product for the same job; indirect: a different way of solving it; or no product: doing it by hand, in spreadsheets, or hiring for it) and its site, and the rest is a free-form document. A good battlecard usually covers who they are, their pricing, where they win, where you win, their gaps, and how to spot them in a deal.
• A persona is a profile. It notes the role and company size, and the rest is a free-form document: usually their situation, pains, triggers, how they evaluate, objections, and quotes in their own words.

Those sections are suggestions, not a form: write the document the way your team actually thinks about competitors and buyers. A workspace holds up to 12 competitors and 5 personas. Click a row to open the record's document; changes save as you type, and History shows every edit with Undo.

Everywhere else, a tenet mentions a record as a link rather than as typed text. A link always shows the record's current name, so renaming a competitor updates every tenet, chat and shared page that mentions it.

Evidence. An insight can be linked to a competitor or a persona as evidence. The agent does this when a web scan or a conversation turns up something relevant, and you can see the evidence on the record. A link can say whether the insight confirms what the record says or contradicts it; a contradiction is a sign that what you wrote may no longer hold and is worth a second look.

During onboarding, the agent drafting Positioning writes a battlecard for each competitor and the one drafting Targeting writes a profile for each persona. Once they have, the names in your other tenets are turned into links automatically.

Linking anything with /¶

In any document, type / at the start of a line or after a space to open a list of everything in your workspace: tasks, missions, outputs, insights, tenets, rules, skills, URLs, files, competitors and personas. Keep typing to search, then pick one to insert a link to it. Press Escape to keep the / as plain text.

Skills: reusable know-how¶

A skill is a piece of reference content the agent should have at hand. A messaging framework, a qualification checklist, the structure your one-pagers follow, the way your team runs a competitive teardown.

Use a skill when you find yourself pasting the same explanation into task prompts. Write it once, and it is available on every run.

Below your own skills, the Skills tab lists the ones built into Questo: the procedures the agent follows for work like writing a document or scoping a mission. Open one to read it. They are the same in every workspace and cannot be edited.

Rules: standing instructions¶

A rule is an instruction every teammate's agent should follow rather than a fact it should know. "Never claim we are the market leader." "Always include a pricing line in outbound emails." "Write dates as 14 March, not 3/14."

Rules are the natural home for corrections. When you edit an output because the agent did something your team always wants done differently, that difference is a rule.

The distinction from skills is worth keeping clean. A skill is knowledge the agent draws on. A rule is a constraint the agent obeys.

Files: your documents¶

Files are documents in your workspace: uploads from you, and deliverables the agent produced while working. Both live here.

The switch that matters is knowledge. Marking a file as knowledge means "this is reference material for the whole workspace", and it is what the agent reads on future runs. It is curation, not history. A file being present does not make it knowledge; you saying so does.

That distinction exists because the agent writes a lot of files while it works. Intermediate research, scratch drafts, one-off exports. If every byte the agent ever wrote were treated as reference material, your context would fill with noise inside a week. So the default is no, and you promote the ones worth keeping.

Files you attach to a single task are a different thing again. Those are context for that piece of work, not for the workspace.

URLs: live references¶

A URL is a named link the agent can read as reference. Your own site and pricing page, competitor pages, an analyst report, a docs site you integrate with.

Add the pages you would check yourself before writing something. The agent will check them for you.

Private pages from Notion and Google Drive¶

A private page cannot be read from its address alone, so there is a second way in: pick it. During setup, Pick pages opens Notion's own screen, where you tick the pages Questo may read. Pick files opens Google Drive's file picker. Each page you pick becomes a URL here, marked as picked, and the agent reads it live every time it needs it.

Google's file picker needs your browser to allow Google's cookies on Questo. If it asks you to sign in to Google and never gets further, your browser is blocking them (Brave Shields and Safari do by default): allow cross-site cookies for Questo and pick again.

Questo can open the pages you picked and nothing else in that workspace. That is the difference from connecting all of Notion or Drive, which lets the agent search everything you can see. Pick when you know which documents matter; connect everything when you want the agent to go looking.

Deleting a picked URL stops the agent reading it. To withdraw access entirely, disconnect Notion pages or Google Drive files in Settings > Integrations, and remove Questo under Settings > Connections in Notion or under third-party access in your Google account.

What is not in here¶

Insights live in their own place, not in the knowledge base, and the distinction is worth keeping.

The knowledge base is what is durably true: your positioning, your house style, the framework you use. An insight is a dated signal: what a prospect said last Tuesday, what a metric read last month. Both feed the agent, but one is standing context and the other is news.

When a signal turns out to be durable, promote it by hand. A quote from one customer is an insight. "Our buyers care more about audit logs than about price" is a tenet.

Where the agent fits¶

The agent can edit knowledge itself. When it learns something during a run that contradicts or extends what you have written, it can change a tenet, skill, rule, competitor or persona.

Every edit it makes is recorded under your name in the item's History, and you can undo any single change from there or from the chat where it happened. Nothing it writes is silent: the change shows up in the chat as it lands, and History keeps the before and after.