Today Is the Front Door of the System

All essays2026-05-067 mintodayproductuxoperations

What Today Is For

Today is the front door of the system.

Its job is not to show everything the database knows. Its job is to answer a narrower question: what matters now?

That is why the page is structured around:

action queue
alerts
goals due soon
events due soon
calendar
weather
habits
commitments
subscriptions

The point is not breadth. The point is compression.

The Product Bet

Most personal systems fail because they separate planning from execution too aggressively. The user can maintain a beautiful set of goals, events, notes, and commitments, but still wake up to a blank operational surface.

Today fixes that by acting as the decision layer between stored context and actual daily behavior.

What Success Looks Like

Success for Today is simple:

you open it and immediately know what needs a decision
you can distinguish urgent from merely present
you do not need to mentally join five separate parts of the system before acting

If that works, Today becomes the page that keeps the rest of the system alive.

Newer

What a Truly Agent-Agnostic Popup Architecture Needs

The concrete architecture needed to make Beacon and FleetCrown lifecycle-driven instead of Claude-driven, with a clear split between adapters, control plane, and clients.

Older

The Prompt Library Is the Interface to Repeatable Intent

Why the Prompt Library matters: it turns useful agent interactions from tribal memory into reusable operational templates.

Images as Agent Input — Why Visual Context Changes the Game

A case for adding image upload and paste support to FleetCrown's agent interface, and what it would take to do it right.

"One Button: Play and Pause the Fleet"

The end state FleetCrown is built toward — describe what you want, press play, and watch the fleet build it. Pause anytime. No forms, no supervision.

The Play Button Is the Product

One click that looks like play should be enough to have all your projects built without supervision. Why FleetCrown's autopilot became a play/pause button, and why project context had to stop being a form.