JourneyM8 LAB

We give time and space for stories to meet.

JourneyM8 LAB creates apps, writing and experiences shaped by attention — and begun as acts of service.

The thread

Everything here began the same way.

Someone noticed something that was already there, and was not being served. A taste with no account of where it came from. A month whose shape only became visible in hindsight. A place that mattered to someone, living only in their own memory.

None of it was invented. It was already present and not yet legible — and the work, in each case, was to make it so without flattening it, overstating it, or claiming more certainty than the evidence supports.

That is the whole method. What follows is the evidence for it.

Walk the whole body of work in the Atlas →

What we build

Three apps, one practice.

JourneyM8

Whisky · iOS & watchOS · live on the App Store

What we noticed: Whisky is experienced through memory, perception, place and human connection — but nothing made the journey from field to glass legible. You could learn a thousand tasting adjectives and still not know why a whisky is the way it is.
Who was underserved: Anyone who had moved past "do I like this" and reached "why is this like this" — and found only scores, wheels and marketing copy waiting for them.
What we built: A knowledge graph connecting production decisions to physical mechanisms to sensory outcome, a twelve-axis Spirit Map, a Flavour Map of over six hundred descriptors organised by lived scenes rather than taxonomy, and an Academy that teaches the causes rather than the labels.
Where to find it: journeym8.com · 633 distillery pages

LUMA

PMDD tracking and support · iOS · live on the App Store

What we noticed: A daughter asked her father for a template in Apple Notes, to track the twelve days each month when her PMDD symptoms are at their worst. Within minutes of reading, it was clear it could not be a Notes template.
Who was underserved: She had tried other apps. They were built for fertility tracking and dressed accordingly, and none of that meets a woman in the worst week of her month deciding whether she can get to work. One had taken weeks of her own symptoms and put a paywall in front of her own record — at exactly the moment she was finally building the thing a clinician needs.
What we built: Everything you track is free and stays free. There is no account, no server, and no networking code in the app at all — nothing leaves the phone, ever. It still learns her cycle, names the phase she is in, and helps her see the hard week coming before it arrives. The thinking happens on the device, so there is nothing to hand over.
Where to find it: journeym8.com/luma · App Store

From the working notes — Language & Tone

Affirming without diminishing
What we avoid · what we use instead
Containment language
Presence and witnessing — being seen without interference

Deciding which words diminish a person, before deciding what the screen looks like.

CapLoc

Capture and clarity · iOS & macOS

What we noticed

Productivity tools treat forgetting as the problem. But the work that matters is rarely forgotten — it is displaced, while you stay busy, finish ten other things, and feel productive.

And something quieter, arriving separately: a practice between two friends, an ocean apart, of leaving a call open — not to talk, but to be present. Presence at distance turns out to be a thing software can hold, and almost nothing tries to. That second observation is where Witness comes from.

Who was underserved

Anyone who knows exactly which piece of work would make the difference and keeps choosing around it — usually on their own.

What we built

A calm home for everything on your mind you cannot deal with right now, so the things that matter stop quietly slipping away. And Witness: you can invite one person you trust to see what is drifting — not to check up on you, just so you are not carrying it alone.

Where to find it

journeym8.com/caploc · App Store

Why CapLoc exists

What if the problem is not forgetting the work, but repeatedly choosing around it?

In Ott Bryan’s words

CapLoc began with two ideas that arrived from very different directions.

In one video, a presenter spoke about reclaiming effort and time—taking capacity consumed by the wrong work and returning it to the pool of what remains possible. In another, an emergency-room doctor described the language of triage: how urgency is assessed, communicated and directed when everything cannot receive attention at once.

The two messages began a conversation with each other. One was about capacity. The other was about consequence. Together, they gave shape to a question:

How do we decide what deserves our attention before busyness makes the decision for us?

My first note was simple: I want to develop an app that solves this problem.

