CIM → PIM transformation rules
CIM→PIM refinement is the semantic bridge from business/domain language to provider-independent serverless architecture.
Follow the concern pages below. Each page documents every ETL rule in its source module, including guards, target types, secondary objects, trace identifiers, manual decisions, and repair guidance.
| Concern | Rules | Page |
|---|---|---|
| Behavior Contracts | 7 | Behavior Contracts |
| Boundaries Security | 5 | Boundaries Security |
| Domain Data | 7 | Domain Data |
| Integration Deployment | 2 | Integration Deployment |
| Process Policy | 20 | Process Policy |
| Root Scaffolding | 7 | Root Scaffolding |
How to investigate a missing target
Start with the source element and the guard. Then check whether an earlier rule should have created the correspondence used by this rule, whether a post phase is responsible for late materialization, and whether the trace/readiness model contains a manual decision. A missing target is often an intentional unsupported/provider-choice hand-off, not necessarily a parser error.