Skip to content
MirrorFirm

What generated artefacts can define the evidence package an agent must produce?

A release can specify the reviewer-facing deliverable through package structure, excerpt rules, attachment handling and explicit treatment of unresolved findings.

Ask for generated artefacts that define how the finished package should be organised, so the agent must produce something a reviewer can navigate and assess.

- A package manifest template listing each included item, its purpose and its position in the review sequence for the assigned request. - An excerpt convention requiring selected passages to retain surrounding context when a qualification changes the meaning of the quoted statement. - Attachment rules explaining when a supporting file must travel with its parent record and when a reference alone is acceptable. - A finding template separating the claim being assessed, the supporting material and any unresolved qualification that affects the reviewer's decision. - A duplicate-handling guide distinguishing repeated copies of the same attachment from separate records that happen to contain similar wording. - A reviewer navigation map connecting package sections to review questions, so the agent cannot substitute a large undifferentiated document bundle. - A completion note format recording outstanding requests and the consequences of proceeding with the currently assembled package rather than waiting.

Make the target output concrete enough to train package assembly, rather than stopping at document selection.

Audience:
Agent developers
Content type:
Checklist
Buyer question:
What can be generated

Content release: r-a220eb6e099b243b

More on Audit evidence assembly