A trigger is a claim about how often
Saying that something sets you off is a claim about frequency. Not once, not memorably, but reliably enough that the next time is worth expecting. That makes it the kind of claim a count can settle, which is unusual for anything in this territory.
The counting almost never happens. What happens instead is that one vivid instance becomes the answer, and every instance afterwards gets read as confirmation of it.
The denominator problem
Suppose work shows up in your log on four of your worst days this month. That looks conclusive right up until you notice work also shows up on twenty six other days. The tag isn't telling you anything. It's just common.
An honest answer needs both numbers: how often the thing lands alongside a rough day, and how often it lands at all. The second number only exists if the ordinary days are logged too, and an ordinary day is exactly the kind nobody feels like recording.
It is the same reason a single bad day cannot settle anything. One day supplies one instance of everything in it, and everything in it looks equally implicated. Separation only appears once there are enough days for the common tags to blur and the uncommon ones to stand out.
What gets logged
An entry is two five-position dials, one for how the day went and one for energy, a set of tag chips for what was in the day, and a short line when a day earns one. About twenty seconds. The tags are what the statistics count. The note is what you reread later.
Nothing here asks you to write about the thing while it is happening. That request is why most trigger journals empty out. The moment worth capturing is the moment you are least able to sit down and describe it.
What the counting returns
Co-occurrence speaks most directly to this. It compares how often a tag lands next to a given level against how often it lands anywhere, and reports the difference rather than the raw tally.
Lagged correlation extends the same question backwards. Some of what set a day off was not in that day, and a check that only ever looks at one date will never find it.
This looks like a real pattern.
After days when you logged more sleep than usual, your logged energy tends to be lower about 2 days later.
Drawn from 48 pairs of days, between March and August 2026.
The example is about sleep and energy rather than about temper, but the shape is the one that matters: something first, something after, a gap in days, and a count of the pairs behind it.
How sure it is willing to be
- EmergingEarly signal. This might be a pattern, I need more to be sure.
- ProbableThis looks like a real pattern.
- StrongThis is a consistent pattern in your history.
Those three sentences are fixed. They are never rewritten to sound more or less certain, so a finding that reads as probable in month two reads exactly the same in month ten. The number of days behind it sits alongside, which is what makes an early finding legible as early.
The line this does not cross
The app reports what lines up. It never says that one thing caused another, and no wording on this site should be read that way. A tag that keeps landing next to your rough days is worth knowing about. What it means is a separate question, and it stays yours.
This is a journaling and reflection tool. It is not therapy and it is not a mental health service, and it offers no advice about what to do with anything it finds.
How long it takes depends on how often the thing occurs. A few weeks of logging is the floor. Something that happens twice a week gives the checks far more chances than something that happens twice a month, and the count on each finding shows how many chances it has had.
Life Pattern Journal is not released yet. The waiting list on the front page sends one email now to confirm the address, then two more, ever: one when the beta opens and one when it launches.