Operating context
Public-sector development environments often require network separation, restricted data export, and software-supply-chain review. Sending source code to an external SaaS agent may be prohibited.
Hosting a model internally is insufficient by itself. Operations must also define who can use which tools in which repository and how every result is validated.
Deployment design
Patty Code uses internal model endpoints and approved development tools only. Project context and instructions stay in internal repositories and session data is not sent outside.
PCCP governs human and agent identity, repository scope, command allowlists, and approval for exported artifacts. Policy versions and execution records remain inside the audit system.
Operating flow
- 01
Patty Code proposes a plan and required tools first. Network use, package installation, and deployment wait for explicit security approval.
- 02
Only approved commands run in isolation. Outputs pass internal validation, and any exported artifact includes provenance and a change record.
- 03
Operators review policy violations, pending approvals, execution outcomes, and audit evidence in one governed flow.
Pre-deployment validation
- Code and session data stayed inside the approved boundary
- Model and tool versions were recorded
- Named approvers authorized high-impact actions
- Policy changes and execution results can be audited independently