Two types, one fundamental difference
The Chastity Tracker offers two ways to govern an orgasm, and the difference between them is the entire point.
A directive is an obligation. The keyholder orders an orgasm that must happen within a time window. Not happening is not a consequence-free option.
An opportunity is a permission. The keyholder opens a window in which an orgasm is allowed. The sub may, but doesn't have to. If the window passes unused, nothing further happens.
It sounds like a small nuance, but it's two completely different experiences. Permission releases something. A directive takes away the choice, in both directions.
The time window and the allowed type
Both types come with a time window: a start and an end. In between, the requirement is active.
On top of that, you can specify which type of orgasm is allowed. So the keyholder determines not only whether and when, but also how. That makes the requirement precise and takes the guesswork away from the sub. What isn't explicitly allowed is not part of the requirement.
How fulfillment is detected
The sub logs an orgasm as an entry in the tracker. If that entry falls within the time window of an open requirement and matches the allowed type, the system automatically marks the requirement as fulfilled. No separate confirmation is needed, no manual reconciliation by the keyholder.
This keeps the mechanism light. The sub does what was directed or allowed, records it, and the rest happens on its own.
When a directive lapses
This is where the two types part ways for good.
If an opportunity passes unused, there are no consequences. A permission you don't take is simply a permission not taken.
If a directive lapses without a matching entry, it counts as unfulfilled and lands in the offense book. Important: it lands there as a detected offense, not as an automatic punishment. What follows is decided by the keyholder later (more on that in the offense-book article). The system only reports that the obligation wasn't met.
Why this separation makes sense
Many dynamics thrive on the fact that not every concession carries the same weight. An opportunity is a gift: generous, without pressure. A directive is an act of leadership: it removes the decision from the sub, which some find relieving and others find challenging.
By keeping both cleanly apart, the tracker lets a keyholder deliberately shape the experience he wants to create right now. A relaxed phase with opportunities. A tight phase with directives. Or a mix that shifts over weeks.
Consent is the prerequisite, not the garnish
A directive that can land in the offense book is only fair if it was clear beforehand that it is an obligation. That is exactly why both partners must understand the difference between directive and opportunity before the first requirement is ever set.
Talk about realistic time windows. A directive that falls inside a 12-hour shift isn't leadership, it's a trap. Talk about exceptions too: illness, stress, bad days. The tracker reflects your agreements; it doesn't replace them. The best technology is useless without the conversation before and after.
Data and operation
Run as your own Docker container, you keep all these entries under your own control. Through the free portal they run on trublue's server, a friendship service with no guarantees. Both remain permanently free.