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.