Define What an Approved Source Is Actually Allowed to Answer
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A product overview is approved for use, so an AI assistant uses it to answer a prospect’s question about features. Then it uses the same document to confirm that those features are included in the prospect’s subscription, available in their workspace, and guaranteed for the duration of their agreement. The source has not changed. The authority assigned to it has expanded without anyone deciding that it should.
To define source authority for AI knowledge, specify the questions a source may support, the questions it must not resolve, the intended audience, and the business conditions under which it applies. Approval should mean approved for a stated purpose in a stated context, not approved as a universal answer source.
A practical way to make that distinction usable is a source authority card: a short record attached to a specific document version. The filled hypothetical card below shows how a product overview can support feature descriptions while remaining insufficient for contractual commitments, account eligibility, or customer-specific exceptions.
1. Replace the approval badge with an answer boundary
A label such as “approved” leaves too much unstated. It may mean that the wording passed editorial review, that a product owner checked the feature descriptions, or that the document is suitable for public distribution. None of those decisions necessarily establishes what an assistant may conclude from it.
Separate three questions:
- Is this source usable? Identify the approved version, its owner, and its review status.
- What can it establish? Name the claims and question types it can support.
- Where does that authority apply? Specify the audience, product, interface, plan, market, and time period where relevant.
A source can be reliable and still be insufficient for a particular answer. A feature overview may accurately explain what a capability does, while saying nothing about whether a particular customer has purchased it. That is a scope mismatch, not necessarily a factual error in the document.
Write the boundary as an operational instruction. “Useful for product questions” is too broad. “May explain the purpose and documented behaviour of the features listed in this version; may not establish account entitlement or future availability” gives the assistant and its reviewers a decision they can apply.
2. Describe answerable claims, not just subject areas
Topic labels alone are weak boundaries. A document tagged “reporting” could be used to explain a report, promise access to it, confirm historical data retention, or make a commitment about future reporting functionality. Those are different claims, even though they share a topic.
For each source, describe the allowed answer in terms of what it can establish:
- Descriptive: What is the feature for, and what does the source explicitly say it does?
- Instructional: Does the source establish a procedure for the relevant interface and version?
- Eligibility-related: Does it establish who can access the feature under current conditions?
- Customer-specific: Does it establish anything about this particular account?
- Commitment-related: Is it an authorised basis for an organisational promise?
These categories are a recommended design for reviewing sources, not a requirement to grant every category to every document. Most product overviews should have a narrower role than detailed operating instructions or current entitlement records.
Also distinguish an explicit statement from an inference. A source that describes task assignment does not, by itself, establish automatic assignment, support on every device, or inclusion in every subscription. If a capability or condition is not stated, the card should prevent the assistant from filling the gap with a plausible assumption.
3. Filled hypothetical source authority card
Fictional worked example: The product, document, features, dates, and organisational roles below are hypothetical. They illustrate a recommended operating design, not existing Alactic functionality or customer results.
The fictional business publishes an overview of “Harbour CRM.” It wants assistants to explain the listed features without turning general descriptions into account-specific assurances.
Source identity and review status
- Source ID: HARBOUR-OVERVIEW-2026-04.
- Document: Harbour CRM Product Overview, April 2026 edition.
- Source type: Public-facing product overview.
- Accountable owner: Product Marketing Lead.
- Factual reviewer: CRM Product Manager.
- Approved use: General feature explanations within the boundaries below.
- Review trigger: A listed feature changes, product packaging changes, an interface claim changes, or a reviewer identifies an unsupported answer.
- Scheduled review: July 2026. A scheduled review does not override a known change that requires earlier reassessment.
Answerable topics
- Explain the stated purpose of contact records: keeping documented contact information together.
- Explain the stated purpose of a deal board: viewing opportunities by stage.
- Explain the stated purpose of task assignment: assigning follow-up work to a team member.
- Summarise these listed capabilities for a general product introduction.
- Distinguish a feature description from an account-specific availability decision.
Excluded topics
- Whether a particular workspace currently has a feature enabled.
- Whether a feature is included in a named customer’s subscription or negotiated package.
- Contractual commitments, service guarantees, or changes to an agreement.
- Customer-specific exceptions, discounts, concessions, or special operating arrangements.
- Future release dates, roadmap commitments, or continued availability.
- Security, certification, performance, integration, or automation claims absent from this document.
- Exact setup instructions, screen locations, or Android behaviour not documented in this version.
Audience and applicable business context
- Intended answer audience: Prospects and customers seeking a general product explanation; internal staff preparing the same explanation.
- Product boundary: Harbour CRM only. Do not transfer claims to another product in the fictional business’s portfolio.
- Interface boundary: The overview describes the browser product. It does not establish mobile-app feature parity.
- Plan boundary: The overview does not establish plan inclusion. Check the current plan and workspace before asserting availability.
- Market boundary: No market-specific eligibility is established. Do not infer universal availability.
- Time boundary: Use the approved edition while it remains current. Do not use it as evidence of historical account behaviour or future commitments.
Answer rules and fallback
- Allowed formulation: Describe only the capabilities expressly covered by the overview, preserving any stated limitations.
- Insufficient-evidence rule: Silence does not prove that a capability exists or that it is unavailable.
- Mixed-question rule: Answer the supported descriptive part, then identify the part that needs another source.
- Conflict rule: Do not use this overview to override current account-specific evidence or another source designated to establish the disputed claim. If the conflict cannot be resolved, withhold that conclusion and route it for review.
- Fallback route: General feature ambiguity goes to the Product Manager. Plan or workspace availability goes to the account-support owner. Requests for commitments or exceptions go to the designated commercial owner.
- Traceability: Record the document ID and relevant section used for the descriptive answer.
This card is intentionally restrictive about eligibility and commitments. It preserves the overview’s value without making it responsible for decisions it was not written to establish.
4. Test the card against questions that change meaning mid-sentence
The most useful tests combine an answerable question with an unsupported conclusion. A simple feature question may pass even when the authority boundary is poorly defined.
Hypothetical question: “What does the deal board do, and is it included in our subscription?”
The card permits a general explanation of the deal board. It does not permit confirmation of subscription inclusion. A bounded answer explains the documented purpose, then says that inclusion requires checking the current plan and workspace. It should not force the reader to repeat the entire question to get the supported portion answered.
Hypothetical question: “Can you confirm that task assignment will remain available throughout our agreement?”
The overview cannot establish that commitment. Repeating its feature description would not answer the actual question. The assistant should state that the overview is insufficient and route the request to the designated owner, without interpreting the agreement.
Hypothetical question: “Your overview lists contact records. Why can’t I see them in the Android app?”
The browser overview does not establish Android availability or diagnose the account. The next evidence needed concerns the app, workspace, and current plan. The assistant must not invent a navigation path merely because the feature exists somewhere in the product.
Hypothetical question: “Does the absence of integrations from this overview mean there are none?”
No such conclusion is supported. The correct boundary works in both directions: do not invent a positive claim, and do not turn missing coverage into proof of absence.
5. Keep audience, access, and authority separate
An intended audience tells you whom the source was written to inform. It does not, on its own, establish permission to disclose the source or every detail within it. Likewise, permission to access a document does not make that document authoritative for every question.
Maintain separate checks for these decisions. A public overview might be suitable for a prospect but too general to resolve an account issue. An internal account note might be relevant to that issue but inappropriate to reuse in a public explanation. A source authority card should not replace access controls.
Business context needs similar precision. “Customer-facing” is not enough if a statement applies only to a particular product, interface, plan, or period. When a relevant context field is unknown, mark it unknown rather than treating it as unrestricted.
Do not overqualify every harmless answer. A general description may not require account details. Ask for additional context only when it could change the requested conclusion. This keeps the boundary useful without turning every product explanation into an intake questionnaire.
6. Make the boundary travel with the source
A card stored where nobody consults it will not constrain answers. In a recommended knowledge workflow, the source’s identity and authority metadata should remain connected to the content when that content is retrieved, excerpted, or copied into another knowledge location.
This matters when documents are split into passages. A paragraph describing a feature can look unconditional after its document-level limitations disappear. Preserve the relevant source ID, allowed use, exclusions, and context alongside the passage, or provide a reliable way for the answering process to consult them.
A practical sequence is:
- Identify the claim the reader wants established.
- Check whether the source permits that claim type.
- Check whether the applicable business context matches.
- Use the relevant content only if those checks pass.
- Otherwise, give a bounded partial answer or seek the missing evidence.
This is a recommended design, not evidence that any particular product enforces these checks. If enforcement is manual, make the card part of answer review. If tooling supports metadata-based controls, verify their behaviour with test questions rather than assuming that attached metadata is being applied.
7. Handle conflicts and repair overbroad approval
Do not resolve every conflict by choosing the newest document. A recently edited overview can still be less suitable for a workspace-eligibility question than a current record designated for that purpose. Compare the authority for the specific claim, contextual fit, and currency together.
If the card fails to distinguish two competing sources, treat that as a governance gap. Ask the responsible owner which source may establish the disputed point, then update the boundary. Do not let an assistant silently invent a hierarchy.
When an unsupported answer has already been produced, repair both the answer and the reusable cause:
- Identify the exact unsupported conclusion, not merely the document used.
- Correct or withdraw that conclusion where appropriate.
- Check whether the cause was missing scope, lost context, stale content, or an ignored boundary.
- Revise the card or its handling, then retest the failure and related questions.
There is a trade-off between narrow authority and answer coverage. Tighter boundaries may increase referrals. Broad boundaries may reduce referrals while allowing unsupported assurances. Expand a source’s authority only when its content and review process actually support the additional claims—not simply because the fallback queue is inconvenient.
8. Run a small authority review before expanding
Start with one frequently reused product overview. Fill the card, have its factual owner check the boundaries, and run a focused question set before applying the pattern more widely.
Hypothetical review exercise: Use twelve questions: four descriptive questions the source should answer, four excluded questions it should not resolve, and four mixed-context questions requiring a partial answer or clarification. These counts are a proposed exercise, not a benchmark.
Record whether each answer uses the right source scope, preserves relevant context, and offers a useful next step when evidence is missing. Count unsupported conclusions separately from unnecessary refusals. A system that refuses every question has not demonstrated useful source authority.
The immediate deliverable is one reviewed card and a recorded test result for every question. Any unsupported commitment should block broader use of that source until its cause is corrected. That gives approval a concrete meaning: this document can support these answers, for these readers, under these conditions—and no more.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications