AI shaping FAQ for first-time readers and reviewers

AI shaping is the operating-model discipline for establishing shaped intelligence that carries a reusable and iteratively improvable domain work pattern and reusable work basis. Two-sided work-burden shift is the operational effect while source basis and human authority remain explicit. The AI shaping page holds the canonical website definition.

The direct-shaping approach establishes a bounded shaped capability directly under human direction and may support sophisticated, long-running work. The mediated-shaping approach develops, governs or renews shaped intelligence through AI-shaping intelligence. Use the AI shaping page for the formal website definitions and full relationship.

AI shaping establishes a reusable and iteratively improvable domain work pattern and reusable work basis. Shaped intelligence then carries more of two recurring burden sides: domain-practice standards and subject-context reasoning, and work-state preservation and work-resumption logic. Source basis is carried forward; judgement, approval and real-world action remain human-owned.

AI-shaping intelligence is the reusable shaping capability used in the mediated-shaping approach to develop, govern or renew shaped intelligence. It combines self-shaping capability, which develops and renews the shaping pattern, with domain-shaping capability, which uses that pattern to develop shaped intelligence for a target work domain under human direction.

Shaped intelligence is the domain-facing reusable capability that carries more domain-practice and subject-context burden, and more work-state and resumption burden, through a shaped work pattern and reusable work basis while source basis and human authority remain explicit.

Product-managing shaped intelligence is operationally established within the bounded AI Shaping knowledge and publication product. It carries recurring product-state, owner-selection, sequencing, reconciliation and resumption burden through governed automation under human review. Its DOI-backed Capability Evidence paper supports initial bounded evaluation while the three-cycle maturity gate remains satisfied; neither fact establishes quantified burden reduction, independent validation, generic transferability or universal Product-management capability. Read the canonical capability page.

No. Governed automation means AI carries recurring coordination through accepted controls and every consequential result remains subject to human review and acceptance. Purpose, scope, source decisions, judgement, disclosure, publication, deployment and real-world action remain human-owned.

It means Kurni Kwok retained functional responsibility for product purpose, value, audiences, priorities, scope, architecture decisions and acceptance, together with stewardship and consequential decision authority. It describes functional responsibility within this bounded product; it does not establish complete Scrum accountability, a conventional Scrum Team or autonomous AI operation. Read the bounded product-ownership account.

Publication co-evolution through reciprocal refinement is a principal mechanism used by Product-managing shaped intelligence across four separately governed publication capabilities. It is not the umbrella capability, a fifth publication capability, automatic propagation or simultaneous multi-agent operation. Read the mechanism section.

They are peer domain-facing capability types with separate formal Capability Evidence papers. Project-managing evaluates the distinct mediated-shaping project-work instance. Product-managing evaluates the distinct bounded direct-shaping product instance through retrospective first-party evidence. Neither paper establishes that one capability is categorically higher or interchangeable with the other.

The DOI-backed Product-managing Capability Evidence paper reports a purposive eight-case first-party corpus, including governed continuation, human correction and deliberate stopping or prevented propagation; accepted controls and repeated cycles support bounded operational establishment, and the three-cycle maturity gate remains satisfied. The evidence does not establish quantified burden reduction, measured productivity improvement, independent validation, autonomy, generic transferability, universal Product-management capability or complete Scrum practice.

Productive AI work is AI-enabled work that is grounded, practice-guided, subject-aware, reviewable, repeatable and resumable under human direction. It is a higher threshold than useful AI output.

AI shaping is useful where recurring work has enough underlying structure to be shaped and people repeatedly rebuild context, source basis, domain-practice guidance, subject-specific context, review state, unresolved matters and next action before useful AI output can become reviewable work.

Not only. It can help individual work, but the category is broader: an operating-model discipline for shifting more recurring work burden to shaped intelligence so productive AI work can continue under human direction.

No. Prompt engineering improves an individual instruction or output; agents may plan, route or act through task steps; automation executes predefined sequences; workflow and project tools organise tasks and artefacts. AI shaping is the operating-model discipline centred on two-sided work-burden shift. It shapes the work pattern and arranges the reusable work basis so shaped intelligence can carry more recurring burden while source basis and the human-authority boundary remain explicit. For the one-page comparison, use AI shaping vs prompts, agents, automation and workflow tools.

No. Publicly, the safest way to describe it is that AI shaping arranges the work pattern, reusable work basis and human-authority boundary around broad general-purpose AI capability. It does not claim to alter the model’s trained weights.

