The problem with automatic punishment
A system that detects offenses itself and then punishes them itself sounds efficient. In a D/s dynamic, it's a mistake. It strips the keyholder of the role that defines him: the decision. And it treats every infraction the same, even though a slept-through alarm and a deliberate boundary crossing are not the same thing.
The Chastity Tracker takes a different path. It cleanly separates two things: detecting an offense and judging it. The software does the former. The human does the latter.
What the system detects automatically
The tracker registers a range of offenses on its own, with no one having to enter them manually:
- Unauthorized opening — the device was opened without permission in place.
- Missed or declined inspection — an inspection request expired or went unfulfilled.
- Cleaning limit exceeded — an allowed cleaning break was stretched beyond the agreed measure.
- Wrong device — a device other than the prescribed one was in use.
- Missed orgasm directive — a requirement set as an obligation went unfulfilled.
Each of these lands as an entry in the offense book. But it lands there as a finding, not as a verdict.
The judgment loop
A detected offense is, at first, just that: detected. Nothing further happens until the keyholder looks at it. He then has two paths:
- Dismiss — the offense is closed with no consequences. The alarm was slept through, there was a good reason, the day was rough. Not every finding deserves a reaction.
- Punish — the keyholder chooses a consequence and sets it.
Nothing escalates on its own. An offense the keyholder never looks at simply remains an open entry. There is no automatic transition from "detected" to "punished."
Why this separation is fair
Separating detection from judgment solves several problems at once.
It makes detection reliable and neutral. The software has no mood, forgets nothing, and makes no distinction between days when the keyholder is watching closely and days when he's busy. Every offense is treated the same: recorded.
It makes the judgment human. Context, tone, history, the shape of the day: all of that feeds into a decision an algorithm cannot make and shouldn't. The keyholder stays responsible, and responsibility can't be automated.
And it protects both sides. The sub knows nothing slips through the cracks, but also that not every trifle escalates blindly. The keyholder doesn't have to stay constantly vigilant to avoid missing something, because detection runs regardless. He can focus on what only he can do: judge.
The offense book as shared memory
Over time, the offense book becomes a chronicle of the dynamic. It reveals patterns: if missed inspections pile up, maybe the cadence is too tight. If cleaning overruns keep appearing, perhaps the agreed limits don't match daily life.
Read that way, the offense book isn't merely a register of sins but a basis for conversation. What's working, what chafes, where does a rule need adjusting? A dynamic that adapts lasts longer than one that stays rigid.
Where all this is stored
As a self-hosted Docker container, the offense book sits entirely in your hands. Through the free portal it sits on trublue's server, a friendship service with no guarantees and no data control on your part. Both routes remain permanently free.