Requirements

What a site needs before task verification is trustworthy. Moon Festival Physical AI observes and records; it does not command the robot.

Hosted verification service

A deployed Moon Festival Physical AI site your team can reach over HTTPS.
Acceptance criteria published for each skill you want judged (see Criteria).
At least one operator account to adjudicate attempts when the outcome is unclear or for pilot sign-off.
Signed shift records when you need a customer-facing artifact (see Shift records).

A wrist or tool-mounted force/torque sensor streaming during each attempt (contact evidence).
A small edge recorder on the cell network: records each attempt locally, then syncs to the verifier (read-only toward the robot — no motion commands).
Network path from the cell to the verifier ingest endpoint (outbound HTTPS only from the cell; storage keys stay on the server).
Optional: before/after camera stills per attempt for visual cross-check when force alone is ambiguous.

Software can run in a lab with replay data. Production sign-off requires real attempts on your equipment:

Probe the sensor before each session.
Record at least 20 mixed pass/fail attempts for one skill.
A person labels each attempt; machine agreement should reach at least 85% or failures must be explainable (criteria, calibration).
Episode chain verifies; provenance complete on every attempt.
Generate a signed shift record and download the customer export.

Your administrator configures the site and cell recorder. Day-to-day users review episodes, criteria, and shift records from this interface.