No. Prompt engineering can improve an individual request or output. AI shaping is broader: it concerns the operating-model design of recurring work and whether more two-sided work burden can shift to shaped intelligence while source basis and human authority remain explicit.

AI productivity is too broad for the specific claim. AI shaping focuses on operating-model design, shaped capability and visible two-sided work-burden shift while the human-authority boundary remains intact. Work burden shifts; accountability does not.

No. Specification-led AI work and iterative AI work are comparison labels for different ways AI-enabled work develops, not additional canonical AI-shaping concepts. AI shaping can operate across both and addresses the recurring work-system burdens that neither pattern resolves by itself.

No. AI shaping is defined by the shaped work pattern, reusable work basis, two-sided work-burden shift, source basis and human-authority boundary. Models and platforms may make one work pattern more practical than another, but they do not define the category.

Project-managing shaped intelligence is the formally published mediated-shaping capability-evidence instance in project and business-as-usual (BAU) IT support contexts, carrying recurring project and BAU IT support work burden while human authority remains explicit.

Work-burden shift is the visible before/after change where more two-sided recurring burden moves from the responsible person to shaped intelligence: domain-practice and subject-context burden, and work-state and resumption burden. Judgement, approval and real-world action remain human-owned.

Two-sided work-burden shift has a domain-practice and subject-context side, and a work-state and resumption side. The first is about carrying practice standards, subject-specific context and relevant reasoning. The second is about preserving current work state, unresolved matters, review status, continuation point, pending work and next-action logic. Source basis is a grounding condition around both sides, and the human-authority boundary governs the shift.

No. AI shaping is about shifting recurring reconstruction, tracking, sequencing, review-preparation and communication-preparation burden. Purpose, supplied context, judgement, review, approval, disclosure, escalation, communication, decisions and real-world action remain human-owned.

Reconstruction means rebuilding the AI work basis before useful work can continue: context, source material, prior decisions, constraints, risks, review status and next action. In ordinary AI use, this often shows up as having to write a long or complex prompt to re-explain the work.

Resumption means continuing work from a preserved reviewable state after a pause, handover, context loss or new information, instead of rebuilding the whole work basis again.

No. The burden that shifts is recurring work such as rebuilding the work basis, applying domain-practice expectations, using subject-context reasoning, sequencing, drafting, tracking, framing and resuming work after a pause. Work burden shifts; accountability does not. Judgement, approval and real-world action remain human-owned.

Stock-evaluating shaped intelligence and code-developing shaped intelligence are prospective cross-domain transfer-evaluation directions. Portfolio-managing shaped intelligence is a possible later extension after stock-evaluating shaped intelligence is materially developed and evaluated. All three share the same public claim status: planning context, not current capability evidence or implementation commitments.

Domain extensibility and domain transferability are evaluation properties. Domain extension is the actual widening of shaped intelligence within a related work family; the current public evidence shows vendor-evaluating shaped intelligence extending into project-managing shaped intelligence because vendor evaluation is a subset of broader project-management work. Domain transfer evaluates target-domain rematerialisation of the shaping pattern in a different work domain, such as stock-evaluating shaped intelligence for one listed stock. Domain extension does not prove domain transfer, and neither public wording nor website diagrams authorise protected-method transfer or implementation.

Read the Category Definition paper first for the shared concept architecture. Read the Project-managing evidence paper for the mediated project-work instance. Read the Product-managing evidence paper for the bounded direct-shaping product instance.

No. The public release supports category understanding and bounded public-stage capability evaluation. It does not provide deployment assurance, product-performance assurance or reproducibility proof.

They are dense because they are doing category-definition and bounded evidence work, not casual marketing explanation. The website provides shorter concept pages so the papers can remain precise and defensible.

The website is the guided reader layer. It explains one public question at a time and routes to the formal source when needed. The DOI-backed papers remain the formal public record for category definition and capability evidence.

No. The site should simplify the reader journey, not reduce the claim. A page can use plain examples, route cards and short boundary notes while glossary popovers, the public evaluation map, the protected-stage page and the papers preserve the precise terms and limits.

Use glossary popovers for canonical website short definitions and the Category definition paper for the formal category treatment.

No. The public pages and papers do not provide implementation guidance, method transfer or commercial-use rights. Implementation-level review requires protected-stage discussion with protective purpose, confidentiality, ownership, scope and permitted use agreed first.