The Kensora Framework

The problem: snapshots of a continuous life

Mental and emotional wellbeing is continuous. The systems we use to care for it are episodic.

The standard of care for someone managing a mood condition is a self-report conversation with a clinician every several weeks. Between appointments, the richest record of how a person is actually doing, their sleep, their movement, their social contact, their writing, the shape of their days, goes largely unread. The person living that life often can't see their own drift either. Self-perception is the first thing that bends when state changes. In my own records, the behavioral signals of an approaching episode are visible weeks before anyone, including me, named what was happening.

Three structural gaps follow from this:

The data gap. The signals that describe a person's state already exist, scattered across devices and apps and journals. Nothing brings them together in service of the person who generated them.

The baseline gap. Health tools compare you to population averages. But a resting heart rate, a sleep duration, or a social pattern only means something against your own stable state. The reference point that matters is you, not the average.

The posture gap. Most technology in this space is built to maximize engagement. It mirrors you. It gives you more of whatever you bring it. For someone whose state is drifting, an amplifying mirror is not neutral. I lived the version of this where a conversational AI fed an escalating state instead of questioning it. The posture a companion takes, whether it amplifies or steadies, is a design decision, and almost everything on the market today makes that decision in the wrong direction by default.

The posture: friction and fuel

The framework's most important design commitment concerns how an AI companion should behave, because this is where I have the most direct evidence of what goes wrong.

A person's state drifts in two broad directions. Sometimes you're climbing: energy rising, ideas accelerating, sleep shortening, scope expanding. Sometimes you're stalling: energy flattening, initiative draining, small tasks becoming immovable. Most people experience mild versions of both. Some of us experience severe versions.

A useful companion behaves differently in each direction. Friction when you're climbing, fuel when you're stalling.

Friction means slowing down rather than speeding up. Asking for evidence rather than supplying enthusiasm. Noticing when the third grand idea in an hour deserves a question instead of a fourth. An engagement-maximizing product can't do this, because friction reduces engagement. Kensora is built to do it on purpose.

Fuel means the opposite mode. When the record shows the days going gray, the companion's job is the small, concrete nudge. Not a lecture, not an alarm. The next achievable step, offered gently.

Two principles make this posture trustworthy rather than presumptuous:

Your baseline, not a population's. Everything is read against your own stable patterns, established over time. The system never tells you that you deviate from an average. At most it shows you that you're deviating from yourself, and shows you the data behind that observation.

Evidence, never a black box. Whenever Kensora raises something, it cites the data it's looking at. The user can always see why. A companion that asks you to slow down has to earn that request transparently, every time.

This is also where the framework's boundary sits. Kensora applies friction and fuel as a perception and reflection mechanism. It does not detect, diagnose, or predict any clinical condition, and the published research is honest that prediction in this field remains an open problem. The framework doesn't depend on prediction. A person who can see their own drift clearly, against their own baseline, with their own people close by, is better equipped regardless of whether any algorithm ever crosses a clinical threshold.

Privacy as architecture

A system that holds a person's reflections, rhythms, and relationships holds the most sensitive record of their life. The framework treats privacy as an architectural property, not a policy promise.

Your data is yours. It stays that way. No ads, no sale of data, no attention economy.

Minimum data. Kensora collects the minimum needed to be useful, not everything it could. Capture breadth is the user's choice, made with the costs visible.

Less screen, not more. Kensora is designed to reduce screen time, not grow it. The product succeeds when you check it briefly and then go live your day. This follows directly from the friction-and-fuel posture: a tool built to steady a person cannot simultaneously be built to maximize their time in an app.

Life first. The governing principle above every other consideration in Kensora's design is the preservation, support, and dignity of human life. Where any product decision trades off against that principle, the principle wins.