Carlo Caprini
Menu
Question

What changes when AI becomes part of the work?

What AI changes about contribution, ownership and system design when it becomes part of everyday work.

AI can help people contribute sooner and move work through a system faster. It also makes boundaries, review and ownership more important because convincing output can arrive before anyone has developed enough context to judge it well.

These notes follow that tension through software development and the small services I build for my own work. I am interested in what the surrounding system needs when AI performs more of the work. The notes move from contribution and review into my bounded-service experiments, then to Friday and the problem of coordinating those services without transferring ownership to the orchestrator.

Back to Explore
Start here

AI accelerates contribution, not mastery

AI can help people contribute sooner without giving them the context or judgment needed to understand and review the work deeply.

AI and automation Teams and collaboration
Thinking

Notes that develop the question.

This is a curated path rather than a complete topic archive. Each group approaches the question from a different part of the work.

Contribution is not understanding

AI can help someone contribute sooner without giving them a deep model of the system or the work.

  • Better output makes shallow review more dangerous AI can make work look ready before its reasoning deserves trust. Review depth should follow the consequences of the decision, not the polish of the output. AI and automation Teams and collaboration
  • Shared context is not shared understanding AI makes context easier to retrieve, but access to the same information does not automatically create shared understanding, alignment, or better decisions. Teams and collaboration AI and automation

Bound the work and keep ownership explicit

Useful AI systems need a clear job, visible state and boundaries around what they can decide.

  • 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
  • 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
  • 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
  • Adding MCP doesn't make a product agent-first Adding MCP to an existing API can create enormous value by making an established product accessible to agents. Designing a product with agents as first-class users is a different problem. AI and automation Software systems
  • Designing for unattended development Unattended development is not the same as leaving an agent alone. It requires explicit eligibility, isolation, verification, stop conditions, and a separate decision about what may enter the stable codebase. AI and automation Software systems

Coordinate attention without taking control

Orchestration becomes useful when it helps a person see what needs attention while leaving authority with them.

  • 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
  • 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
  • Stop asking people for information the system already has Much process work moves facts between tools. Useful automation connects what is already recorded while keeping system interpretations separate from source truth and human judgment. Software systems
  • 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
Influences

Ideas that sharpen the question.

Selected external arguments and research that add evidence, language or a useful challenge.

Experience behind the ideas

Introducing AI into existing capabilities

How AI features change product behaviour, workflows and operational expectations around an existing system.

See the experience behind this question