Projects
Projects now expose workflow ownership, project scope, and object scope on top of the same shared foundation model as Team. That keeps later execution, billing, and marketplace expansion attached to one stable boundary.
Project Boundary
Projects now read and mutate against the same shared foundation
Day 11 now keeps org, project, and membership reads on the D1-backed foundation, while account root updates, project creation, active-project switching, and project detail updates all enforce the same actor-aware foundation boundary before D1 mutation begins.
Service boundary: foundation-control-plane-service · demo:error
Total projects
--
Active now
--
Staging
--
Planned
--
Project state
Project boundary data is unavailable
This error-state demo models the org or project foundation failing before the project list can render.
We need this shell now so later RBAC and billing gates can fail without redesigning the workspace surface.