AI Security & Fiduciary (CISO)

Technical debt is the implied cost of future rework caused by choosing an expedient solution now instead of a better approach that would take longer. First coined by Ward Cunningham in 1992, technical debt has become one of the most important concepts in software engineering economics. Like financial debt, technical debt accrues interest. Every shortcut, every "we'll fix it later," every copy-pasted function adds to the principal. The interest comes in the form of slower development velocity, more bugs, longer onboarding times for new engineers, and increased fragility of the system. Technical debt exists on a spectrum from deliberate ("we know this is a shortcut but ship it anyway") to accidental ("we didn't realize this was a bad pattern until later"). Both types compound over time. Organizations that don't actively measure and manage their technical debt risk reaching what Richard Ewing calls the Technical Insolvency Date — the specific quarter when maintenance costs consume 100% of engineering capacity.

Orchestration Debt is an emerging form of AI technical debt (2026) created when autonomous AI agents interact with multiple enterprise systems, creating complex dependency chains that are difficult to monitor, debug, and maintain. As organizations deploy agentic AI workflows where agents call other agents, access databases, invoke APIs, and make decisions autonomously, the orchestration layer between these components accumulates debt through: undocumented dependencies, brittle error handling, cascading failure modes, and untested interaction patterns. Orchestration debt is uniquely dangerous because it is invisible — each individual agent may work correctly, but the interactions between agents produce emergent behaviors that no single team designed or tested.

The Innovation Tax is a framework coined by Richard Ewing that measures the hidden cost of maintenance work that gets reported as innovation investment. It is OpEx masquerading as R&D investment, causing organizations to dramatically overestimate their effective engineering velocity. When a team reports '65% of time on new features' but the actual number is 23%, the 42-point gap is the Innovation Tax. This gap causes CFOs and boards to overestimate R&D productivity and make poor capital allocation decisions. The Innovation Tax is insidious because it's invisible in standard reporting. Engineering teams don't intentionally misreport — the maintenance work is scattered across feature work, making it hard to isolate. Bug fixes get bundled into feature sprints. Infrastructure upgrades get coded as feature dependencies. Benchmark: >40% Innovation Tax is dangerous. >70% is terminal — the organization is approaching the Technical Insolvency Date.

AI-Assisted Development encompasses the integration of advanced Large Language Models, coding agents, and generative copilots directly into the software development lifecycle (SDLC). By 2025/2026, tools like Cursor, GitHub Copilot, Devin, and SWE-Agent evolved from simple autocomplete engines to autonomous architectural reasoning systems. The paradigm shifted developers away from "writing code" and towards "prompt supervision, structural review, and security verification." While AI Dev tools radically boost individual throughput, they create significant systemic risks around codebase vastness (software entropy), undocumented context fragmentation, and the unprecedented generation of undetectable AI Technical Debt.