Everything Shift Harness publishes on Security in the Era of AI lives under CTO playbook. Start here for AI playbook that CTOs and delivery teams can act on.
AI operating model
An engineer will drop the phrase into a planning meeting and mean it as a personal workflow upgrade. Take the phrase seriously. The framing it arrives in is the part to reject.
AI operating model
An agent shipped clean code that quietly broke a convention living in a wiki page it never opened. The instruction file is where a team's standards reach the code, or quietly fail to.
AI Security
Agent security debates fixate on attacks reaching the agent. The question that comes first: what is the agent allowed to do, and through whose identity? That standing authority is owned by no one and revisited approximately never.
AI in Software Delivery
AI output volume is up and the dashboard says adoption works. Escaped defects and rework say otherwise. The gap is a standard your team never rewrote: what "done" certifies once an agent wrote the code.
Quality Harness Engineering
Skills, subagents, hooks, MCP. Most leaders treat them as one pile of jargon and let whoever wired the agent that morning decide. Each answers a different question, and the question is yours.
Quality Harness Engineering
The model writes the function in four seconds and the team still does not move. AI removed the cost of writing code and left the cost of specifying, governing, reviewing, and remembering it untouched. Six artifact classes are what close that gap.
AI operating model
The cut was supposed to prove AI was working. The quiet rehiring is the proof that something else was. AI takes the task; it does not inherit the judgment, ownership, and review standard the seat also held.
Role Playbooks
A background agent opened a PR at 2 a.m. and the gate let it through, because the gate was built for a worker who could be reasoned with. The DevOps job is no longer writing infrastructure. It is owning the bounded environment agents act inside.
AI Security
Connecting an MCP server is not enabling a feature. It is taking on a code dependency that holds execution and data rights nobody reviewed. You already govern packages and APIs as a supply chain. Your MCP fleet is the same risk under a new name.
AI Security
For two years teams filed prompt injection under "someone else's problem." That filing expired. The moment an agent reads content it did not author, every author of that content can rewrite its instructions.
AI transformation
An AI agent is not a smarter chatbot. It is a new reader of your system of record, and it can only read what you have made authoritative, current, and governed. The Klarna case is the warning: govern the substrate before you scale the reader.
AI operating model
Slow human execution used to absorb your org's ambiguity before anyone noticed. AI compresses that buffer, so thin specs, unclear ownership, and broken handoffs surface at speed. The fix is the operating model, not another tool.