Specific knowledge. Broader understanding.
Your facts. A wider perspective.
Bring the details only your organization knows together with the context that helps people understand and apply them.
Specific facts and broader context have different jobs.
A question can need more than the facts in one document.
A specification tells you what a product does. It may not explain how that detail affects an unfamiliar application. A project report records a result. It may not contain the scientific or industry context needed to interpret it.
KnowScapes is built around this combination: keep your own information in the conversation while using broader knowledge and reasoning to explore what it means.
World knowledge supplies breadth.
Models and permitted external sources can contribute technical concepts, industry background, scientific explanations and other knowledge beyond your own material. That context can help a user formulate better questions or consider an alternative approach.
Breadth is not the same as current, verified knowledge. A general model may not know the latest change, and it does not automatically know your unpublished product details or internal decisions.
Organizational knowledge supplies the specifics.
Your website and documents describe the products, methods, terminology and recorded experience that distinguish your work. They give an Expert information a general-purpose model would otherwise have to guess or ask you to provide.
The source still matters. An obsolete specification or an ambiguous procedure does not become authoritative just because it was processed into a Knowledge Base.
See the two contributions side by side.
| Question area | Your information | Broader context |
|---|---|---|
| Product suitability | Your specification and documented applications | Technical principles and application context |
| Project interpretation | Your findings, assumptions and recorded decisions | Relevant methods, research and alternative explanations |
| Process understanding | Your documented steps and terminology | Background concepts that explain why those steps matter |
These examples describe how the information can contribute. They do not imply that every external source or specialist workflow is automatically included.
When the information disagrees, ask a better question.
A difference between a source document and general background may reveal a special case, an old assumption or a gap in the evidence. It is a reason to investigate—not a reason to automatically prefer either input.
Check the reference
Which version, date or documented statement supports the answer?
Check the assumption
Does the general explanation apply to this particular product, process or situation?
Check what is missing
Which additional document or qualified review would help resolve the uncertainty?
Broader context must respect the processing choice.
The available world context depends on the selected reasoning model, permitted sources and processing configuration. World knowledge does not mean a continuous live feed or an exemption from the workload’s processing boundary.
In Enterprise internal Germany mode, workload content stays away from external AI processors. The reasoning and available context must remain within that mode; adding broader context does not authorize an external fallback.
Test both sides with a question you can judge.
Choose one real question, one relevant fact from your website or document, and the wider context needed to understand it. Ask the Expert to explain their relationship. Review whether it used the specifics correctly and made the uncertainty clear.
Given what our documentation says, what does this mean for this particular application—and what should we verify?
Make the conversation specific enough to be useful.
Start with your own content. Then ask the questions that require explanation beyond it.