Verification

Submit a revision for verification

Run the remote verifier from your repository after configuring the cloud connection. The default request identifies the repository from its origin remote and uses the current commit. The server fetches the revision and evaluates its configured gates.

node ~/.claude/skills/asondy/scripts/asondy-verify-remote.js

The relay needs access to the repository and commit. Uncommitted working-tree changes are not part of that commit; commit the intended change and make its revision available before requesting server-authoritative verification.

What the result identifies

The server generates an unsigned verification statement identifying the repository, commit and checked-content digest. Keep the statement with the corresponding revision when reviewing or sharing evidence.

The statement records what was checked. It does not provide a cryptographic signature or cover later edits.

Read the outcome

• Pass: the configured verification checks passed for the checked revision.
• Fail: one or more conditions were not satisfied; use the gate details to identify the correction.
• Error or unavailable: the verifier could not establish a result. Missing configuration, inaccessible revisions and network failures must not be treated as passes.

Keep the evidence accessible

The cloud audit flow records verification outcomes with session and trace identifiers. Audit exports support review outside the dashboard. Match the result to the commit, inspect the individual checks and rerun verification after changes.

Server verification and SDK submissions

The verifier also includes an SDK mode that submits a local diff and selected text files. That payload is client-supplied and observational. Use the default repository-and-commit path when you need the server to establish the checked revision independently.

What leaves your machine

The default path sends revision metadata and fetches code through the server’s repository access. SDK mode submits code in its payload. Verification workers use temporary job directories with cleanup after the job exits. Audit records and relay conversations are separate data flows; see Privacy and Security.