At the time, I did not have one dependable place to hold ideas, project goals and the decisions attached to them. A notebook worked until it was somewhere else. A nearby piece of paper worked until it disappeared. Apple Notes held everything, but that became part of the problem: the thought was technically still there, buried beneath hundreds of titles I could no longer remember.

Most productivity systems treat forgetting as the central problem. You have something to do, so you record it. The application reminds you. You complete it. A box receives a check mark.

But the harder problem is often not forgetting.

You know what matters. You know which piece of work could make the greatest difference. Yet something easier, more enjoyable, more immediate or less consequential takes its place. You remain busy. You may complete ten other things. You may even feel productive.

The important work has not been forgotten. It has been displaced.

CapLoc emerged from the idea that this displacement should remain visible before activity can disguise it as progress. It preserves not only the work itself, but the decision you made about why it mattered. If that decision later changes, CapLoc creates room to notice:

Did reality change?

Did the work become less important?

Am I blocked?

Or am I quietly choosing around something I do not want to face?

It would be easy to call CapLoc a task manager, except it has no field for a due date. It sits somewhere between productivity and organization, but neither name quite reaches the idea beneath it.

CapLoc is concerned with capacity, intention and consequence. It does not simply ask what remains unfinished.

It asks whether the work receiving your attention is still the work you meant to choose.

What we write

The writing is not the marketing for the software. It came first.

SeasonsTwelve seasons, forty-eight meditations, fifty-two weekly journals. The origin work — the twelve words the Companion Card decks take their names from.
The Books of SeasonsTwelve companion volumes. A human map — Attention, Awareness, Clarity, Permission — that rhymes with the twelve-axis Spirit Map without ever being the same thing.
The whisky booksFive published titles. Production, perception, and the ground between them.
Companion Cards624 cards across twelve decks, written to sit beside someone rather than instruct them.

What we are exploring

Open questions, not launched products.

Recorded here because pretending every idea is finished is how a studio stops being able to tell the difference.

Expression DNAWhether an exact bottle can carry an evidence-backed account of how it came to taste as it does — with what is verified, inferred and unknown kept visibly apart.
Same destination, different routeTwo whiskies that arrive at a similar place by unrelated production paths. Findable, if the graph is honest about uncertainty.
The operating engineHow one person and a set of agents can hold several bodies of work at once without any of them going quiet.
Consideration for Context: The principle is settled. The mechanism is not.We are no longer exploring whether judgment requires context. We have come to understand that a binary decision made in a contextual vacuum is not judgment at all; it is classification. What remains open is how to build the threshold before judgment: a gate capable of determining what information belongs inside the decision, what must remain outside it, and how both choices can be made visible enough to examine. Can we build a judgment space that is small enough to remain inspectable, but large enough to hold the context that changes what the evidence means?
Epistemic OSA system for managing not merely what an organization knows, but the state of its knowing. A conventional information system stores information. A database might tell you that a value is 46%. A document might say that a distillery uses a particular process. A CRM records what a customer said. An Epistemic Operating System asks another layer of questions: What is this thing we think we know? Why do we believe it? How certain are we? Where did it come from? What contradicts it? Has it been verified? What depends upon it? What don't we know yet? And what should happen when new evidence changes our understanding? That's the epistemic part. Epistemology is concerned with knowledge: what constitutes knowledge, how we acquire it, and what justifies believing something to be true.

Work with us

Licensing, clinical partnership, commissioned development, collaboration.

The knowledge graph, the Flavour Map vocabulary and the Companion Card writing all exist as licensable bodies of work. LUMA's approach — everything on the device, nothing transmitted — is available to anyone building in a field where that matters and is usually told it costs too much.

Contact

info@journeym8.com

Ott Bryan and Joe Cooper. One builds, one knows the ground the work stands on — and neither part arrives without the other.

JourneyM8 LAB is the research, writing and idea work of JourneyM8 Ltd. It holds the pre-work rather than the storefront.