Only approved customer stories are published
We describe the customer problem, scope, and verified outcomes within the boundaries of explicit publication consent.
No customer story is currently approved for public release. The implementation patterns below show how deployment and validation can be structured by industry.
How Patty Code and PCCP work together
These are fictional scenarios, not customer outcomes. They explain deployment structures and validation questions for specific operating environments.
Specialty hospital in Seoul
Balancing delivery speed and control for clinical-support systems
A fictional design in which an internal hospital team uses Patty Code for changes while PCCP governs personal-data access, approval scope, execution environments, and evidence.
Read implementation pattern↗02Financial services · fictional implementation scenarioKorean financial-services organization
Shortening regulated code review while preserving separation of duties
A software-delivery pattern that expands development automation while PCCP fixes dual approval, permitted tools, and production-data boundaries as policy.
Read implementation pattern↗03Manufacturing · fictional implementation scenarioGlobal industrial enterprise
Modernizing production systems whose documentation no longer matches the code
A modernization pattern that moves from read-only analysis to staged deployment while controlling permissions by plant and environment.
Read implementation pattern↗04Public sector · fictional implementation scenarioPublic-sector development organization
Operating a coding agent inside a sovereign, disconnected environment
A sovereign deployment pattern that keeps models, tools, and repositories inside the approved boundary while requiring human approval and audit-ready execution records.
Read implementation pattern↗