Pseudotsuga menziesii

cannonical approaches in the ai era


Recently I was reading on Heitor Gouvêa’s core takeaway from Nubank - that security vulnerabilities and maintenance bottlenecks hide in the cost of variation - and noticed that it became an existential problem in the AI era. This text are my notes, with a few extra thoughts on how to apply canonical principles to internal AI tooling.


Across industries, the recurring pitch among C-level executives is that AI will make employees more productive. But the reality is that AI makes employees more autonomous.

When motivated employees use AI to build internal tools, scripts, and agents ("vibe coding"), variation explodes overnight. Instead of three teams picking different HTTP libraries over a year, fifty people spin up bespoke apps in a weekend, each missing cross-cutting concerns like authentication, secret management, SSRF protection, and audit logging, and worse - they seldom host their code a private repository or document it. The result is a sprawling, unmaintained, and insecure internal AI ecosystem at the mercy of the employee's endpoints security posture, holding organizational data at risk (most of the time).

Banning AI builders only drives usage underground into "Shadow AI." To preserve employee agency while keeping security and tech debt under control, the canonical principle must be applied by turning the central architecture into a paved road: make the secure, standardized path the fastest way for both humans and LLMs to ship.

To keep the discussion concrete, I’ll focus on three canonical approaches to internal AI tooling:

1. Centralized Architectures (The Paved Road)

Rather than auditing every individual AI-generated app, centralize the infrastructure primitives that every tool has to touch:

2. Security Guardrails for High-Agency Builders

When non-security engineers - or non-engineers - build tools with AI, security cannot rely on code review alone. Enforce invariants at the runtime layer:

3. Containing Tech Debt: The Tiered Graduation Model

Tech debt happens when a quick AI experiment quietly becomes mission-critical without anyone owning it. Establish explicit lifecycle tiers with built-in expiration dates so experimental code doesn't calcify:

Lifecycle TierIntended ScopeCanonical RequirementsTech Debt Control
Tier 1: SandboxPersonal productivity & throwaway prototypesRuns via AI Gateway; user-scoped OAuth only; zero persistent shared DBs30-day TTL: Infrastructure auto-pauses or deletes unless explicitly renewed
Tier 2: Squad UtilityShared workflows within a single teamMust use the canonical starter template, SSO, and central logging; named team ownerQuarterly ownership check: Orphaned tools without an active team owner are archived
Tier 3: CanonicalCross-org tools or customer-adjacent systemsFull engineering review, SLOs, automated testing, and standard CI/CDConsolidation: Platform/Core teams absorb the prototype and deprecate duplicate clones

By separating freedom to prototype (Tier 1) from permission to persist (Tiers 2 and 3), you let employees experiment at full speed while ensuring that only validated, standardized software accumulates in your long-term codebase.

Are you currently trying to rein in internal AI sprawl at your organization, and if so, is the bigger pain point right now security exposure (keys, data access) or unmaintained tool proliferation?

Mapping these canonical approaches to your internal AI strategy can help you answer that question and prioritize the right guardrails.

↑ Back to top