← Work

AI engineer · In progress

Can a tool read mental state without the data ever leaving the machine?

FlowState — On-Device Cognitive Load Estimation

Estimates cognitive load and burnout risk from behavioural telemetry, with every model running locally. Nothing leaves the machine.

Role
AI engineer
Built with
Python · Behavioural Telemetry · On-Device ML · Privacy Engineering
FlowState, cover image

A tool that estimates cognitive load and burnout risk from behavioural telemetry, with every model running locally on the user’s machine. Nothing leaves the device. That constraint is the point of the project: the signals most useful for inferring mental state are precisely the ones users should be most reluctant to upload, so the architecture removes the upload entirely rather than promising to handle it responsibly.

Problem

Inferring cognitive state requires fine-grained behavioural data — activity patterns, timing, interaction rhythms. That data is intimate, and the conventional architecture of shipping it to a server for scoring asks the user to trust a promise. A privacy policy is not an architectural guarantee.

Approach

Models run entirely in user space on the local machine, so the telemetry never crosses the network and there is no server-side store to breach or subpoena. This costs the things centralized training would give you: no cross-user population baseline, no model improvement from aggregate data, and inference bounded by whatever hardware the user happens to have. The design accepts all three, on the view that a tool for monitoring mental state is not one users should have to take on trust. This is an in-progress prototype and has not been validated against any clinical or psychometric measure of cognitive load.

Screens

Launch film · 21 seconds, with sound.
The FlowState landing screen, headed “Work in Flow. Not in Burnout.”, above a product preview showing a task queue, an energy level chart, work velocity and AI suggestions
The product surface: task queue, current energy level, and the suggestions derived from them.
A three-step explanation: Monitor tracks task completion speed, idle time, error rate and keystroke cadence; Analyze calculates a work velocity score and cognitive load index; Orchestrate suggests breaks and reschedules work
The three stages, and the behavioural signals each one reads. All of it runs on the machine that produced the signals.
The analytics screen: a weekly focus heatmap by time slot, alongside burnout risk, average focus session length, energy recovery and productivity score
The weekly view. A heatmap of deep work by time slot is the output that made the estimate legible to a user.
The closing screen, headed “Stop Managing Tasks. Start Managing Energy.”

Watch the walkthrough on YouTube Walkthrough of the on-device estimator and the weekly view.