Projects Are the Unit of Execution

All essays2026-05-067 minprojectsexecutioncontextproduct

Why Projects Matter

Projects are the unit of execution in FleetCrown.

A project is not just a repo card. It is the thing that ties together:

source code
git health
session handoff
agent runtime
related goals
related prompts

That makes the project the main boundary where abstract intention turns into concrete work.

The Product Mistake To Avoid

Many systems treat projects as metadata. That creates shallow project pages that describe work without helping the work move.

FleetCrown should do the opposite. A project should be the place where context becomes operational:

what changed
what is broken
what is next
which agent is active

What Success Looks Like

Projects succeed when opening a project feels like stepping into a live work context rather than opening an archive entry.

Newer

System Is Where the Product Admits It Is a Runtime

Why the System product matters: it is where FleetCrown stops pretending to be only an app UI and exposes the runtime and autopilot machinery underneath.

Older

People Is a Relationship Operating System

Why People should not be a static contacts list, but a living map of social context, relationship health, and interaction history.

Control and Projects — Two Views, One System

Control and Projects serve genuinely different needs and should stay separate. Here is the source of truth for each, what their tiles show, and how to improve them.

Goals Are the Bridge Between Ambition and Work

Why Goals exist to connect direction with execution instead of becoming isolated motivation artifacts.

Memory Is the Knowledge Layer

Why Memory exists as the long-term substrate beneath projects, people, goals, and interactions instead of as a decorative graph view.