Skip to main content
A P2HS project groups the source and operational state needed to build an application: workspace ownership, source/import state, composition, environment configuration, codegen runs, revisions, previews, deployments, and domains.

​
Project boundaries

Project reads and mutations are workspace-scoped. A project ID alone is not a substitute for an ownership check. Integrations, secrets, and environment values are likewise scoped to the project and its allowed targets.

​
Project lifecycle

Not every project takes every path. For example, an imported project may begin with discovery, while a new AI project may begin with a prompt session.