CUST.2:5 - Archetypal Grounding
In the analytical-service case, an initial request lists five features. The recovered differences are more useful:
| Request wording | Recovered difference | Disposition and join |
|---|---|---|
| “Use our login” | Existing identity interface, customer-specific credentials and access conditions. | Supported configuration, after access is supplied. |
| “Use our active-account count” | A different operational meaning, not only a column rename. | Semantic clarification and qualified mapping before computation. |
| “Run inside our network” | Hosting, monitoring and upgrade access differ together. | Bounded field inquiry; support conditions remain open. |
| “Add our report” | A local output with monthly preparation. | Funded local service; no automatic common feature. |
| “Respond immediately” | A new service obligation using scarce capacity. | Accept only a feasible response arrangement, otherwise narrow it. |
A developer who starts by adding five product features misses the status decision and continuing service obligations. A practitioner using the recovered differences can keep the supported identity path, investigate only hosting and preserve the report locally.
Change the setting to a public literacy service. “Translate the course” can hide language, reading ability, device access and facilitator help. Translation alone cannot repair missing devices or different prior capability. The same delta recovery separates the contributions while preserving the participant’s intended activity.