Software release verification
A separate example: validate a candidate artifact with approved checks, verify the findings and enforce deployment policy.
A separate example: validate a candidate artifact with approved checks, verify the findings and enforce deployment policy.
Example · Software release verification
A coding agent submits a candidate artifact. The release owner accepts the validation function and required references; a release integration receives the permitted report, verifies Standard Proof and applies its deployment policy to that exact artifact.
This is a separate design example from Conversation analytics. release-checks is an illustrative function name. No complete release-checks project, profile, fixtures or candidate archive is supplied by this guide, and the function is not preinstalled in your account. Agree the setup and supported execution route before implementing it.
The approved function validates a candidate manifest, required file paths and SHA-256 digests against accepted references. It computes from declared inputs; it does not launch candidate binaries or run an arbitrary Linux test suite. Required references are bound inputs under the release owner’s authority.
A report can contain passing and failing checks:
{
"artifact": "service-api-2.14.0.tar.gz",
"checks": [
{ "id": "manifest-format", "outcome": "pass" },
{ "id": "file-digests", "outcome": "pass" },
{ "id": "required-files", "outcome": "fail" }
]
}This is illustrative output, not a retained execution. Your accepted workload defines the actual report schema and required checks.
Implement the workload through the restricted Wasm interface. Prepare the complete project, operation profile, input fixtures and expected results; build and test its exact bytes before publication.
The release owner authorizes the candidate, required references, workload and report recipient. The coding agent cannot replace the checks or use evidence for one candidate to authorize another. Connected-source inputs require their own approved selection and per-operation authority.
The coding agent requests the published function through the configured transport. Hosted requests return metadata; the release integration retrieves and verifies the permitted result on its delivery path. An installed recipient receives verified bytes through the CLI or SDK. See Receiving results in the SDK.
The current hosted continuation limit described in Connect also applies to this example. A submitted or approved request is not evidence of execution.
Verify evidence for the accepted function, references, candidate and report. Then evaluate the check outcomes and enforce deployment authority. Valid evidence can accompany failed checks; it does not prove the software has no defects or grant permission to deploy.
A changed candidate needs its own applicable checks and authority. Keep the candidate digest, verified report and deployment decision bound together. See Verification checks.