Architecture, business, resilience, and operational policies

Policy concepts capture non-functional and behavioral decisions that shape reliability, security, cost, observability, and runtime behavior.

Source: mde/metamodels/pim/pim-policy.emf.

ArchitecturePolicy

An abstract architecture policy concept. Use one of its concrete subtypes when creating a model instance; the shared attributes and relationships defined here still apply.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
policyScope	String [1]	Records boundary within which policy scope is interpreted for architecture policy. It keeps isolation and ownership decisions explicit during review and transformation, so later steps do not have to infer it. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: orders.
productionRequired	Boolean [1]	Records whether production required applies to architecture policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	Either true or false. Example: true.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
attachedTo → PolicyTarget	reference, [*]	References the policy target element(s) used as attached to by this architecture policy; the target may be shared elsewhere in the model.

PolicySetting

An abstract policy setting concept. Use one of its concrete subtypes when creating a model instance; the shared attributes and relationships defined here still apply.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

This class declares no attributes of its own. It inherits the attributes of its supertype, if any.

Relationships

This class declares no direct relationships.

DataProtectionPolicy

Represents data protection policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
classification	String [1]	Records the data-sensitivity classification for classification in data protection policy. It keeps privacy, encryption, and access decisions explicit during review and transformation, so later steps do not have to infer them. Semantic validation: ProtectedDataHasRetentionDecision (protected data has retention decision) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. ClassifiedDataNeedsProtectionDecision (classified data needs protection decision) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule DataClassification2DataProtectionPolicy in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy. ETL rule PrivacyConstraint2Policies in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: STANDARD.
encryptionRequired	Boolean [1]	Records whether encryption required applies to data protection policy. It preserves an explicit architectural or governance decision through review and transformation, so later steps do not have to infer it. Semantic validation: ClassifiedDataNeedsProtectionDecision (classified data needs protection decision) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule DataClassification2DataProtectionPolicy in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy. ETL rule PrivacyConstraint2Policies in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy.	Either true or false. Example: true.
maskingRequired	Boolean [1]	For a data protection policy, the model records whether masking required applies. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: ClassifiedDataNeedsProtectionDecision (classified data needs protection decision) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule DataClassification2DataProtectionPolicy in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy. ETL rule PrivacyConstraint2Policies in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy.	Either true or false. Example: true.
tokenizationRequired	Boolean [1]	Records whether tokenization required applies to data protection policy. It preserves an explicit architectural or governance decision through review and transformation, so later steps do not have to infer it. Semantic validation: ClassifiedDataNeedsProtectionDecision (classified data needs protection decision) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule DataClassification2DataProtectionPolicy in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy.	Either true or false. Example: true.
accessAuditRequired	Boolean [1]	Records whether access audit required applies to data protection policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: ClassifiedDataNeedsProtectionDecision (classified data needs protection decision) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule DataClassification2DataProtectionPolicy in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy. ETL rule PrivacyConstraint2Policies in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy.	Either true or false. Example: true.
deletionRequired	Boolean [1]	Stores the data-lifecycle rule for deletion required on the data protection policy. The field records retention and data-lifecycle controls as an explicit, reviewable input. Transformation role: ETL rule DataClassification2DataProtectionPolicy in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy. ETL rule PrivacyConstraint2Policies in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy.	Either true or false. Example: true.
retentionPeriod	String [1]	For a data protection policy, the model records the data-lifecycle rule for retention period. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: ProtectedDataHasRetentionDecision (protected data has retention decision) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule DataClassification2DataProtectionPolicy in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy. ETL rule PrivacyConstraint2Policies in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Data Protection Policy Retention Period.
residencyRequirement	String [1]	For a data protection policy, the model records the residency requirement value. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Transformation role: ETL rule DataClassification2DataProtectionPolicy in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy. ETL rule PrivacyConstraint2Policies in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining DataProtectionPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Data Protection Policy Residency Requirement.

Relationships

This class declares no direct relationships.

DataQualityPolicy

Represents data quality policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
validationRequired	Boolean [1]	Records whether validation required applies to data quality policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: DataQualityPolicyHasMeasurementRule (data quality policy has measurement rule) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule DataQualityNfr2SchemaConstraintAndReadiness in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining DataQualityPolicy.	Either true or false. Example: true.
completenessCheckRequired	Boolean [1]	For a data quality policy, the model records whether completeness check required applies. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: DataQualityPolicyHasMeasurementRule (data quality policy has measurement rule) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule DataQualityNfr2SchemaConstraintAndReadiness in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining DataQualityPolicy.	Either true or false. Example: true.
freshnessCheckRequired	Boolean [1]	Records whether freshness check required applies to data quality policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: DataQualityPolicyHasMeasurementRule (data quality policy has measurement rule) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule DataQualityNfr2SchemaConstraintAndReadiness in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining DataQualityPolicy.	Either true or false. Example: true.
duplicateDetectionRequired	Boolean [1]	Records whether duplicate detection required applies to data quality policy. The field records an explicit architectural or governance decision as an explicit, reviewable input. Semantic validation: DataQualityPolicyHasMeasurementRule (data quality policy has measurement rule) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule DataQualityNfr2SchemaConstraintAndReadiness in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining DataQualityPolicy.	Either true or false. Example: true.
qualityDimensions	String [1]	Records the quality dimensions value for data quality policy. It keeps this decision explicit during review and transformation, so later steps do not have to infer it. Semantic validation: DataQualityPolicyHasMeasurementRule (data quality policy has measurement rule) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule DataQualityNfr2SchemaConstraintAndReadiness in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining DataQualityPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Data Quality Policy Quality Dimensions.
measurementRule	String [1]	Records expression or rule that governs measurement rule for data quality policy. It keeps this decision explicit during review and transformation, so later steps do not have to infer it. Semantic validation: DataQualityPolicyHasMeasurementRule (data quality policy has measurement rule) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule DataQualityNfr2SchemaConstraintAndReadiness in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining DataQualityPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: $.status == 'READY'.

