Imposing a punishment

Created from Punishments → New punishment, or from the conversation with «Tools» → Impose punishment.

What you define

To whom — only bonded subs who have set their maximum accepted severity.

Title and reason — the reason is mandatory. You can choose a specific reason and explain it, or the «Because I can» option if that is the agreed dynamic. What you cannot do is leave it empty.

Type and subtype:

• Physical — discipline, physical restriction.
• Psychological — humiliation, degrading task, public confession.
• Control — forced check-in, app restriction.

Severity — capped by the ceiling that sub has set. You cannot exceed it.

Completion deadline — by when.

Recurrence — One-off, Daily or Weekly, with a daily cut-off time, days of the week and «Repeat until». A template is created and instances generate up to a week ahead; each is completed separately. It can be stopped at any time.

Off-catalogue — mark it and the punishment is not compulsory: the sub can refuse with no consequences and, if he completes it, receives the points you set.

Save as template — assigns it to nobody; it is stored for reuse, for example as the punishment if not completed on a task.

The cycle

Pending → Active → Proof sent → Completed

With the exits Missed, Cancelled and Refused.

The sub describes how he completed it and presses «Send proof». You can accept it or reject the proof. Proof is timestamped.

Clemency

If the sub has accumulated points, he can ask for clemency on an active punishment. You decide: Grant or Deny. If he accepted the punishment when he could have refused, he cannot ask — the app flags it as no clemency.

A note on using it

A punishment exists to close a breach, not to feed a loop. The platform is designed under Just Culture: consequences that are proportionate, with a route back, aimed at next time going right. A history that is all punishments and no recovery does not describe a sub who fails: it describes a dynamic that is not working.