How Flowo's planner works

Flowo uses a deterministic scheduling engine for routine planning. Optional generative tools are separate and run only when a user invokes them.

Inputs

A user supplies tasks with deadlines, estimated durations, and priorities plus fixed events, habits, sleep, meals, rest, category windows, productive hours, and available days. The quality of the result depends on those inputs.

Transactional planning

The engine evaluates independent in-memory timelines rather than mutating the source during a pass. It evaluates ideal quota duration, minimum quota duration, and only then a permitted compression retry. Candidate slots are scored from structured factors including fit, productive-hours overlap, previous allocations, and stability.

Auditable result

The result contains task and quota allocations plus status, lateness, compression, placement failures, quota shortfalls, and pinned-conflict evidence. Placement context can record why a selected slot won over a rejected candidate.

Current boundary

The everyday flow currently applies allocations and then exposes placement context for inspection and editing. A universal preview-and-confirm step is proposed product and research work, not a shipped feature.

Evidence boundary

Cognitive offloading and implementation-intention research inform the design rationale, but they do not establish that Flowo improves ADHD symptoms, executive function, task initiation, or completion. Flowo is a planning tool, not a medical device or treatment.