Evidence and operations

An assessment can carry attachments with a title, evidence type, upload date, uploader and visibility value. Internal and Shared are different choices that need an agreed audience. A test also holds an evidence reference, while a review decision has its own reason. These records work together when the team needs to reconstruct what the reviewer saw at a particular stage.

Operation receipts capture an action, an operation key, the expected assessment revision, occurrence date and result state. Pending, Completed, Failed and needs review distinguish an accepted effect from a request that needs investigation. The receipt can retain external and effect references or a failure reason. It gives an Assessment Owner a place to investigate a repeated or uncertain operation without assuming that a submitted command changed the assessment.

• Evidence. Attach files to the correct assessment and record their type and audience.
• Receipt. Keep a stable operation key and expected revision with each guarded action.
• Queue. Use Operations Overview to investigate failed tests, pending decisions and failed operations.

Define when a document is Internal and when Shared is appropriate. Agree who may upload or view each class of material and how a test’s text reference points to an attachment or external source. Keep source-system credentials and retention rules with the organization that owns them. A title alone cannot establish that an evidence file is the right version for a control test.

For operations, agree the caller’s stable key and the expected revision policy. A retry after a timeout should first inspect the earlier receipt. If the result is Failed or needs review, the team should investigate the failure reason and effect references before attempting another action. Do not classify a Pending operation as completed merely because the request was sent.

Upload a sample document to the assessment as Internal and confirm the intended reviewer can find it while an out-of-scope user cannot. Reference it from a control test and ask the reviewer to locate the same evidence. Then submit a guarded assessment action with a known operation key and revision. If the response is uncertain, inspect the receipt before retrying.

Use a failed receipt to rehearse the exception queue. The owner should identify the action, expected revision, reason and linked assessment before resolving the issue. The reviewer should be able to distinguish a failed operation from a failed control test and a pending review decision. Each requires a different next step even when they appear together in Operations Overview.

• Failed operation queue — Inspect failed and needs-review receipts with their reasons.
• Control test exceptions — See failed and inconclusive tests that require evidence review.
• Assessments in review — Follow assessment decisions waiting for judgment.

Follow evidence to review and read the integration boundaries.