PLATFORM
Knowledge and context
Bring business information into context with traceability and access boundaries.
Overview
Good answers depend on relevant, permission-appropriate context. Treat connected knowledge as governed business information, not as a reason to bypass the source system’s access rules.
Select sources
Start with known repositories and clearly identify the system of record for each important data domain.
Preserve provenance
Where available, keep source names, links, timestamps and version information with retrieved material.
Respect permissions
Validate that users and workflows can access the source content they retrieve. Do not assume indexing alone grants permission.
Manage freshness
Define how updates, removals and access changes propagate. Establish an owner for stale or conflicting material.
Evaluate retrieval
Test representative questions, ambiguous terminology, missing answers and restricted content. Make uncertainty visible rather than inventing a source.
Worked example
When two sources disagree
A policy document and an older operational note return different answers. Make source authority and freshness explicit rather than asking the model to guess.
- 1Identify the system of record and the owner for the policy topic.
- 2Compare document versions and effective dates.
- 3Prefer the approved current source; surface the conflict if authority is unclear.
- 4Record the unresolved question and route it to the accountable owner.
- 5Correct or retire stale source material so the conflict is less likely to recur.
Was this guide useful?
Send feedback or flag a gap. Include the article link so the team can improve the right guide.