> ## Documentation Index
> Fetch the complete documentation index at: https://docs.p2hs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How P2HS works

> Follow an application from idea or source repository to deployment.

P2HS organizes application work around a project. A project can begin as a new AI-assisted build or as an imported existing source tree.

<Steps>
  <Step title="Create or import">
    Start a project with P2HS AI or import source from an existing application. Source import and Git workflows preserve the project boundary used by later builds.
  </Step>

  <Step title="Configure">
    Select the project’s composition, environment configuration, authentication policy, and integrations that the implementation admits for that project.
  </Step>

  <Step title="Build and validate">
    A codegen run plans and applies changes, records status and timeline data, and can request user input or approval when required.
  </Step>

  <Step title="Preview">
    Successful build output can be made available through a preview deployment for verification before production.
  </Step>

  <Step title="Deploy and operate">
    Production deployment, domains, revisions, and subsequent updates remain associated with the project.
  </Step>
</Steps>

## P2HS-owned boundaries

P2HS keeps project ownership, entitlement and capability policy, billing state, secrets policy, and orchestration authoritative at the platform boundary. Application workloads run through managed build and runtime services that receive only the authorization and configuration required for the project.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.