VERIFICATION · PUBLISHED
Verifying Autonomous Robot Tasks: Evidence, Computation, and Settlement
A technical explanation of job-specific physical evidence, canonical signed submissions, verification decisions, and explicit settlement actions.
PRIMARY SOURCE · @ontosworld/verify package ↗Define proof before the task
A payment record or robot status message cannot independently prove that a physical job met its completion criteria. Verification begins by committing the required evidence when the job is created.
The current standard schema can require GPS, a camera hash, QR or NFC data, motion count, timestamps, and a device signature. A new evidence field requires a versioned schema and matching verifier implementation; arbitrary custom data is not implicitly evaluated.
Prepare a canonical evidence envelope
Evidence is associated with the job and machine, validated against requirements, normalized into a canonical payload, hashed, and signed by the submitting account. Hardware collectors can be composed without allowing one provider to silently overwrite another.
Device attestation can be connected through platform or hardware-backed providers. Development attestation exists for local testing, but a hardened service must reject it and verify native statements against vendor requirements.
Submission and computation
The SDK stores immutable evidence through a configured service, commits its hashes, and can trigger a SEDA verification workflow. Applications poll or retrieve an approved or rejected result through stable developer interfaces.
Browser clients must not receive evidence upload credentials or project secrets. An application-owned server route exchanges credentials for narrowly scoped access and forwards evidence to the managed service.
Settlement remains explicit
A verification result can support payment release or a rejection path, but settlement is not an invisible side effect. Release, dispute, cancellation, and timeout refund are explicit application actions with wallet and chain requirements.
The published package implements this workflow for its documented Peaq and SEDA integration boundary. Deployments still require configured identity, wallet, chain, evidence, attestation, and verifier infrastructure.
What this note is based on
This engineering note summarizes the public implementation and documentation at the source below. It does not add unreported performance results or treat a roadmap objective as a validated capability.
@ontosworld/verify package ↗