The spreadsheet is the prototype — three work lanes and an AI-planned schedule

One more Day 008 morning note before I start the work: the way I manage multiple projects is becoming an app idea of its own.

Right now the prototype is a spreadsheet. The screenshot shows the schedule as repeating color-coded rows: 15 minutes of ACF work, 15 minutes of client work, then 10 minutes on a side app. After that, the cycle starts again.

For today, the client lane is mainly PrintFetti. The ACF lane is the Lead System and the business work around it. The 10-minute side-app lane is the reusable Rails + React + React Native boilerplate. That third block is not supposed to mean “take a break.” It is a controlled change of context where I can keep a longer-term foundation moving without letting it take over client or business priorities. Real breaks still need their own place in the schedule.

I want to eventually add a work and Pomodoro tracker to the backlog that replaces this manual sheet with something designed around how I actually work.

What the digital version should track

• The active project lane, task, timer and intended outcome for each session.
• The repeating 15 / 15 / 10 rhythm, while allowing the timing to change when the work needs a longer block.
• Planned time versus actual time, what was completed, what interrupted the block and what carries forward.
• Separate rest breaks, so a side-project session is never mistaken for recovery time.
• A clean history that can become proof of work and help draft an honest Daily Build later.

AI could help plan the schedule from current priorities, deadlines and unfinished work. Before a block, it could suggest the smallest useful task that fits the available time. When a session runs long or gets blocked, it could re-plan the remaining cycles instead of making me rebuild the spreadsheet. Over time it could also show whether 15-minute switching is helping or whether the context switching is costing more than it saves.

The important boundary is that AI would advise and adapt, not quietly decide what matters. I should still approve the priorities and be able to override the schedule at any point.

This is a backlog product idea, not another app to build today. Today the spreadsheet is enough. The job now is to follow the rhythm: client work, ACF work, a small boilerplate block, then repeat—and record what actually gets finished.