AI Shaping practice is governed by seven established practice-derived principles, organised through a complete capability lifecycle and enacted through reusable practitioner techniques. Public disclosure narrows as operational specificity increases: principles are stated directly, the lifecycle is shown through broad capability bands, and techniques are explained by role and benefit while their catalogue and operating machinery remain protected.
Principles govern what must remain true. The lifecycle governs when work, decisions and transitions occur. Techniques govern how particular recurring work is performed.
The strategic hierarchy remains Principles → Lifecycle → Techniques. Principles constrain the whole practice. The lifecycle organises capability work over time. Techniques are reusable ways of performing recurring work within or across lifecycle phases.
The public disclosure funnel is different from the hierarchy. It controls depth, not importance: operational detail becomes progressively more protected as it becomes easier to reproduce, transfer or operate independently.
The narrowing widths represent disclosure depth, not strategic rank. Principles remain the highest layer; techniques remain essential to disciplined practice.
The seven principles are established within the current AI Shaping body of work. They are practice-derived, evidence-sensitive and iteratively improvable under human direction. They are not an external standard, universal doctrine, complete body of knowledge, mandatory seven-step process or independent implementation authority.
The groups are memory aids. The principles recur, interact and constrain one another throughout the lifecycle.
The lifecycle covers the whole capability over time, not only establishment. For public orientation, the complete lifecycle is grouped into five broad bands. These bands show completeness and decision flow without publishing the canonical phase catalogue or practitioner operating sequence.
Determine whether shaping is justified, define the capability and establish its purpose, authority, sources, boundaries, suitable approach and intended value.
Create the bounded capability, test its fitness, remediate material findings and obtain human acceptance before consequential use.
Apply the accepted capability across recurring work while preserving continuity, reviewability and controlled improvement under human direction.
Respond to material change and separately evaluate broader related use or movement into another work domain.
End reliance responsibly while preserving required state, history and residual obligations.
Public-band boundary: these five bands are disclosure categories, not replacement phase names. The complete lifecycle, phase gates and practitioner detail remain private or protected. Improvability by design is also distinct from actual improvement through accepted revision and measured improvement supported by defined measures.
Techniques are reusable ways of performing recurring shaping work. They turn broad principles and lifecycle intent into more consistent, reviewable and resumable practice. The public site explains their role and benefits rather than publishing the named catalogue, selection logic or procedures.
A technique may support one lifecycle phase, span several phases or recur across the lifecycle. Detailed technique names, applicability rules, inputs, activities, outputs, gates, exceptions and recovery machinery remain private or protected.
The public site shows the seven compact principles, complete lifecycle coverage through broad bands, the role and benefits of reusable techniques, observable work-burden shift, source basis and the human-authority boundary.
This is enough to understand the practice architecture, recognise potential relevance and evaluate whether a defined deeper question is justified.
The canonical lifecycle phase structure, named technique catalogue, selection logic, complete procedures, detailed gates, decision rules, readiness tests, prompts, templates, schemas, validation and recovery machinery, sensitive records and sufficient material to reproduce or independently operate the method remain private or protected.
Protected-stage discussion is for a defined question, minimum necessary detail and agreed protective conditions—not unrestricted method transfer.
Use the AI shaping category page for the whole public concept architecture, Operating-model design for the work-system lens, or Productive AI work for the outcome.
Page 4 of 31