Short reads on how Kept works, from setup to safety.
A task moves through a small set of states. A Dom assigns one directly, or a Sub proposes one, if the Dom has turned on task requests, for the Dom to approve or reject. Once assigned, a Sub acknowledges it, works it, and either completes it or reports it failed. A Duration-type task adds a running timer: starting it moves the task to in progress, and stopping the timer without submitting proof yet leaves it awaiting proof rather than marking it done outright.
A task can require proof, a photo, a note, a feed post, before it counts as complete, or require verification, in which case a submitted attempt sits pending until the Dom reviews it and accepts or rejects it rather than completing on submission. A Dom can also override a task's outcome directly, or grant leniency on one that was missed.
See "A task or chastity action didn't go through: what to check" for the specific reasons an assignment gets blocked: hard limits, blackout windows, revoked consent, and the rest.