Public evidence asks whether the durable shaped-capability mechanism produces a visible operational effect: more two-sided recurring work burden carried by shaped intelligence while source basis and human authority remain explicit. Evidence strength depends on the bounded instance, not the diagram or wording alone.
Project-managing shaped intelligence and Product-managing shaped intelligence now have distinct DOI-backed formal capability-evidence papers. The Project-managing paper evaluates the mediated project-work instance; the Product-managing paper evaluates the bounded direct-shaping product instance. Public web-developing shaped intelligence remains a bounded, readily inspectable website-specific evidence instance established through the direct-shaping approach.
The roles are complementary, not interchangeable. The separate product-ownership page is a human-authority account, not another evidence role. The Category Definition paper retains formal category authority; each Capability Evidence paper controls its own evidence object and limitations.
These labels identify source and maturity; they are not scores or claims that one route proves the others.
The diagrams answer progressively harder questions. Public web-developing shaped intelligence makes the burden-shift mechanism easy to see. The five-capability publication-product diagram shows Product-managing coordination and publication co-evolution. AI-shaping intelligence shows the reusable shaping capability. Project-managing shaped intelligence shows the mediated project-work instance. The two Capability Evidence papers now provide distinct formal evidence objects for Project-managing and Product-managing shaped intelligence.
The diagrams give public-safe before/after views. They show observable capability relationships and burden shift without disclosing implementation mechanics, providing deployment assurance, proving reproducibility or authorising method transfer.
| Public evidence role | Public role | Boundary |
|---|---|---|
| Website-specific capability example | Shows an instance established through the direct-shaping approach with visible two-sided work-burden shift in recurring website development and revision. | A bounded instance established through the direct-shaping approach on this website; it is outside the capability paper's structured evidence package and does not evidence AI-shaping-intelligence domain transfer. |
| Product-managing shaped-intelligence evidence | Supports the bounded classification that Product-managing shaped intelligence is operationally mature within the AI Shaping knowledge and publication product; repeated accepted operation also shows observable but unquantified coordination value and work-burden shift. | The v1.88 Capability Evidence paper contributes a limited first-party direct-approach argument only. It does not establish quantified effect, sole causation, independent validation, replication, autonomy, generic transferability, universal Product-management capability, complete Scrum practice or general direct-shaping superiority. |
| Reusable shaping-capability evidence | Shows the mediated-shaping approach through AI-shaping intelligence: vendor-evaluating shaped intelligence was developed and then extended into broader project-managing shaped intelligence. | Supports bounded public-stage evaluation of the reusable shaping capability; public pages do not disclose its protected implementation mechanics. |
| Primary project-managing capability evidence | Shows visible work-burden shift in real project and BAU IT support contexts with materially greater work-state and resumption burden. | Supports public-stage capability evaluation only; judgement, approval and real-world action remain human-owned. |
| Illustrative transfer-evaluation map | Shows how later protected-stage evaluation could frame target-domain rematerialisation into a different work domain. | Does not create an investment-domain capability claim, financial advice or implementation authority. |
The three planned capability directions sit outside the current public evidence package. Naming a planned direction does not create a capability claim, evidence stream or transfer result.
Useful one-off AI output, a polished demo, a private implementation description by itself, or an illustrative transfer map without visible burden-shift evidence would not be enough. The public question is narrower: whether the available evidence shows reviewable work-burden shift under human authority, while leaving implementation-level review to protected-stage discussion.
| Question | Use this page | Public-safe role |
|---|---|---|
| What is the most readily inspectable public work-burden-shift example? | Public web-developing shaped intelligence | Shows a bounded website-specific capability instance and connected work across content, information architecture, interface and visual design, front-end implementation, publishing and validation. |
| How is one publication product managed across four publication capabilities? | Product-managing shaped intelligence | Explains the product-level coordinating capability, repeated accepted cycles, the satisfied three-cycle maturity gate, the four publication capabilities and publication co-evolution under human product ownership, stewardship and decision authority. |
| What product responsibilities did Kurni Kwok retain while AI carried recurring delivery work? | AI Shaping product ownership | Explains human product authority and the bounded human–AI work division without creating another capability-evidence role. |
| What evidences AI-shaping intelligence as the reusable shaping capability? | AI-shaping intelligence evidence | Explains the shaping-capability evidence position without disclosing protected implementation mechanics. |
| What is the formally published mediated-shaping project-work evidence instance? | Project-managing shaped intelligence | Explains the distinct Project-managing evidence object and visible two-sided work-burden shift in project and BAU IT support contexts. |
| How should the public evidence be read and where does it stop? | Public evaluation map | Maps category understanding, public-stage evidence review and protected-stage stop rules. |
| Where is the formal DOI-backed evidence artefact? | Project-managing evidence paper | Routes to the formal publication, DOI and citation details for the mediated-shaping Project-managing evidence object. |
| Where is the formal Product-managing evidence artefact? | Product-managing evidence paper | Routes to the formal publication, DOI and citation details for the bounded direct-shaping product-level evidence object. |
The papers index is for publication access and citation. This evidence overview is for website navigation: it tells readers which evidence page to use before they open the relevant formal Capability Evidence paper. Use About for the development provenance and author context behind the evidence.
This overview may route to website-specific and integrated publication-system evidence, but it does not replace the formal papers or present private material as publicly inspectable. Each Capability Evidence paper remains the formal source for its own bounded evidence object and limitations.
This page supports bounded public-stage capability evaluation only. It does not establish deployment readiness or disclose the protected method. Implementation-level review belongs in Protected-stage discussion.
Page 15 of 31