Before you start
A Reasoner isn’t a general-purpose chat. It’s a reusable setup for one specific kind of work.
You choose one industry, define the business domains it should operate in, then add the work functions it should use. That structure frames every answer it gives later.
Add Axioms for the rules it must always respect — internal policy, approval logic, compliance boundaries. Then attach documents and reference material in the Knowledge Vault. When you ask a question, it answers inside that structure instead of drawing on an unstructured pile of context.
Finally, review each answer through its Reasoning Scope: the decision, the evidence behind it and any flags it raised.
Key terms
- Reasoner
- A reusable reasoning instrument built for one industry, the business contexts you operate in and the work it should perform.
- Industry
- The top-level anchor, with a Geo Focus. It sets the vocabulary and operating context. Each Reasoner has one.
- Business domains
- The parts of the business it operates in, such as Sugar - Merchandizing or Lending.
- Work functions
- The jobs it performs, such as hedging, credit risk underwriting or regulatory compliance. Each one defines the methods it applies.
- Axioms
- Hard rules the Reasoner treats as ground truth: regulatory obligations, internal policy, approval logic, prohibited actions. Always respected, always cited, and only applied while switched on.
- Knowledge Vault
- Where you upload PDF, TXT and CSV files so the Reasoner can use them as bounded evidence. Audit Vault checks them against each other for contradictions.
- Reasoning World
- The Studio map of your Reasoner: its industry, domains and work functions, and how well each domain is grounded in your documents.
- Decision
- How an answer ends: Answer, Ask for more, or Abstain.
- Reasoning Scope
- Correctness, Confidence and Veracity, alongside flags and evidence used. Score bars read like a traffic light.StrongerCautionWeaker
Getting started
The shortest path from an empty Studio to an answer you can verify.
- 1
Create your Reasoner
Choose one industry and its Geo Focus, add the business domains you operate in, then select the work functions it should use. First time here? A guided setup walks you through each step.
- 2
Set custom rules with Axioms
Open the Axioms tab in Studio and add explicit operating rules: policy constraints, approval requirements and the boundaries it must not cross. New axioms are in force as soon as you add them. Switch one off to pause it.
- 3
Load supporting material
In the Knowledge Vault, upload PDF, TXT or CSV files (up to 10 MB each) by dragging them onto the right cluster, so answers stay properly scoped. Run Audit Vault to check your documents for contradictions.
- 4
Ask practical questions
Use plain language. The answer streams in with a live reasoning trail, then settles into a decision, a recommended action and suggested follow-ups. Highlight any passage and choose Ask about this to dig in.
- 5
Review the audit trail
Check the Reasoning Scope, the flags, the evidence used and the full reasoning trail to see what supported the answer and where cautions were raised.
Guides
Download the user manual
The full Studio guide in one PDF, from creating a Reasoner to reviewing an answer. Keep it open while you work or share it with your team.
User manual
The day-to-day workflow, from a new Reasoner to an answer you can act on.
- Create a Reasoner from the Reasoners page, or let the guided setup lead you.
- Use Studio to shape it: Reasoning World, Axioms and the Knowledge Vault.
- Open Chat for the Reasoner and ask. Each Reasoner keeps one conversation.
- Try a demo Reasoner from the top bar before you build your own.
Document handling
What to upload, where to attach it, and how scope affects the evidence a Reasoner can rely on.
- Accepted files are PDF, TXT and CSV, up to 10 MB each.
- Drop a file onto the industry, business-domain or work-domain cluster it supports.
- Empty files and files that don’t match their type are rejected.
- Run Audit Vault to find contradictions between documents before they reach an answer.
Prompting guide
How to ask questions that produce clearer answers.
- Name the decision you need to make, not only the topic.
- Ask comparative questions: this contract against that policy, this quarter against last.
- If the Reasoner asks for more, upload the missing document and ask again.
- Use the suggested prompts and follow-ups when you’re not sure where to start.
Axioms and governance
How rules and Reasoning Scope shape an answer before anyone acts on it.
- Write each axiom as a hard rule, for example “Quantity tolerance can’t exceed 5%”.
- New axioms are In force right away. Switch one Off to pause it without deleting it.
- Answers show Correctness, Confidence and Veracity, plus flags from Critical to Info.
- Every answer ends in a decision: Answer, Ask or Abstain.
Questions
What should go into the Knowledge Vault?
The material an operator would actually trust at work: policies, operating procedures, transaction documents, historical references, datasets and internal guidance, as PDF, TXT or CSV files.
What file types and sizes can I upload?
PDF, TXT and CSV files, up to 10 MB each. Empty files and files whose contents don’t match their type are rejected.
Why does it matter where I attach a document?
Files attached to an industry, business or work cluster become evidence for that scope only. That stops an answer from borrowing support from the wrong area.
What are Axioms for?
They let you give the Reasoner rules in plain language: policy constraints, mandatory checks, approval requirements, definitions and instructions it should always follow. Answers cite the axioms they apply.
Can I pause an axiom without deleting it?
Yes. New axioms are in force as soon as you add them. Switch one off in the Axioms tab to stop applying it, and switch it back on when it should apply again.
When should I use an Axiom instead of a document?
Use an Axiom for a rule it should apply every time. Use a document for supporting material, evidence, examples or references it may need to inspect and cite.
What do Answer, Ask and Abstain mean?
Answer means the Reasoner has enough evidence to give a call. Ask means it needs something from you, usually a missing document. Abstain means it can’t support an answer from what it has.
How do I read the Reasoning Scope bars?
Correctness, Confidence and Veracity read like a traffic light. Green is a stronger signal, yellow means caution or mixed support, and red is a weaker result that deserves a closer look before you act.
Can I see how an answer was formed?
Yes. Every answer exposes its reasoning trail, flags and the evidence it used, so you can audit it rather than take it on trust.
Can a Reasoner cover more than one industry?
No. Each Reasoner is anchored to one industry, which keeps its vocabulary and evidence consistent. Create another Reasoner for another industry.
How can I try it before building my own?
Open a demo Reasoner from the top bar of the app. It comes with its own Knowledge Vault and chat, and you can reset it at any time.
How do I sign in?
With your work email and password, or by continuing with Google.
Ready to try it?
Create a Reasoner, add the Axioms and documents that define its scope, and ask your first question.