Verification

“The agent says it’s done” and “it’s done” are different claims. Verification is CubeDot’s way of closing that gap: a Verifier agent checks a functionality against its acceptance criteria and records the result, so the PM Hub can show a verified checkmark that actually means something.

Off by default

Verification is a single on/off switch, and it ships off. Turn it on per repo with:

cubedot config set verify on

Why off? Verification costs real time on every functionality. For a prototype, “the human looked at it” is often enough; cubedot done is already a deliberate human gate. Flip it on when correctness matters more than pace. The setting is per checkout, so one developer can verify while a teammate on the same project builds without it.

What changes when it’s on

• cubedot verify-scope <FN> tells the Verifier exactly what to check for that functionality: the acceptance criteria, the relevant spec context, the conventions.
• The Verifier does the checking and the result is recorded with cubedot ingest <FN>.
• The PM Hub shows the functionality as verified with a receipt of what was checked.

With verification off, cubedot report-scope <FN> still produces a build report, a record of what was done, but never a verdict. The PM Hub shows such work as untested rather than pretending it was checked.

Honesty by design

A verified badge only ever comes from a verifier that ran. Marking something done doesn’t create one, and nothing backfills them. If the board shows untested work, that’s the truth, and it’s fixable: turn verification on and re-run the pass for the functionalities you care about.

Verification is available on Trial and Pro plans (see Plans).