Skip to content

Projects

Planned product surface

Projects are intended to provide durable work boundaries inside a Product and Organization. The current Projects interface is design scaffolding; authoritative project work management is not yet implemented.

  • An Organization provides the top-level ownership and authorization context.
  • A Product represents an enduring system or product.
  • A Project represents a durable technical or work boundary inside a Product.
  • A repository may be attached to a Project later, but the initial model does not require one.
  • Product and Project context may filter the current view, but it must never hide unresolved Global Attention elsewhere.
  • Project creation, lifecycle, ownership, and authorization
  • Work Item and workflow provenance
  • Repository and workspace relationships
  • Delivery history and reviewed-result evidence
  • Assignment to people, teams, roles, agents, or system actions

The final lifecycle and API contract will be documented after Work Items and internal teams are accepted.