Relationships

This class declares no direct relationships.

CompliancePolicy

Represents compliance policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
regulation	String [1]	Records the regulation value for compliance policy. It keeps this decision explicit during review and transformation, so later steps do not have to infer it. Transformation role: ETL rule ComplianceConstraint2CompliancePolicy in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining CompliancePolicy. ETL rule GenericComplianceNfr2CompliancePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining CompliancePolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Compliance Policy Regulation.
controlId	String [1]	Records stable name/key/code used for control id for compliance policy. It keeps this decision explicit during review and transformation, so later steps do not have to infer it. Transformation role: ETL rule ComplianceConstraint2CompliancePolicy in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining CompliancePolicy. ETL rule GenericComplianceNfr2CompliancePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining CompliancePolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: order-123.
evidenceType	String [1]	For a compliance policy, the model records the controlled classification or strategy represented by evidence type. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Transformation role: ETL rule ComplianceConstraint2CompliancePolicy in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining CompliancePolicy. ETL rule GenericComplianceNfr2CompliancePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining CompliancePolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: BUSINESS.
auditReportRequired	Boolean [1]	Records whether audit report required applies to compliance policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Transformation role: ETL rule ComplianceConstraint2CompliancePolicy in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining CompliancePolicy. ETL rule GenericComplianceNfr2CompliancePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining CompliancePolicy.	Either true or false. Example: true.

Relationships

This class declares no direct relationships.

BusinessRule

Represents business rule in the PIM vocabulary. It specializes TraceableElement, PolicyTarget with the details needed for this modeling concern.

Direct supertypes: TraceableElement, PolicyTarget. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
naturalLanguageRule	String [1]	Records the expression or rule that governs natural language rule for the business rule. This keeps the decision explicit even when the element's class or relationships remain unchanged. Transformation role: ETL rule Requirement2BusinessRule in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining BusinessRule. ETL rule BusinessGoal2BusinessRule in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining BusinessRule.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: $.status == 'READY'.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
expression → Expression	containment, [?]	Contains the expression element(s) that make up this business rule; the contained objects belong to this model element.
inputSchemas → Schema	reference, [*]	References the schema element(s) used as input schemas by this business rule; the target may be shared elsewhere in the model.
outputSchemas → Schema	reference, [*]	References the schema element(s) used as output schemas by this business rule; the target may be shared elsewhere in the model.
enforcedBy → FunctionTarget	reference, [*]	References the function target element(s) used as enforced by by this business rule; the target may be shared elsewhere in the model.

DecisionModel

Represents decision model in the PIM vocabulary. It specializes TraceableElement, DeployableElement, PolicyTarget with the details needed for this modeling concern.

Direct supertypes: TraceableElement, DeployableElement, PolicyTarget. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
hitPolicy	String [1]	For a decision model, the model records the hit policy value. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Transformation role: ETL rule DecisionTable2DecisionModel in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining DecisionModel. ETL rule DecisionModel2PsmMetadata in mde/transformations/pim-to-awspsm/contracts-external-policy.etl reads or derives this feature while refining DecisionModel.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: STANDARD.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
rules → DecisionRule	containment, [+]	Contains the decision rule element(s) that make up this decision model; the contained objects belong to this model element.
inputs → Schema	reference, [*]	References the schema element(s) used as inputs by this decision model; the target may be shared elsewhere in the model.
outputs → Schema	reference, [*]	References the schema element(s) used as outputs by this decision model; the target may be shared elsewhere in the model.

DecisionRule

Represents decision rule in the PIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

This class declares no attributes of its own. It inherits the attributes of its supertype, if any.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
condition → Expression	containment, [1]	Contains the expression element(s) that make up this decision rule; the contained objects belong to this model element.
outcome → Expression	containment, [1]	Contains the expression element(s) that make up this decision rule; the contained objects belong to this model element.

ResiliencePolicy

