Skip to main content
Meadow Arc

Back to all posts

Why I am building Caligo Relief

Published on by Meadow Arc · 3 min read

I am building Caligo Relief because I kept looking for a tool that would help me stay oriented, and I could not find one.

There are plenty of apps around routines, health, recovery, and symptoms. I tried some of them. A few were thoughtful. Many were polished. None of them really fit the shape of what I needed when things were inconsistent and hard to read.

They usually leaned too far in one direction. Too clinical. Too data-heavy. Too generic. Or simply too demanding for the kinds of days when my capacity was already low.

The uncertainty was harder than the symptoms

What wore me down was not just pain or nervous system sensitivity by itself.

It was the uncertainty around it.

Not knowing what was helping. Not knowing what had changed. Not knowing whether a better day meant I was moving forward or whether a rough day meant I was back at the beginning.

That kind of inconsistency can quietly erode trust in your own sense of things. You start second-guessing small decisions. You overdo it on one day, pull back too far on the next, and lose the thread of what is actually happening.

I needed more than another tracker

I did not just need a tracker.

I needed something that could help me:

  • notice patterns without obsessing over them
  • return to a few useful actions
  • see progress that might be too slow to feel day to day
  • and reduce the background noise of constant re-evaluation

In other words, I wanted something that could hold the process lightly.

Not something that promised a fix. Not something that turned everything into a project. Just something calm enough to come back to and clear enough to help me keep going.

The product has to stay calm on low-capacity days

Caligo Relief began as a tool for myself.

A place to log symptoms without overcomplicating them. A place to keep a small amount of structure around activities that seem to help. A place to look back and see a little more than whatever today happens to feel like.

That is still the center of it. The product needs to stay usable on the days when a person has the least patience for one more demanding system.

I am not trying to build the definitive app for pain or recovery. I am trying to build something more modest and, I think, more useful:

  • supportive without becoming overbearing
  • simple enough to use on low-capacity days
  • honest about slow progress
  • and steady enough to make the process feel a little less confusing

It is still evolving, which feels appropriate. This is the kind of product that probably has to be built close to real life, not above it.

That is why I am making it.