Follow-on tasks

An autonomous workflow can use one operation's result as the input to another. The handoff carries Standard Proof so the receiving agent can check the evidence before relying on the result.

Configure the receiving step

1. Identify the result and the evidence the next operation requires.
2. Verify that evidence against accepted references and policy.
3. Apply the receiving step's acceptance rules to the result.
4. Confirm authority to use that result and request the next operation.

Receiving a verified result does not grant access to the original inputs. A follow-on operation needs authority for any additional resources or disclosure.

Example: validation to release

A verification operation returns test and scanner findings bound to a candidate artifact. The release agent verifies the evidence and confirms that the findings satisfy the release policy. It then requests an authorized release of the same artifact.

If the evidence is invalid, the handoff is rejected. If the evidence is valid but the findings fail policy, the candidate returns to remediation. A newly produced artifact needs evidence for its own checks.

Preserve the evidence boundary

Keep the upstream result and evidence references when the supported integration provides them. Claim a linked execution history only for relationships actually recorded and checked. A chain of accepted records does not establish the truth of unverified inputs or the correctness of every business decision.

Each agent may use a different workflow or belong to a different owner. The verification and authority requirements apply at each handoff.