Pat — Head of Platforms

Type: Primary Persona
Responsibilities
- Owns platform strategy across many domains & teams
- Centralized services & tooling & guidance
- Works across engineering, security, and architecture
Related Problem Statements
| Problem Statement | Context | Impact | Naftiko Today | Naftiko Tomorrow | Type |
|---|---|---|---|---|---|
|
Need MCP to Integrate with Existing Governance Tooling
Organizations need to understand how MCP fits into existing API infrastructure and governance tooling they have invested in over the past decade.
|
|||||
|
Need MCP Documentation
The assumption that AI will figure out how to use MCP servers is wrong, and traditional documentation and discovery are still required.
|
|||||
|
Need Auto-Discovery of API Artifacts
Building an accurate catalog of APIs and services requires automated discovery rather than manual registration that developers resist.
|
|||||
|
Need to Define What Reuse Means
Pat has been asked to drive API reuse but the organization has never defined what reuse means.
|
|||||
|
Need Discoverability Not Just Governance
Pat realizes the organization has been focused on governance when the actual problem is that teams can't find what already exists.
|
|||||
|
Need Governance to Be Seamless
API governance must be embedded seamlessly into the developer workflow so that the compliant way of building APIs is also the easiest and most secure way.
|
|||||
|
Need Developer Experience Treated as Product Discipline
Documentation efforts are treated as a publishing exercise rather than a product discipline that actively enables and teaches developers.
|
|||||
|
Need Clear Ownership for Context Layer
The repo context layer (README, CONTRIBUTING, AGENTS) has no clear owner as AI copilots roll out across IDEs.
|
|||||
|
Need Continuous Agent Readiness Checks
Scaling IDE copilots across hundreds of repos requires a repeatable way to verify each repository is agent-ready.
|