Represents resilience policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
retryEnabled	Boolean [1]	For a resilience policy, the model records whether retry enabled applies. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Transformation role: ETL rule AvailabilityReliabilityNfr2ResiliencePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ResiliencePolicy.	Either true or false. Example: true.
deadLetterRequired	Boolean [1]	Records whether dead letter required applies to resilience policy. The field records an explicit architectural or governance decision as an explicit, reviewable input. Transformation role: ETL rule AvailabilityReliabilityNfr2ResiliencePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ResiliencePolicy.	Either true or false. Example: true.
fallbackRequired	Boolean [1]	For a resilience policy, the model records whether fallback required applies. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Transformation role: ETL rule AvailabilityReliabilityNfr2ResiliencePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ResiliencePolicy.	Either true or false. Example: true.
circuitBreakerRequired	Boolean [1]	Records whether circuit breaker required applies to resilience policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Transformation role: ETL rule AvailabilityReliabilityNfr2ResiliencePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ResiliencePolicy.	Either true or false. Example: true.
timeoutRequired	Boolean [1]	Records whether timeout required applies to resilience policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Transformation role: ETL rule AvailabilityReliabilityNfr2ResiliencePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ResiliencePolicy.	Either true or false. Example: true.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
retry → RetryPolicy	containment, [?]	Contains the retry policy element(s) that make up this resilience policy; the contained objects belong to this model element.
deadLetter → DeadLetterPolicy	containment, [?]	Contains the dead letter policy element(s) that make up this resilience policy; the contained objects belong to this model element.
timeout → TimeoutPolicy	reference, [?]	References the timeout policy element(s) used as timeout by this resilience policy; the target may be shared elsewhere in the model.

RetryPolicy

Represents retry policy in the PIM vocabulary. It specializes PolicySetting with the details needed for this modeling concern.

Direct supertypes: PolicySetting. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
maxAttempts	Integer [1]	Stores the max attempts value on the retry policy. The field records an operational boundary explicitly instead of leaving it to provider defaults. Semantic validation: RetryPolicyBounded (retry policy bounded) in mde/validation/pim/rules/policies.evl the related value or object must be explicitly provided. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/contracts.eol.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
initialDelaySeconds	Integer [1]	Stores the initial delay seconds duration or limit, expressed in seconds on the retry policy. The field records an operational boundary explicitly instead of leaving it to provider defaults. Semantic validation: RetryBackoffIsValid (retry backoff is valid) in mde/validation/pim/rules/policies.evl the value must remain absent in this modeling situation.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
backoffRate	Double [1]	Stores the backoff rate value on the retry policy. The field records an operational boundary explicitly instead of leaving it to provider defaults. Semantic validation: RetryBackoffIsValid (retry backoff is valid) in mde/validation/pim/rules/policies.evl the value must remain absent in this modeling situation. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/contracts.eol.	A numeric Double value; use the unit or boundary documented for this attribute. Example: 1.
maxDelaySeconds	Integer [1]	Stores the max delay seconds duration or limit, expressed in seconds on the retry policy. The field records an operational boundary explicitly instead of leaving it to provider defaults. Semantic validation: RetryBackoffIsValid (retry backoff is valid) in mde/validation/pim/rules/policies.evl the value must remain absent in this modeling situation. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/contracts.eol.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
retryableErrors	String [*]	Records the retryable errors value for retry policy. It keeps this decision explicit during review and transformation, so later steps do not have to infer it. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A collection of values. Example: [Retry Policy Retryable Errors, Retry Policy Retryable Errors-2].
nonRetryableErrors	String [*]	For a retry policy, the model records the non retryable errors value. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A collection of values. Example: [Retry Policy Non Retryable Errors, Retry Policy Non Retryable Errors-2].

Relationships

This class declares no direct relationships.

DeadLetterPolicy

Represents dead letter policy in the PIM vocabulary. It specializes PolicySetting with the details needed for this modeling concern.

Direct supertypes: PolicySetting. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
required	Boolean [1]	Records whether required applies to dead letter policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: RequiredDeadLetterPolicyHasChannel (required dead letter policy has channel) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition.	Either true or false. Example: true.
reason	String [1]	Stores the reasoning behind reason on the dead letter policy. The field records design review and decision traceability as an explicit, reviewable input. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Dead Letter Policy Reason.
retentionPeriod	String [1]	Records data-lifecycle rule for retention period for dead letter policy. It keeps retention and data-lifecycle controls explicit during review and transformation, so later steps do not have to infer it. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Dead Letter Policy Retention Period.
alarmRequired	Boolean [1]	For a dead letter policy, the model records whether alarm required applies. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	Either true or false. Example: true.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
deadLetterChannel → EventCarrier	reference, [?]	References the event carrier element(s) used as dead letter channel by this dead letter policy; the target may be shared elsewhere in the model.

TimeoutPolicy

