Skip to main content
P2HS treats security as a set of explicit boundaries:
  • workspaces and projects are tenant-scoped;
  • P2HS is authoritative for ownership, entitlements, capability admission, and usage policy;
  • managed runtime services execute only admitted work;
  • secrets are policy-controlled assets with explicit propagation targets;
  • provider credentials are not exposed to browser clients;
  • webhook signatures and provider events are verified before reconciliation;
  • MCP clients use scoped grants and tool authorization;
  • generated applications should use approved server-side or trusted-client flows.
This documentation describes implemented technical mechanisms. It does not make compliance or certification claims.