← Work · Case 06
In developmentWeb & app engineering · Web app

A daily-focus app

Capture a reminder in one gesture. See the day as an editorial page.

StatusIn development
TypeWeb app
RoleConcept, design and build, with AI agents

01 · Problem

Problem

Reminder apps are built around lists, not attention. By noon the list is longer than the day.

02 · Approach

Approach

Instant capture first, sorting later. The home screen is an editorial "focus of the day": a few things, in order, readable at a glance. The app ships in phases, each one behind its own activation gate.

03 · Architecture

Architecture

captureSOURCEcomposerSTEP 01focus of thedaySTEP 02phase gateHUMAN GATEreleaseOUTPUTSOURCE → PROPOSAL │ HUMAN GATE │ INSPECTABLE OUTPUTcaptureSOURCEcomposerSTEP 01focus of the daySTEP 02phase gateHUMAN GATEreleaseOUTPUT
Sanitized architecture · roles and decisions, never real data.

04 · Guarantees

Guarantees

  1. 01Each phase ships behind an explicit activation gate.
  2. 02Dashboard contracts are covered by tests, responsive layouts included.
  3. 03Sync is exercised with synthetic probes before it touches real data.

05 · Stack & decisions

Stack & decisions

ReactThe capture-first interface and the editorial dashboard.
PythonThe backend and the sync layer.
TestsContract and responsiveness tests on every change to the dashboard.

06 · Proof

Proof

Daily focus · commit history excerptlog · authentic, sanitized
  1. feat: add immediate reminder capture
  2. feat: add progressive reminder composer
  3. feat: build editorial daily focus dashboard
  4. fix: harden editorial dashboard contracts
  5. test: cover editorial redesign responsiveness
  6. feat: expose guarded synthetic sync probes
  7. docs: record phase 1C activation gate

Excerpt from the real system, translated and sanitized: no names, identifiers or data.

Next case · 01One working memory, many agents