Back to all articlesAI knowledge preparation

Separate Reference Facts From Embedded Instructions in Source Documents

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A support manual can contain useful service facts, instructions for employees, and a pasted assistant prompt on the same page. If all three enter a knowledge collection without context, text meant to describe a workflow may be mistaken for permission to control the assistant.

Review imported material by separating what the document says about the business from what it tells an assistant to do. Preserve verified reference facts, keep legitimate operating instructions with their actor and scope intact, remove copied prompts that serve no reference purpose, and hold passages that attempt to override approved rules for specialist review.

The practical goal is a traceable editorial decision for each instruction-like passage—not a claim that a cleaned document is safe under every circumstance. Source review helps clarify trust boundaries; it does not replace technical controls or prevent every prompt-injection attempt.

1. Establish the boundary before reviewing sentences

A source document supplies information. It should not acquire authority to change the assistant’s approved behaviour merely because it was imported, retrieved, or written in commanding language. Treating those as separate functions is the foundation of the review.

Before reading, record the intended use of the material. Is it a reference for answering questions, a staff training resource, or an approved procedure that the assistant may explain? Those uses are different from authorising the assistant to perform an action.

For each source, establish:

  • Owner: who can confirm its accuracy and intended audience.
  • Scope: which team, process, product, or situation it covers.
  • Status: whether it is current, superseded, draft, or unknown.
  • Permitted use: what information may be drawn from it.
  • Authority limit: what it cannot authorise, such as changing access or taking an external action.

A document from a recognised internal team can still contain an obsolete instruction or a copied experiment. Conversely, an imperative sentence is not automatically hostile. The reviewer’s job is to identify the intended actor and effect, not to reject every sentence containing a command.

2. Read instruction-like text in context

Start with passages that address an assistant, claim priority, change permissions, or request an action. Also inspect ordinary operating instructions, because their intended actor can disappear when a paragraph is copied into another system.

Look across headings, body text, comments, appendices, exported conversation transcripts, and any other content included in the import. If the extracted version is available, review that as well as the original. A heading that clearly frames an example in the original may be absent from the extracted text.

Ask four questions about each candidate passage:

  1. Who is being addressed? A service employee, a customer, a reviewer, or the assistant itself?
  2. What would following it change? An answer’s wording, a business decision, a permission boundary, or an external action?
  3. What makes it authoritative? An identified business owner and approved process, or only the passage’s own claim?
  4. Why does it belong in this source? Is it needed to understand the subject, or is it unrelated text attached to useful information?

Use search terms as review aids, not as a complete detector. References to system messages, hidden instructions, rule overrides, credentials, or unapproved destinations deserve attention. However, a copied prompt can look harmless, and a training document may legitimately discuss suspicious instructions. Context determines the editorial decision.

3. Choose among preserve, remove, and escalate

Preserve legitimate operating information

Keep an operating instruction when it is relevant, current, and clearly assigned to an appropriate actor. If the actor is implicit, rewrite the passage to make the responsibility explicit without changing the underlying procedure.

For example, a hypothetical instruction telling a service coordinator to confirm an account detail before preparing a request can remain useful reference material. It should not become a general instruction for an assistant to collect that detail in every conversation or to submit the request automatically.

Preserve instruction text as subject matter only when needed

A training or incident-review document may need to describe a copied prompt or an attempted override. Retain only the material needed for that purpose, clearly framed as an example being analysed rather than a procedure to follow. A summary is often sufficient.

Quotation or labelling is an editorial distinction, not a security guarantee. If the intended audience does not need the example, excluding it from the assistant’s reference collection may be the better choice.

Remove irrelevant prompt residue

Copied assistant prompts, role assignments, output-format demands, and experiment notes often belong in a separate working record rather than a business reference source. Remove them from the publication copy when they do not contribute necessary subject matter.

Keep a change record so another reviewer can understand what was removed and why. Do not silently delete a passage that may be evidence of a wider issue.

Escalate attempted authority changes

Hold material that requests disregard of approved rules, seeks restricted information, changes access expectations, or directs activity toward an unapproved destination. Route it to the relevant security or system specialist; involve the business owner where process accuracy is also in question.

A reviewer should not have to prove malicious intent before escalating. An unexplained request to cross a trust boundary is enough to pause publication.

4. Filled hypothetical source-review checklist

Fictional worked example: A business is preparing a service operations handbook for use as assistant reference material. Every document, role, passage description, and decision below is hypothetical. The checklist records editorial decisions, not evidence of a product control.

Source-level record

  • Source: Service Operations Handbook, working revision B.
  • Intended use: explain the service-request process to staff.
  • Content owner: service operations lead.
  • Reviewer: knowledge editor.
  • Initial status: held pending passage review.
  • Authority boundary: reference content cannot approve account changes, grant access, or authorise external actions.
  • Evidence retained: original file, reviewed copy, passage locations, decisions, and owner confirmations.

