What Is Verified Done? Why a Checkbox Is Not Proof

Verified Done, defined

Verified Done is the final state of an action in Aksa. An action reaches it only when there is durable proof and the verification rule for that action has been met. It is not triggered by an AI response, and it is not triggered by a checked item in the interface.

The path to Verified Done

Aksa describes an action as a persistent workflow, not a disposable task row. Its minimum lifecycle runs from Proposed to Accepted to Running, then to Blocked or Approval Needed when something is in the way, then to Proof Submitted, and finally to Verified Done.

Each action keeps its desired outcome, owner and collaborators, current state, context, blockers, approvals, activity history and proof.

• Proposed
• Accepted
• Running
• Blocked or Approval Needed
• Proof Submitted
• Verified Done

Who verifies the proof

It depends on the action. Solo goals are private and self-verified by the owner. Some actions require approval from a peer or a mentor. In that case, submitting the action sends a review notification to the reviewer, and approval sends a verified confirmation back to the member.

Whatever the route, the rule is the same: weak or missing evidence is never upgraded into verified proof.

What Verified Done changes

Verified Done is the only state that moves things forward. Progress counts verified proof only. A streak moves only on verified proof. Weekly rank uses active streak and verified weekly claims, and Gold is earned through verified daily actions.

This keeps the numbers honest. A streak of 12 days means 12 days with proof, not 12 days of tapping.

Verified Done and AI

AI can help plan an action, suggest the next step and keep momentum. It cannot declare the action finished. Aksa keeps that boundary on purpose so that automation never inflates progress.