Represents timeout policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
timeoutSeconds	Integer [1]	Records timeout seconds duration or limit, expressed in seconds for timeout policy. It keeps an operational boundary that should not be left to provider defaults explicit during review and transformation, so later steps do not have to infer it. Semantic validation: TimeoutPolicyIsPositive (timeout policy is positive) in mde/validation/pim/rules/policies.evl the related value or object must be explicitly provided. Transformation role: ETL rule TemporalConstraint2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining TimeoutPolicy. ETL rule TemporalConstraint2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl reads or derives this feature while refining TimeoutPolicy.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 30.
clientTimeoutSeconds	Integer [1]	For a timeout policy, the model records the client timeout seconds duration or limit, expressed in seconds. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: TimeoutPolicyIsPositive (timeout policy is positive) in mde/validation/pim/rules/policies.evl the value must remain absent in this modeling situation. Transformation role: ETL rule TemporalConstraint2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining TimeoutPolicy. ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining TimeoutPolicy.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 30.

Relationships

This class declares no direct relationships.

IdempotencyPolicy

Represents idempotency policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
keySource	String [1]	Records the origin/source selected for key source for the idempotency policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: IdempotencyKeyRequired (idempotency key required) in mde/validation/pim/rules/policies.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: orderId.
storeRequired	Boolean [1]	Records whether store required applies to idempotency policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: IdempotencyStoreDecisionRecommended (idempotency store decision recommended) in mde/validation/pim/rules/policies.evl the value must be present and non-blank.	Either true or false. Example: true.
scope	String [1]	Records the boundary within which scope is interpreted for the idempotency policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: IdempotencyStoreDecisionRecommended (idempotency store decision recommended) in mde/validation/pim/rules/policies.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: orders.
expirationSeconds	Integer [1]	Records the expiration seconds duration or limit, expressed in seconds for the idempotency policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: IdempotencyStoreDecisionRecommended (idempotency store decision recommended) in mde/validation/pim/rules/policies.evl the value must be present and non-blank.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
appliesToRetries	Boolean [1]	For a idempotency policy, the model records whether applies to retries applies. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	Either true or false. Example: false.
appliesToDuplicateRequests	Boolean [1]	Records whether applies to duplicate requests applies to idempotency policy. It preserves an explicit architectural or governance decision through review and transformation, so later steps do not have to infer it. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	Either true or false. Example: false.

Relationships

This class declares no direct relationships.

ConcurrencyPolicy

Represents concurrency policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
maxConcurrency	Integer [1]	For a concurrency policy, the model records the max concurrency value. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: ConcurrencyPolicyShouldExplainScaling (concurrency policy should explain scaling) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ConcurrencyPolicy.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
reservedConcurrencyHint	Integer [1]	Records the reserved concurrency hint value for concurrency policy. It keeps an operational boundary that should not be left to provider defaults explicit during review and transformation, so later steps do not have to infer it. Semantic validation: ConcurrencyPolicyShouldExplainScaling (concurrency policy should explain scaling) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ConcurrencyPolicy.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
burstAssumption	Integer [1]	Stores the burst assumption value on the concurrency policy. The field records an operational boundary explicitly instead of leaving it to provider defaults. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ConcurrencyPolicy.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
perSourceLimitRequired	Boolean [1]	Records the origin/source selected for per source limit required for the concurrency policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ConcurrencyPolicy.	Either true or false. Example: true.
scalingRationale	String [1]	Records the reasoning behind scaling rationale for the concurrency policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: ConcurrencyPolicyShouldExplainScaling (concurrency policy should explain scaling) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ConcurrencyPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: The choice protects the business outcome while keeping the design independently deployable..

Relationships

This class declares no direct relationships.

RateLimitPolicy

Represents rate limit policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
requestsPerSecond	Integer [1]	Stores the requests per second value on the rate limit policy. The field records an operational boundary explicitly instead of leaving it to provider defaults. Semantic validation: RateLimitPolicyIsPositive (rate limit policy is positive) in mde/validation/pim/rules/policies.evl the related value or object must be explicitly provided. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining RateLimitPolicy.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
burstLimit	Integer [1]	Stores the burst limit value on the rate limit policy. The field records an operational boundary explicitly instead of leaving it to provider defaults. Semantic validation: RateLimitPolicyIsPositive (rate limit policy is positive) in mde/validation/pim/rules/policies.evl the value must remain absent in this modeling situation. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining RateLimitPolicy.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
keyBy	String [1]	Records the key by value for the rate limit policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining RateLimitPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: orderId.
clientSpecific	Boolean [1]	For a rate limit policy, the model records whether client specific applies. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining RateLimitPolicy.	Either true or false. Example: false.

Relationships

This class declares no direct relationships.

BatchPolicy

