Maya — Developer Experience & AI Engineering Lead
Type: Secondary Persona
Responsibilities
- Owns the governed rollout of AI coding assistants (Copilot and equivalents) across a developer population of thousands
- Stands up internal registries, allow-lists, and catalogs so developers can discover approved MCP servers and agent tooling from inside their IDE
- Balances developer pull for new AI tooling against enterprise supply-chain and security requirements
- Coordinates with security, platform, and architecture teams to decide which AI features are safe to enable and when they can be rolled out at scale
- Evaluates AI product lifecycle (preview vs GA) against enterprise contract and compliance constraints
Related Problem Statements
| Problem Statement | Context | Impact | Naftiko Today | Naftiko Tomorrow | Type |
|---|---|---|---|---|---|
|
Need an Internal MCP Server Registry as an Allow-List
Enterprises need an internal registry of approved MCP servers that surfaces inside the developer IDE, acting as an allow-list so developers discover only vetted servers.
|
|||||
|
Need to Separate MCP Discovery Registry from Package Distribution
The MCP discovery registry (which servers are approved) and the package registry (where the binary actually lives) are two different systems with different governance requirements.
|
|||||
|
Need to Align Enterprise AI Rollout with Product GA Timing
Enterprise contracts only cover generally-available features, so AI tooling rollouts at scale must wait for GA even when developers are already asking for preview capabilities.
|
|||||
|
Need MCP Documentation in Existing Portal Pipelines
Enterprises with mature OpenAPI portal pipelines need MCP-server documentation that flows through the same build process — not vendor-coupled extensions or a parallel doc system.
|
|||||
|
Need API Onboarding Flow Standardization Beyond Translation
API onboarding flows — sign-up, account creation, scopes, token issuance — are wildly inconsistent across providers, and the translation/gateway layer does not fix the hard middle: the onboarding-flow layer itself.
|
|||||
|
Need Dynamic Tool Discovery with Client Compatibility
MCP servers exposing dynamic tool discovery still run ahead of client support, leaving a cross-ecosystem compatibility gap that blocks scaling tool catalogs past a handful of agents.
|
|||||
|
Need API-First Internal Software with MD-File Agent Instructions
Internal enterprise software is shifting to a pattern where every service is an API, every API is exposed to agents via markdown / skills files, and users themselves activate or deactivate features — replacing generic SaaS with customer-specific agentic interfaces.
|
|||||
|
Need a Canonical Agent-Ready Developer Platform Pattern
Developer platforms need a canonical pattern for what 'agent-ready' actually means — a spectrum from markdown and llms.txt at the simple end through full discover-sign-up-and-build-PoC agent journeys at the complex end.
|
|||||
|
Need Onboarding Flow Where First Step Is Copy an MCP Skill Prompt
Developer platforms need a canonical onboarding pattern where the first step is copying an MCP skill prompt — copy the .env key, copy the prompt, run — replacing multi-page sign-up flows for agent-era developers.
|