Claimed vs. verified

Claimed vs. verified is the distinction between a worker (human or agent) self-declaring a task done and an independent party confirming that it actually is — and today, Kanbai's task status only captures the former.

Kanbai's task status field ("To Do", "In Progress", "Review", "Completed") is a plain, self-declared dropdown: whoever is assigned a task sets it to Completed themselves, and nothing in the schema records who verified that claim, when, or whether the verifier was a different person than the claimant. This matters because a claim and a verification are genuinely different events with different failure modes — a claim can be honestly wrong, optimistically premature, or (for an autonomous agent) simply mistaken about its own output, and none of those get caught by a status field that only the claimant controls. Kanbai's own design packet is explicit that the terminal success state should be independently verified work, not a claim, and that faking the distinction — for instance by relabeling "Completed" to "Verified" in the UI without a real verification event behind it — would be worse than being honest about the gap. So today, `lib/status-adapter.ts`'s `deriveTaskDisplayStatus` is a deliberate, honest passthrough: it shows exactly what's stored, with `isIndependentlyVerified` hardcoded to false, because there is nothing in the schema yet to make it true. A real verification event (a verifier distinct from the claimant, with a timestamp) is a specified, not-yet-built follow-on.