Represents batch policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
batchSize	Integer [1]	Records the batch size value for the batch policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: BatchPolicyHasSizeAndFailureDecision (batch policy has size and failure decision) in mde/validation/pim/rules/policies.evl the related value or object must be explicitly provided. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/cfn.eol.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
maxBatchingWindowSeconds	Integer [1]	Records the max batching window seconds duration or limit, expressed in seconds for the batch policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
parallelizationFactor	Integer [1]	For a batch policy, the model records the parallelization factor value. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/cfn.eol.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
decisionRationale	String [1]	Records the reasoning behind decision rationale for the batch policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: BatchPolicyNeedsRationaleForNoPartialFailureHandling (batch policy needs rationale for no partial failure handling) in mde/validation/pim/rules/policies.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: The choice protects the business outcome while keeping the design independently deployable..
bisectOnError	Decision [1]	Records the controlled classification or strategy for bisect on error in the batch policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	Exactly one of: UNDECIDED, REQUIRED, NOT_REQUIRED, ACCEPTED, NEEDS_REVIEW, GENERATOR_OWNED. Example: UNDECIDED.
partialFailureHandling	Decision [1]	For a batch policy, the model records the controlled classification or strategy represented by partial failure handling. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: BatchPolicyHasSizeAndFailureDecision (batch policy has size and failure decision) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. BatchPolicyNeedsRationaleForNoPartialFailureHandling (batch policy needs rationale for no partial failure handling) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition.	Exactly one of: UNDECIDED, REQUIRED, NOT_REQUIRED, ACCEPTED, NEEDS_REVIEW, GENERATOR_OWNED. Example: UNDECIDED.

Relationships

This class declares no direct relationships.

OrderingPolicy

Represents ordering policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
orderingKey	String [1]	Records precedence value for ordering key for ordering policy. It keeps deterministic ordering or precedence explicit during review and transformation, so later steps do not have to infer it. Transformation role: ETL rule TemporalConstraint2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining OrderingPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: orderId.
strictOrderingRequired	Boolean [1]	Stores the precedence value for strict ordering required on the ordering policy. The field records deterministic ordering or precedence as an explicit, reviewable input. Transformation role: ETL rule TemporalConstraint2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining OrderingPolicy. ETL rule TemporalConstraint2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl reads or derives this feature while refining OrderingPolicy.	Either true or false. Example: true.
orderingRequirement	OrderingRequirement [1]	Records precedence value for ordering requirement for ordering policy. It keeps deterministic ordering or precedence explicit during review and transformation, so later steps do not have to infer it. Transformation role: ETL rule TemporalConstraint2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining OrderingPolicy.	Exactly one of: NONE, PER_KEY, GLOBAL. Example: NONE.

Relationships

This class declares no direct relationships.

CachePolicy

Represents cache policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
cacheRequired	Boolean [1]	Records whether cache required applies to cache policy. It preserves an explicit architectural or governance decision through review and transformation, so later steps do not have to infer it. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining CachePolicy.	Either true or false. Example: true.
ttlSeconds	Integer [1]	Records the ttl seconds duration or limit, expressed in seconds for the cache policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining CachePolicy.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
cacheKey	String [1]	Records stable name/key/code used for cache key for cache policy. It keeps this decision explicit during review and transformation, so later steps do not have to infer it. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining CachePolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: orderId.
privateCache	Boolean [1]	Records whether private cache applies to cache policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Transformation role: ETL rule PerformanceNfr2TimeoutPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining CachePolicy.	Either true or false. Example: false.

Relationships

This class declares no direct relationships.

BackupPolicy

Represents backup policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
backupRequired	Boolean [1]	Records whether backup required applies to backup policy. It preserves an explicit architectural or governance decision through review and transformation, so later steps do not have to infer it. Semantic validation: RequiredBackupPolicyHasObjectives (required backup policy has objectives) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule AvailabilityReliabilityNfr2ResiliencePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining BackupPolicy.	Either true or false. Example: true.
backupFrequency	String [1]	Stores the backup frequency value on the backup policy. The field keeps the model explicit and reviewable during review and transformation instead of leaving the decision to an inferred default. Semantic validation: RequiredBackupPolicyHasObjectives (required backup policy has objectives) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule AvailabilityReliabilityNfr2ResiliencePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining BackupPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: PT5M.
recoveryPointObjective	String [1]	Stores the recovery point objective value on the backup policy. The field keeps the model explicit and reviewable during review and transformation instead of leaving the decision to an inferred default. Semantic validation: RequiredBackupPolicyHasObjectives (required backup policy has objectives) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule AvailabilityReliabilityNfr2ResiliencePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining BackupPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Backup Policy Recovery Point Objective.
recoveryTimeObjective	String [1]	Records the recovery time objective value for the backup policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: RequiredBackupPolicyHasObjectives (required backup policy has objectives) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule AvailabilityReliabilityNfr2ResiliencePolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining BackupPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Backup Policy Recovery Time Objective.

Relationships

This class declares no direct relationships.

RetentionPolicy

Represents retention policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
retentionPeriod	String [1]	Records the data-lifecycle rule for retention period for the retention policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: RetentionPolicyHasPeriod (retention policy has period) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule PrivacyConstraint2Policies in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining RetentionPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Retention Policy Retention Period.
deletionAfterRetention	Boolean [1]	Stores the data-lifecycle rule for deletion after retention on the retention policy. The field records retention and data-lifecycle controls as an explicit, reviewable input. Transformation role: ETL rule PrivacyConstraint2Policies in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining RetentionPolicy.	Either true or false. Example: false.
legalHoldPossible	Boolean [1]	Records whether legal hold possible applies to retention policy. It preserves an explicit architectural or governance decision through review and transformation, so later steps do not have to infer it. Transformation role: ETL rule PrivacyConstraint2Policies in mde/transformations/cim-to-pim/domain-data.etl assigns or materializes this feature while refining RetentionPolicy.	Either true or false. Example: false.

