Begin at the moment of doubt
A manager receives a short comparison of two suppliers and notices that one delivery condition looks unfamiliar. The immediate question is not which model wrote the paragraph. It is where the condition came from and whether the underlying document still applies. Design the evidence trail around that moment. The reader should be able to move from a claim to the relevant source passage, see the document’s identity and understand its status. Provenance becomes useful when it supports an ordinary act of checking, without requiring the reader to reconstruct the entire processing system.
Preserve the identity through transformation
Information can move through several forms before appearing in an answer: a scanned page becomes text, a table becomes structured rows, and selected passages become a working collection. Each transformation can make material easier to use while obscuring its original context. Keep a connection to the original item and record the transformation that produced the current form. When a table cell appears questionable, the reviewer should know whether to inspect extraction, interpretation or the source itself. A traceable identity turns a vague accuracy concern into a question that someone can investigate.
Record judgement as well as movement
A technical lineage map may show every processing step and still omit the decision that mattered most. Someone excluded an older policy, selected a regional version or resolved a conflict between two records. Those choices shape the answer as directly as any transformation. Add a concise decision note where human judgement changes the working material: what was chosen, why, by whom and for which scope. This does not require turning every action into a long report. It requires recognising the points where another reasonable reviewer might have made a different selection.
Design for changed material
Sources do not remain still after a report is produced. A document can be corrected, replaced or withdrawn, leaving an earlier answer with an uncertain relationship to current information. Decide whether the output represents a historical snapshot or is expected to remain current. Then make the applicable date and update responsibility visible. A snapshot needs its original evidence preserved; a continuing service needs a way to discover affected outputs. The distinction prevents a convenient link to the latest document from silently rewriting the evidential basis of an earlier decision without a record.
Make the trail proportionate
Not every reader needs to see the full history in the first view. A short answer can present the supporting source and a clear route to more detail, while reviewers can inspect transformations and selection notes when necessary. Decide which questions each layer should answer before adding more metadata. Too much undifferentiated history can make checking harder rather than easier. The practical test is simple: can a person identify the basis of an important statement, locate the relevant uncertainty and decide what to do next within the context of the task?
Editorial draft prepared for the BGX concept preview. This is not a regulatory announcement or evidence of a deployed client project.
