Workflow preview

What the agent will follow (tools, prompts, and workflow steps).

1. Apply the following prompt: Goal:
Ask the user for the original file they want to verify. Upload it using the File Management tool.

Inputs:
The user provides the file they want to verify — a software release, document, archive, or any artifact that has an attestation certificate.

Outputs:
A file_id from File Management after uploading the file.

Constraints:
The file must be uploaded to File Management using upload_standard before proceeding. Save the returned file_id.

Success criteria:
The file is uploaded and a file_id is returned.

2. Apply the following prompt: Goal:
Ask the user for the attestation certificate JSON file. Upload it using the File Management tool.

Inputs:
The user provides the attestation certificate JSON file they received from the attestation issuer.

Outputs:
A file_id for the attestation certificate from File Management.

Constraints:
The certificate must be a JSON file. Upload it using File Management upload_standard. Save the returned file_id as the attestation_file_id.

Success criteria:
The attestation certificate JSON is uploaded and a file_id is returned.

3. Call tool: Quantum-Safe File Attestation (Verify Attestation).

Instructions:
Call verify_attestation with the file_id from the original file upload and the attestation_file_id from the certificate upload. Report the result clearly: if accept is true, the file is verified authentic. If accept is false, list the failed_checks and explain what each failure means.

Parameters:
{"action": "verify_attestation"}

4. Apply the following prompt: Goal:
Present the verification result to the user in clear, non-technical language.

Inputs:
The verification report from the attestation tool including accept, failed_checks, manifest_sha256, and signer_public_key_hex.

Outputs:
A clear statement of whether the file is verified or not, with explanation of what was checked.

Constraints:
If accept is true, confirm the file is authentic and untampered. If accept is false, explain each failed check in plain language. Never overstate what verification means — it proves the file matches what was signed, not that the contents are safe or correct.

Success criteria:
The user understands whether their file is verified and what that means.