Relationships

This class declares no direct relationships.

CostPolicy

Represents cost policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
budget	String [1]	For a cost policy, the model records the budget value. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Transformation role: ETL rule CostNfr2CostPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining CostPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Cost Policy Budget.
costDriver	String [1]	Stores the cost driver value on the cost policy. The field keeps the model explicit and reviewable during review and transformation instead of leaving the decision to an inferred default. Transformation role: ETL rule CostNfr2CostPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining CostPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Cost Policy Cost Driver.
optimizationIntent	String [1]	Stores the optimization intent value on the cost policy. The field keeps the model explicit and reviewable during review and transformation instead of leaving the decision to an inferred default. Transformation role: ETL rule CostNfr2CostPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining CostPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Cost Policy Optimization Intent.
alarmsRequired	Boolean [1]	Records whether alarms required applies to cost policy. The field records an explicit architectural or governance decision as an explicit, reviewable input. Transformation role: ETL rule CostNfr2CostPolicy in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining CostPolicy.	Either true or false. Example: true.

Relationships

This class declares no direct relationships.

ObservabilityConfig

Represents observability config in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
loggingEnabled	Boolean [1]	Records whether logging enabled applies to observability config. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: ObservabilityShouldEnableSignals (observability should enable signals) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule AuditOperabilityNfr2Observability in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ObservabilityConfig.	Either true or false. Example: true.
metricsEnabled	Boolean [1]	Records whether metrics enabled applies to observability config. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: ObservabilityShouldEnableSignals (observability should enable signals) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule AuditOperabilityNfr2Observability in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ObservabilityConfig.	Either true or false. Example: true.
tracingEnabled	Boolean [1]	For a observability config, the model records whether tracing enabled applies. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: ObservabilityShouldEnableSignals (observability should enable signals) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule AuditOperabilityNfr2Observability in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ObservabilityConfig.	Either true or false. Example: true.
alarmsEnabled	Boolean [1]	For a observability config, the model records whether alarms enabled applies. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: ObservabilityShouldEnableSignals (observability should enable signals) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition. Transformation role: ETL rule AuditOperabilityNfr2Observability in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ObservabilityConfig.	Either true or false. Example: true.
dashboardRequired	Boolean [1]	Records whether dashboard required applies to observability config. The field records an explicit architectural or governance decision as an explicit, reviewable input. Transformation role: ETL rule AuditOperabilityNfr2Observability in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ObservabilityConfig.	Either true or false. Example: true.
correlationIdRequired	Boolean [1]	Records whether correlation id required applies to observability config. It preserves an explicit architectural or governance decision through review and transformation, so later steps do not have to infer it. Semantic validation: ProductionObservabilityNeedsCorrelation (production observability needs correlation) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule AuditOperabilityNfr2Observability in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ObservabilityConfig.	Either true or false. Example: true.
correlationIdField	String [1]	For a observability config, the model records the data location or endpoint represented by correlation id field. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: ProductionObservabilityNeedsCorrelation (production observability needs correlation) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule AuditOperabilityNfr2Observability in mde/transformations/cim-to-pim/process-policy.etl assigns or materializes this feature while refining ObservabilityConfig.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Observability Config Correlation Id Field.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
logging → LoggingPolicy	containment, [?]	Contains the logging policy element(s) that make up this observability config; the contained objects belong to this model element.
metrics → MetricPolicy	containment, [*]; opposite observability	Contains the metric policy element(s) that make up this observability config; the contained objects belong to this model element.
tracing → TracingPolicy	containment, [?]	Contains the tracing policy element(s) that make up this observability config; the contained objects belong to this model element.
alerts → AlertPolicy	containment, [*]; opposite observability	Contains the alert policy element(s) that make up this observability config; the contained objects belong to this model element.
slos → Slo	containment, [*]; opposite observability	Contains the slo element(s) that make up this observability config; the contained objects belong to this model element.

LoggingPolicy

Represents logging policy in the PIM vocabulary. It specializes PolicySetting with the details needed for this modeling concern.

Direct supertypes: PolicySetting. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
logFormat	String [1]	Stores the serialization/content format for log format on the logging policy. The field keeps the model explicit and reviewable during review and transformation instead of leaving the decision to an inferred default. Semantic validation: StructuredLoggingNeedsFormat (structured logging needs format) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/cfn.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Logging Policy Log Format.
logLevel	String [1]	Records the log level value for logging policy. It keeps this decision explicit during review and transformation, so later steps do not have to infer it. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: INFO.
structuredLogging	Boolean [1]	Records whether structured logging applies to logging policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: StructuredLoggingNeedsFormat (structured logging needs format) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition.	Either true or false. Example: false.
includeCorrelationId	Boolean [1]	Records whether include correlation id applies to logging policy. The field records an explicit architectural or governance decision as an explicit, reviewable input. Semantic validation: LoggingShouldIncludeCorrelationId (logging should include correlation id) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition.	Either true or false. Example: false.
maskSensitiveData	Boolean [1]	Records the data-sensitivity classification for mask sensitive data in the logging policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	Either true or false. Example: false.
retentionPeriod	String [1]	Stores the data-lifecycle rule for retention period on the logging policy. The field records retention and data-lifecycle controls as an explicit, reviewable input. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Logging Policy Retention Period.

