Episode 02 / 06
August
Document continuity
A draft, its current version and two review threads remain part of the same piece of work.
Series
Building My Own AI Operating System
From one general assistant to smaller services with clearer jobs, boundaries and ownership.
The system so far
Separate services, explicit responsibilities.
This series follows my attempt to build a personal AI operating system by starting from work I already do, rather than from one universal assistant.
August keeps documents, versions and review state together. March makes the publishing runway visible without turning it into a commitment. Friday now coordinates signals across them while each service remains responsible for its own work.
-
Jarvis
Failed attempt
A general orchestration system that began with decisions and action items before it had a recurring job.
-
August
Document continuity
A private, local review workspace for developing documents with AI while keeping versions, review state and unresolved questions visible.
-
March
Editorial runway
A view of what may be published, what is ready and where intentional gaps remain, without turning the plan into a promise.
-
Friday
Working orchestrator
The ongoing second attempt, built around noticing what may deserve attention across bounded services without replacing them.
Episodes
Notes in this series.
- Episode 01 I stopped trying to build Jarvis I started with a general AI assistant and no recurring job for it. The useful parts appeared only after I built smaller services around work I was already doing. AI and automation Software systems
- Episode 02 I built August because copy and paste was not collaboration AI could help with a document, but the work around each answer kept falling apart. I built August to keep the draft, its review state and my decisions in one place. AI and automation Teams and collaboration
- Episode 03 I built March to plan with AI without becoming a content machine I wanted a view of the publishing runway without turning empty space into pressure. March keeps the plan visible so AI can help question it while the editorial decisions remain mine. AI and automation Product decisions
- Episode 04 Why I started building Friday Friday is my second attempt at the original Jarvis ambition. It began when August and March created a concrete coordination problem between them. AI and automation Software systems
- Episode 05 Friday connects the services without owning their work A coordinating layer can compare state, explain disagreement, and direct attention without becoming the source of truth for the services it connects. AI and automation Software systems
- Episode 06 I need my AI dashboard to leave things out A useful AI dashboard should reduce the first pass over the work, not reproduce every open item. Its omissions, priorities, and explanations all need to remain inspectable. AI and automation Software systems
From the notes
A few views of the system.
Screenshots from August, March and Friday, collected as the interfaces changed across the series.
Episode 03 / 06
March
The publishing runway
Planned, published and intentionally empty slots stay visible across the coverage horizon.
Episode 04 / 06
Friday
The Morning Bridge
Signals from separate services meet in one attention queue.
Episode 05 / 06
Friday
Authority and reconciliation
Observe-only defaults and scoped writes make the ownership boundary visible.
Episode 06 / 06
Friday
Presence Mode
One decision stays central while secondary and hidden signals remain recoverable.
Interface views use public or fictional demonstration data. No private document content is shown.