FIRST PUBLIC USE
March 20, 2026
SHARED TERM NOTE
Intent Architecture Stack stays on the site because it is a published framework with its own page and predates the book.
CANONICAL EXAMPLE
A financial services firm implements the Intent Architecture Stack across its Microsoft agent deployment: the board approves the AI risk tolerance policy, the CISO owns the agent registry and access governance layer, enterprise architects own the intent design layer for each agent, security operations owns the runtime behavioral monitoring layer, and internal audit owns the review cycle. When an agent drifts, the stack identifies the accountable owner at the layer where the gap occurred — no Accountability Assumption is possible.
USAGE GUIDANCE FOR CONTENT
Use Intent Architecture Stack in framework documents, long-form newsletter editions, and posts that move from problem to structured solution. It is the most complete term in the vocabulary — use it when the audience is ready for a full governance model, not just a named problem. It is most effective paired with a visual or a layered description that makes each accountability layer concrete. Mark as evolving until a formal framework document is published.