Relationships

This class declares no direct relationships.

MetricPolicy

Represents metric policy in the PIM vocabulary. It specializes PolicySetting with the details needed for this modeling concern.

Direct supertypes: PolicySetting. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
metricName	String [1]	Records stable name/key/code used for metric name for metric policy. It keeps this decision explicit during review and transformation, so later steps do not have to infer it. Semantic validation: MetricPolicyShouldNameMetricAndUnit (metric policy should name metric and unit) in mde/validation/pim/rules/policies.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: MetricPolicyExample.
unit	String [1]	For a metric policy, the model records the unit value. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: MetricPolicyShouldNameMetricAndUnit (metric policy should name metric and unit) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/awspsm2artifacts.egx. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/paths.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: milliseconds.
statistic	String [1]	For a metric policy, the model records the statistic value. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: MetricPolicyShouldNameMetricAndUnit (metric policy should name metric and unit) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/cfn.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Metric Policy Statistic.
businessMetric	Boolean [1]	For a metric policy, the model records whether business metric applies. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	Either true or false. Example: false.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
observability → ObservabilityConfig	reference; read-only, [1]; opposite metrics	References the observability config element(s) used as observability by this metric policy; the target may be shared elsewhere in the model.
dimensions → MetricDimension	containment, [*]; opposite metric	Contains the metric dimension element(s) that make up this metric policy; the contained objects belong to this model element.

MetricDimension

Represents metric dimension in the PIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
key	String [1]	Records the stable name/key/code used for key for the metric dimension. This keeps the decision explicit even when the element's class or relationships remain unchanged. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/awspsm2artifacts.egx. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/cfn.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: orderId.
valueExpression	String [1]	Records the expression or rule that governs value expression for the metric dimension. This keeps the decision explicit even when the element's class or relationships remain unchanged. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: $.status == 'READY'.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
metric → MetricPolicy	reference; read-only, [1]; opposite dimensions	References the metric policy element(s) used as metric by this metric dimension; the target may be shared elsewhere in the model.

TracingPolicy

Represents tracing policy in the PIM vocabulary. It specializes PolicySetting with the details needed for this modeling concern.

Direct supertypes: PolicySetting. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
tracingRequired	Boolean [1]	Records whether tracing required applies to tracing policy. It preserves an explicit architectural or governance decision through review and transformation, so later steps do not have to infer it. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	Either true or false. Example: true.
samplingPolicy	String [1]	Records the sampling policy value for the tracing policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: STANDARD.
propagateTraceContext	Boolean [1]	Records whether propagate trace context applies to tracing policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	Either true or false. Example: false.

Relationships

This class declares no direct relationships.

AlertPolicy

Represents alert policy in the PIM vocabulary. It specializes PolicySetting with the details needed for this modeling concern.

Direct supertypes: PolicySetting. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
metricName	String [1]	Records stable name/key/code used for metric name for alert policy. It keeps this decision explicit during review and transformation, so later steps do not have to infer it. Semantic validation: AlertPolicyIsActionable (alert policy is actionable) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule AlertPolicy2CloudWatchAlarm in mde/transformations/pim-to-awspsm/contracts-external-policy.etl assigns or materializes this feature while refining AlertPolicy. ETL rule AlertPolicy2CloudWatchAlarm in mde/transformations/pim-to-awspsm/contracts-external-policy.etl reads or derives this feature while refining AlertPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: AlertPolicyExample.
condition	String [1]	Records the expression or rule that governs condition for the alert policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: AlertPolicyIsActionable (alert policy is actionable) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule AlertPolicy2CloudWatchAlarm in mde/transformations/pim-to-awspsm/contracts-external-policy.etl assigns or materializes this feature while refining AlertPolicy.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: $.status == 'READY'.
threshold	String [1]	Records the threshold value for alert policy. It keeps this decision explicit during review and transformation, so later steps do not have to infer it. Semantic validation: AlertPolicyIsActionable (alert policy is actionable) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Transformation role: ETL rule AlertPolicy2CloudWatchAlarm in mde/transformations/pim-to-awspsm/contracts-external-policy.etl assigns or materializes this feature while refining AlertPolicy. ETL rule AlertPolicy2CloudWatchAlarm in mde/transformations/pim-to-awspsm/contracts-external-policy.etl reads or derives this feature while refining AlertPolicy. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/cfn.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Alert Policy Threshold.
evaluationPeriods	Integer [1]	Stores the evaluation periods value on the alert policy. The field records an operational boundary explicitly instead of leaving it to provider defaults. Transformation role: ETL rule AlertPolicy2CloudWatchAlarm in mde/transformations/pim-to-awspsm/contracts-external-policy.etl assigns or materializes this feature while refining AlertPolicy. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/cfn.eol.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
severity	String [1]	Records the severity value for the alert policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Alert Policy Severity.
notificationTarget	String [1]	Stores the destination selected for notification target on the alert policy. The field keeps the model explicit and reviewable during review and transformation instead of leaving the decision to an inferred default. Semantic validation: AlertPolicyIsActionable (alert policy is actionable) in mde/validation/pim/rules/policies.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Alert Policy Notification Target.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
conditionExpression → Expression	containment, [?]	Contains the expression element(s) that make up this alert policy; the contained objects belong to this model element.
observability → ObservabilityConfig	reference; read-only, [1]; opposite alerts	References the observability config element(s) used as observability by this alert policy; the target may be shared elsewhere in the model.

