An agent extracts specifications from a product document and submits them for review. Before approval, the document changes. Looking at the pending record alone may not reveal that it was generated from an older version.
What's a useful way to track this relationship in Busabase? Can the result retain the source version it used, so reviewers can identify which submissions need another check? I'd like the supporting document version to be clear during review.
Reviewers should be able to tell which source version an agent used. In Busabase, have the agent include the source Asset ID or node link, content hash/version identifier at read time, read timestamp, and a page or exact excerpt supporting each extracted fact in the proposed record or Change Request. A mutable filename alone is not enough evidence.
Busabase does not currently mark every pending derived result as stale automatically when its source file is replaced. Before approving, compare the identifier recorded on the proposal with the current source; if it changed, ask the agent to recheck the changed sections and revise the proposal. If reviewers must inspect the exact old version, retain an immutable copy or versioned reference under your retention rules rather than assuming an overwritten file remains available. Record each source separately when a result draws on several files.
We have logged automatic source-version impact flags as a separate request. Does your team replace a file at the same path, or upload each revision as a new file? The Chinese discussion covers the same review case.
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in