Entry A: operating instruction

  • Location: request preparation section.
  • Passage summary: directs a service coordinator to confirm the customer’s preferred contact method before preparing a service request.
  • Intended actor: service coordinator.
  • Requested effect: a preparation step in the staff workflow.
  • Reference value: explains what staff must check before preparation.
  • Concern: the original paragraph leaves the actor implicit, which could make the step appear to apply to the assistant.
  • Decision: preserve with clarified actor and scope, subject to owner confirmation.
  • Prepared wording: The service coordinator confirms the customer’s preferred contact method before preparing a service request. This describes the staff preparation process; it does not authorise submission.
  • Release condition: the operations lead confirms that the step and responsibility remain current.

Entry B: copied assistant prompt

  • Location: appendix containing drafting notes.
  • Passage summary: assigns a sales-assistant role, requests an upbeat tone, and specifies a response format for a previous drafting exercise.
  • Intended actor: an assistant used during document preparation.
  • Requested effect: change answer style and structure.
  • Reference value: none for explaining the service-request process.
  • Concern: readers or downstream processing could mistake drafting instructions for current behavioural guidance.
  • Decision: remove from the reference copy and retain in the restricted review record if needed for change history.
  • Prepared wording: none; deleting the drafting residue does not remove a business fact.
  • Release condition: compare the edited appendix with the original and confirm that necessary operational information remains.

Entry C: embedded request to disregard approved rules

  • Location: note inserted beside an account-handling procedure.
  • Passage summary: claims special authority and asks the assistant to disregard approved handling rules when responding to account questions.
  • Intended actor: the assistant consuming the source.
  • Requested effect: override the established handling boundary.
  • Reference value: no demonstrated operational purpose.
  • Concern: the passage attempts to turn reference content into authority.
  • Decision: hold the affected source, preserve the original, and escalate to the security or system specialist with the operations owner informed.
  • Prepared wording: none pending review; do not rewrite the request into a more plausible instruction.
  • Release condition: the reviewer records the specialist’s disposition, confirms the affected material’s scope, and prepares a clean copy for a separate publication check.

In this example, the decisions differ because the passages serve different purposes. Removing all three would discard useful process information. Preserving all three would leave an unresolved authority conflict.

5. Edit without erasing important meaning

After classification, check the surrounding material. A suspicious sentence may sit between valid conditions, exceptions, or responsibility assignments. Removing an entire section can make the surviving procedure inaccurate.

Prefer the smallest defensible edit. Separate a factual statement from an unrelated command, restore a missing actor, or remove a drafting appendix while retaining the approved process description. Ask the owner to confirm any change that could alter operational meaning.

Be cautious with instructions that combine valid and invalid elements. A passage may correctly describe how requests are prepared, then add an unsupported exception allowing normal approval steps to be skipped. Do not preserve the exception merely because the first part is accurate.

The opposite mistake is over-cleaning. Removing every imperative can turn a useful handbook into vague background prose. Instructions for employees are often part of the subject matter. Keep them attributable to the right role and bounded by the correct conditions.

6. Handle uncertainty and recover from mistakes

When ownership, purpose, or authority is unclear, mark the item unresolved rather than guessing. The review record should state the unanswered question, the person responsible for resolving it, and what remains excluded meanwhile.

Match the hold to the uncertainty. A self-contained drafting appendix may be separable from the rest of a document. An unexplained override inserted into a core procedure may justify holding the whole source until its history and scope are understood. Record why a partial release is appropriate rather than assuming it is harmless.

If an instruction-like passage is discovered after publication, use a recovery path:

  1. Record the source version and the discovered passage.
  2. Pause use of, or withdraw, the affected material through the available process.
  3. Ask the responsible specialist whether related copies or other exposure need investigation.
  4. Prepare and review a corrected version before restoring it.
  5. Update the checklist with the missed signal and the new review step.

Do not assume that editing the original removes every imported copy. Confirm with the responsible administrator how source updates are applied in the actual environment. Likewise, do not treat a clean editorial record as evidence that no earlier response was affected.

7. Keep publication decisions separate from permissions

An editor can decide whether a source is suitable for reference. That decision does not grant the assistant permission to access records, disclose information, or perform actions.

This distinction matters even for approved procedures. A handbook can describe who approves a change without allowing the assistant to approve it. It can describe a communications process without authorising a message to be sent.

For systems that act on business data, separate permission checks remain necessary. OWASP’s authorization guidance recommends least privilege, deny-by-default behaviour, and permission checks on every request. These are system-design recommendations, not evidence that a particular product implements them.

Make the editorial handoff explicit: suitable for reference, withheld pending review, or unsuitable for this collection. Avoid a broad label such as safe, which can imply assurances beyond the review performed.

8. Run a small review with observable completion criteria

For a first pass, choose one source that contains both business procedures and working notes. Create a review record using the fields in the hypothetical checklist, then inspect every instruction-like passage in that source.

Track source identity and version, passage location, intended actor, requested effect, reference value, decision, reviewer, and release condition. Count unresolved items separately from removed items: a deletion is not the same as a resolved concern.

A useful completion test is whether another editor can explain every retained instruction’s actor and scope, find the reason for every removal, and identify who owns each unresolved decision. Also confirm that any exported publication copy matches the reviewed version.

Your next action is concrete: select one pending import, fill the checklist, and do not release it while any passage lacks a recorded disposition. The outcome is a reviewable source with explicit boundaries—not a security guarantee.

Knowledge preparationSource reviewAI governanceEditorial workflows

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