Builds / the work itself

Built to be used.

A project earns its place here by meeting a real need. The record includes what it is for, where it stands, and what becomes clearer through use.

Build 001 / in progress

MONDAY: a more useful kind of AI assistant

MONDAY is Chris’s ongoing, user-owned AI chief-of-staff project. Its aim is to help carry context across projects and conversations, so useful work can continue without starting from zero each time.

The important questions are practical: What knowledge should an assistant rely on? How should it distinguish a plan from something actually done? How can it stay useful while keeping the owner in control of consequential decisions?

This is an active build. It is not presented here as a finished product or a service you can sign up for. As public-safe lessons become clear, this journal will explain the problem, the choices, and what held up in real use.

What to expect

Evidence before a victory lap.

Future build updates will name the stage of the work and separate experiments from dependable results. If a lesson only applies to one context, it will say so.

How builds will be documented

  • The need: the specific friction that made the work worth starting.
  • The approach: enough detail to understand the choices, without exposing private material.
  • The use: what happened when the idea met ordinary work.
  • The lesson: what another builder can borrow, question, or avoid.

More entries belong here when there is actual work and a useful lesson to share.