Slo

Represents slo in the PIM vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Direct supertypes: TraceableElement. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
objectiveName	String [1]	Stores the stable name/key/code used for objective name on the slo. The field keeps the model explicit and reviewable during review and transformation instead of leaving the decision to an inferred default. Semantic validation: SloShouldBeMeasurable (slo should be measurable) in mde/validation/pim/rules/policies.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: SloExample.
metric	String [1]	Stores the metric value on the slo. The field keeps the model explicit and reviewable during review and transformation instead of leaving the decision to an inferred default. Semantic validation: SloShouldBeMeasurable (slo should be measurable) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/templates/docs/operations.egl.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Slo Metric.
target	String [1]	Records destination selected for target for slo. It keeps this decision explicit during review and transformation, so later steps do not have to infer it. Semantic validation: SloShouldBeMeasurable (slo should be measurable) in mde/validation/pim/rules/policies.evl the value must be present and non-blank. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/awspsm2artifacts.egx. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/cfn.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Slo Target.
measurementWindow	String [1]	For a slo, the model records the measurement window value. Keeping the fact with its owning element lets validation and refinement inspect it before artifact generation. Semantic validation: SloShouldBeMeasurable (slo should be measurable) in mde/validation/pim/rules/policies.evl the value must be present and non-blank.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Slo Measurement Window.
errorBudgetPolicy	String [1]	Records the error budget policy value for the slo. This keeps the decision explicit even when the element's class or relationships remain unchanged. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: STANDARD.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
observability → ObservabilityConfig	reference; read-only, [1]; opposite slos	References the observability config element(s) used as observability by this slo; the target may be shared elsewhere in the model.

CorsPolicy

Represents cors policy in the PIM vocabulary. It specializes ArchitecturePolicy with the details needed for this modeling concern.

Direct supertypes: ArchitecturePolicy. Inherited attributes and marker capabilities are documented in the shared kernel; this section lists every attribute declared by this class.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
allowedOrigins	String [*]	Stores the allowed origins value on the cors policy. The field keeps the model explicit and reviewable during review and transformation instead of leaving the decision to an inferred default. Semantic validation: CredentialedCorsCannotUseWildcardOrigins (credentialed cors cannot use wildcard origins) in mde/validation/pim/rules/policies.evl the value participates in a membership or uniqueness check. CorsPolicyShouldDeclareMethodsAndHeaders (cors policy should declare methods and headers) in mde/validation/pim/rules/policies.evl the collection or referenced set must not be empty.	A collection of values. Example: [Cors Policy Allowed Origins, Cors Policy Allowed Origins-2].
allowedMethods	String [*]	Records the allowed methods value for the cors policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: CorsPolicyShouldDeclareMethodsAndHeaders (cors policy should declare methods and headers) in mde/validation/pim/rules/policies.evl the collection or referenced set must not be empty.	A collection of values. Example: [Cors Policy Allowed Methods, Cors Policy Allowed Methods-2].
allowedHeaders	String [*]	Records the allowed headers value for the cors policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. Semantic validation: CorsPolicyShouldDeclareMethodsAndHeaders (cors policy should declare methods and headers) in mde/validation/pim/rules/policies.evl the collection or referenced set must not be empty.	A collection of values. Example: [Cors Policy Allowed Headers, Cors Policy Allowed Headers-2].
exposedHeaders	String [*]	Records the exposed headers value for the cors policy. This keeps the decision explicit even when the element's class or relationships remain unchanged. The repository contains no direct EVL rule, ETL assignment, or artifact-generator read for this declared field. For now, it remains a model-level fact for review and future refinement.	A collection of values. Example: [Cors Policy Exposed Headers, Cors Policy Exposed Headers-2].
credentialsAllowed	Boolean [1]	Records whether credentials allowed applies to cors policy. It preserves an explicit architectural or governance decision through review and transformation, so later steps do not have to infer it. Semantic validation: CredentialedCorsCannotUseWildcardOrigins (credentialed cors cannot use wildcard origins) in mde/validation/pim/rules/policies.evl the feature participates in a semantic validation condition.	Either true or false. Example: true.
maxAgeSeconds	Integer [1]	Records max age seconds duration or limit, expressed in seconds for cors policy. It keeps an operational boundary that should not be left to provider defaults explicit during review and transformation, so later steps do not have to infer it. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/values.eol.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.

Relationships

This class declares no direct relationships.