Tier 1: Provider
Provides the model and service under published capabilities and limitations. It does not own the enterprise's decision to use the recommendation in procurement.
CONSTRUCTED EXAMPLE
A generic enterprise procurement team is preparing an agent that checks vendor submissions and recommends whether a human reviewer should escalate a package.
Published under CC BY 4.0. Free to reproduce, adapt, translate, and use commercially, including inside your own governance program, with attribution to Sougata Roy and a link to this page. Attribution is a condition of the license. Claiming authorship is not attribution. Full terms at sougataroy.com/rights
Cite this framework
Sougata Roy, "The Deployment Accountability Map", Version 1.0, April 2026, https://sougataroy.com/frameworks/deployment-accountability-map
Filled accountability map
This scenario is constructed for explanation. It is not a real organization and is not drawn from an engagement.
Tier 1: Provider
Provides the model and service under published capabilities and limitations. It does not own the enterprise's decision to use the recommendation in procurement.
Tier 2: Control infrastructure
Provides the registered identity, configured permissions, audit trail, and access controls. It enforces what the organization configures, not what the organization intended but never recorded.
Tier 3: Deploying organization
Authorizes the purpose, permitted scope, prohibited actions, human review point, named Consequence Owner, and deployment decision. Those choices are recorded before production use.
Output
A completed map showing the gap between platform controls and organizational accountability.
How to use this page
Compare this completed map with the primary framework, then create a map for a real deployment. The example demonstrates the accountability boundary; it does not replace organization-specific authorization.