| Rename and declare victory | A product is called a service or solution with no changed engineering claim. | Recover the promise, subjects, provider arrangement, and decision; stop if none changes. |
| Service-object collapse | Provider, API, promise, Method, Work, ticket, access, product, and result share one referent. | Apply A.6.P:4.11a; name each referent and direct relation. |
| Product-only architecture | Technical transfer is designed while continuing provision and recovery are assumed. | Develop provider Systems, capability, Work, interfaces, resources, evidence, and change with the product concept. |
| Provider as organization label | A company or department label is used as if it had identified the actual Agent for every provider Work occurrence. | Recognize the actual Systems and Agents; separate local SystemRole kinds, assignments, capabilities, and Work attribution. |
| Universal PSS recipe | One canvas, maturity ladder, or servitization sequence is made mandatory. | Generate context-relevant alternatives and compare them under the named use and evidence. |
| Guaranteed gain | Recurring revenue, sustainability, loyalty, or market growth is inferred from the arrangement form. | Return the commercial, financial, environmental, and use claims to evidence and specialist decisions. |
| Hidden burden transfer | Automation or self-service reduces provider effort while increasing user Work or excluding cases. | Trace Work, exception handling, affected Systems, and burden under each candidate. |
| Specialist absorption | Systems Engineering invents a neighboring result—for example, a price, legal duty, organization design, operating policy, or Platform Engineering result. | Obtain the specialist result and use it as an input with its authority boundary. |
| Frozen provider | Launch architecture is treated as sufficient for continuing provision. | Record configuration, update, maintenance, partner, migration, recovery, and reopen evidence. |