Signals
What imminence, onset, peak, end, edges, the display signals and the subject read mean, how sure each is, and what none of them are.
orgasm.dev sends two kinds of signal. Imminence looks ahead: how likely orgasm is to begin soon. Orgasm calls look back: an onset, a peak or an end that has just happened. From the two, orgasm.dev also counts each edge, an approach that receded. A live session also describes what the voice, the body and the face are doing, for a display. Your product decides what to do with any of them; presets are worked examples.
Imminence
imminence.updated arrives about once a second while the face is analysed.
| Field | Meaning |
|---|---|
p30 | Probability that the next orgasm begins within 30 seconds, given that it has not begun yet |
p60 | The same over 60 seconds; never lower than p30 |
logit30, logit60 | The same probabilities as logits, to combine with a prior of your own |
featuresPresent | Share of the model's inputs available this second |
faceVisible, baselineReady | Whether the reading rests on a tracked face and on the person's own baseline |
stimulationAware | Whether it accounts for time under stimulation you reported |
recentCalls | The session's last orgasm calls, repeated so a missed call is seen within a second |
"Begins" means the onset for a woman and the peak for a man.
Read it as a probability over a horizon, not a countdown. A p30 of 0.6 does not mean "in 18 seconds"; it means the model estimates that orgasm is more likely than not to begin within the next 30 seconds. Compare it with thresholds you tune for your experience and for the person, rather than reading the number as exact. The reading is null until the person's resting baseline is in, about a minute after their face first appears, and whenever the face is out of view.
Imminence from the face alone does not know how long the person has been stimulated. If your product controls stimulation, report it with reportStimulation, and imminence takes time under stimulation into account.
Imminence is currently more informative for men than for women. For women, combine it with onset and end.
Orgasm calls
| Event | Called by | Applies to | Needs |
|---|---|---|---|
orgasm.onset | onset_end | Women | Face and microphone |
orgasm.end | onset_end | Women | Face and microphone |
orgasm.peak | peak | Men | Face and microphone |
orgasm.end | face_end | Men, after a peak | Face |
Each call names a moment (eventAtS) and says when the detector was sure enough to call it (calledAtS). The difference, lagS, is typically a few seconds: a call tells you what happened, not what is about to. To act at a moment, act on imminence; to confirm what happened, act on calls.
orgasmIndex counts orgasms in the session from 1; the onset and end of the same orgasm share it, as do a man's peak and the end read from his face. score and threshold are the detector's own: a score at or above the threshold made the call.
orgasm.end also says whether the orgasm was ruined: your product reported stimulation off at the point of no return (p30 at 0.75 or above) within the 30 seconds before it began. A recording takes no stimulation reports, so its orgasms are never ruined.
Edges
edge.completed arrives when an approach recedes: p30 reached 0.6 and fell back below 0.3 with no orgasm called in between, the edge preset's back-off and resume levels. orgasm.dev counts it on its side, numbers it (edgeIndex), and says when the approach started, how high it went (peakP30) and how long it lasted. Without the microphone no orgasm can be called, so every approach that recedes is an edge. In live mode an edge is charged half a credit (Credits and billing).
Signals for a display
signals.updated arrives with each imminence reading of a live session. It describes what the voice, the body and the face are doing, so a heads-up display can show more than a probability. None of it is a call, and none of it is charged. It is only streamed: webhooks don't carry it, and recordings don't have it.
| Field | Meaning | Needs |
|---|---|---|
vocalizationsPerMin | Vocalizations a minute | Microphone |
loudnessAboveBaselineDb | How much louder the voice is than at the person's baseline, in decibels | Microphone |
contractionsPerMin | Pelvic floor contractions a minute | Body view |
movement | How still the body is: settled, shifting or unsettled | Body view |
faceRegions | How far the brows, eyes, cheeks, nose, lips, mouth corners and jaw have each moved from the person's own resting state, from 0 to 1: each the largest of its expression channels | Face |
face | The face's 24 expression channels (expression, each 0 at the person's rest to 1 for a full movement) and how far the head has turned from its resting pose (head: yawDeg, pitchDeg, rollDeg, as someone facing them sees it), for a display that draws the face | Face |
Each field is null while its input is absent or still calibrating, so show only the fields that have a value. To act, act on imminence and the calls; these describe the moment.
The channels say how the face moves, not what it looks like: drawn on a generic face, as the HUD's face part does, they show the person's expression without their features. A display can read them five times a second as face frames, which also carry the head as the camera sees it, from before the baseline. A view token reads them only when made with includeFace.
The device's state
stimulation.updated is not a signal of the person's: it is what your product reported about the device it drives (on or off, its level and channels, its mode, who sets the level), merged across reports and sent to every reader, so a display can show it beside the signals. It is only streamed.
The subject read
subject.identified arrives once, about 30 seconds after the face first appears: whether it reads as a woman's or a man's, or undetermined. It decides which detectors apply. Subject explains how, and how to treat it.
Confidence
Every signal carries confidence: high, medium or low, from how complete its input was. high means the face was tracked throughout and every input the signal uses was present; low means degraded input, or a detector that ran while the subject was undetermined. It describes the input, not a calibrated probability that the call is right.
What signals are not
- Not proof. Detectors make false calls and miss real ones. Do not treat a call as evidence about a person, and do not attach consequences to one that the person has not agreed to in advance.
- Not a medical measurement. Nothing here diagnoses or monitors a condition.
- Not identity. No signal identifies who a person is, and the subject read is not a statement about anyone's sex or gender.
Credits and billing
What live sessions are charged for and how each charge is counted, where charges show up, what happens at zero, what each of your users and sessions cost, reconciling with your invoices, and testing it in the sandbox.
Inputs
The face is the minimum. What the microphone, a body view and stimulation reports add, and what happens when an input is missing.