Each framework is published in full, with its object model, roles, worked examples and glossary.
A practitioner method for designing, building and evolving an operating model. Six stages from the enduring WHY to a model that keeps changing, three design layers from principles to specifications, six dimensions running through all of them, fourteen printable worksheets, and a stage gate that is passed on evidence rather than waved through.
Read the framework →Reference method · v0.7A software development method for teams where coding agents do most of the typing. Seven phases in two loops and a pulse, three change classes set by what a change touches, six agent roles with a read-only verifier that never built the change, four phase skills that run the change loop, and evidence bound to the exact commit it covers.
Read the framework →Reference model · v1.0An enterprise economic control system for AI, not a cryptocurrency model. Three operating objects (AI Credits, Seats and Entitlements, Capacity), a 13-step demand-to-execution lifecycle with four gates, an Architecture Review with a Token Assumption Stress-Test, and transparent chargeback from central funding to business-unit accountability.
Read the framework →Reference model · v3.0A conceptual framework and logical object model for managing digital risk within enterprise risk management. Nine connected domains, one golden thread from corporate objective to governance decision, aligned to COSO ERM, ISO 31000 and 27001, NIST CSF 2.0, COBIT 2019 and DORA.
Read the framework →More frameworks are in preparation. For writing on governance, architecture and transformation, see Thought Leadership.
Reference model v3.0. Use it, adapt it, or talk to me about standing it up in your organization.
Connect on LinkedIn →