Simulations
Friday soccer and neck pain: from separate measurements to a useful question
A synthetic account, a weekly routine and 12 independent pain readings. A closer look at what Reven detected, what it asked and what this test does not establish.
The objective
Test whether Reven could detect a possible relationship between a habitual activity and a symptom from information recorded separately, without receiving statements such as “my neck hurts more after I play soccer.”
How the case was prepared
A synthetic account was created through the usual onboarding process. The profile included neck discomfort and a soccer routine on Fridays.
We then added 12 independent responses about pain intensity, with simulated dates spread over three weeks.
| Recorded days | Neck pain |
|---|---|
| Friday, October 9 | 6/10 |
| Friday, October 16 | 7/10 |
| Friday, October 23 | 6/10 |
| Nine other recorded days | Between 1 and 3/10 |
The responses contained only pain intensity. They did not mention soccer or suggest an explanation. No games were marked as completed.
How the models handled the information
The usual capture models interpreted the responses and saved the measurements. Reven’s relationship engine then received the full context assembled by the system, including the routine and the dated observations.
In a single run, it identified that pain was higher on all three Fridays and compared those readings with the other recorded days. It opened an investigation titled, in translation:
“A pattern to clarify between soccer and neck pain”
The investigation remained pending clarification. The engine recognized that an essential fact was missing: whether the person had actually played on those days.
The question it generated
“Did you play soccer on Fridays, October 9, 16 and 23?”
It also prepared the wording to communicate that request for clarification. Sending it to the device was not part of this test.
Three distinctions that mattered
- Scheduled does not mean completed. Having soccer on the calendar does not confirm that the person played.
- Coincidence does not establish a cause. Matching dates alone cannot explain why the pain occurred.
- No measurement does not mean no pain. A day without a reading cannot be treated as symptom-free.
The engine also noted that it was still unknown whether the pain occurred before or after the game.
Why this is a step forward
This simulation showed that Reven can use a routine and independent measurements to form a hypothesis and turn it into a specific question, without needing the person to suggest the relationship first.
Relationship findings are available as context for the prediction engine, together with their uncertainties and the user’s responses. No predictions were run in this test: it evaluated the detection of the pattern and the decision to ask for clarification.