Shared kernel reference

The shared kernel supplies the cross-cutting vocabulary inherited by CIM, PIM, and AWS PSM elements. A class page in a DSML module lists its directly declared attributes; follow its supertype here for identity, traceability, lifecycle, expressions, readiness, and common value objects.

Source: mde/metamodels/shared/kernel.emf.

Enumerations

These literals are shared by all three DSMLs. They are closed values; use the spelling shown here.

Priority

Literal	Practical meaning
LOW	low as a shared lifecycle, traceability, validation, or readiness choice.
MEDIUM	medium as a shared lifecycle, traceability, validation, or readiness choice.
HIGH	high as a shared lifecycle, traceability, validation, or readiness choice.
CRITICAL	critical as a shared lifecycle, traceability, validation, or readiness choice.

Severity

Literal	Practical meaning
INFO	info as a shared lifecycle, traceability, validation, or readiness choice.
WARNING	warning as a shared lifecycle, traceability, validation, or readiness choice.
ERROR	error as a shared lifecycle, traceability, validation, or readiness choice.
CRITICAL	critical as a shared lifecycle, traceability, validation, or readiness choice.
BLOCKER	blocker as a shared lifecycle, traceability, validation, or readiness choice.

ConstraintStrength

Literal	Practical meaning
ADVISORY	advisory as a shared lifecycle, traceability, validation, or readiness choice.
RECOMMENDED	recommended as a shared lifecycle, traceability, validation, or readiness choice.
MANDATORY	mandatory as a shared lifecycle, traceability, validation, or readiness choice.
BLOCKING	blocking as a shared lifecycle, traceability, validation, or readiness choice.

LifecycleStatus

Literal	Practical meaning
DRAFT	draft as a shared lifecycle, traceability, validation, or readiness choice.
INCOMPLETE	incomplete as a shared lifecycle, traceability, validation, or readiness choice.
REVIEW_REQUIRED	review_required as a shared lifecycle, traceability, validation, or readiness choice.
APPROVED	approved as a shared lifecycle, traceability, validation, or readiness choice.
TRANSFORMATION_READY	transformation_ready as a shared lifecycle, traceability, validation, or readiness choice.
DEPLOYMENT_READY	deployment_ready as a shared lifecycle, traceability, validation, or readiness choice.
PRODUCTION_READY	production_ready as a shared lifecycle, traceability, validation, or readiness choice.
BLOCKED	blocked as a shared lifecycle, traceability, validation, or readiness choice.
DEPRECATED	deprecated as a shared lifecycle, traceability, validation, or readiness choice.

TraceConfidence

Literal	Practical meaning
LOW	low as a shared lifecycle, traceability, validation, or readiness choice.
MEDIUM	medium as a shared lifecycle, traceability, validation, or readiness choice.
HIGH	high as a shared lifecycle, traceability, validation, or readiness choice.
VERIFIED	verified as a shared lifecycle, traceability, validation, or readiness choice.
MANUAL	manual as a shared lifecycle, traceability, validation, or readiness choice.

TraceLinkType

Literal	Practical meaning
DERIVES_FROM	derives_from as a shared lifecycle, traceability, validation, or readiness choice.
REFINES	refines as a shared lifecycle, traceability, validation, or readiness choice.
SATISFIES	satisfies as a shared lifecycle, traceability, validation, or readiness choice.
CONSTRAINS	constrains as a shared lifecycle, traceability, validation, or readiness choice.
GENERATED_FROM	generated_from as a shared lifecycle, traceability, validation, or readiness choice.
VALIDATES	validates as a shared lifecycle, traceability, validation, or readiness choice.
MITIGATES	mitigates as a shared lifecycle, traceability, validation, or readiness choice.
CONFLICTS_WITH	conflicts_with as a shared lifecycle, traceability, validation, or readiness choice.
MAPS_TO	maps_to as a shared lifecycle, traceability, validation, or readiness choice.
TRANSFORMS_TO	transforms_to as a shared lifecycle, traceability, validation, or readiness choice.
REALIZES	realizes as a shared lifecycle, traceability, validation, or readiness choice.
IMPLEMENTS	implements as a shared lifecycle, traceability, validation, or readiness choice.
DEPLOYS_TO	deploys_to as a shared lifecycle, traceability, validation, or readiness choice.
OBSERVES	observes as a shared lifecycle, traceability, validation, or readiness choice.
OTHER	other as a shared lifecycle, traceability, validation, or readiness choice.

FindingType

Literal	Practical meaning
MISSING_INFORMATION	missing_information as a shared lifecycle, traceability, validation, or readiness choice.
INCONSISTENCY	inconsistency as a shared lifecycle, traceability, validation, or readiness choice.
BLOCKING_RISK	blocking_risk as a shared lifecycle, traceability, validation, or readiness choice.
BLOCKING_HOTSPOT	blocking_hotspot as a shared lifecycle, traceability, validation, or readiness choice.
VALIDATION_WARNING	validation_warning as a shared lifecycle, traceability, validation, or readiness choice.
VALIDATION_ERROR	validation_error as a shared lifecycle, traceability, validation, or readiness choice.
TRANSFORMATION_ASSUMPTION	transformation_assumption as a shared lifecycle, traceability, validation, or readiness choice.
POLICY_VIOLATION	policy_violation as a shared lifecycle, traceability, validation, or readiness choice.
SECURITY_RISK	security_risk as a shared lifecycle, traceability, validation, or readiness choice.
DEPLOYMENT_RISK	deployment_risk as a shared lifecycle, traceability, validation, or readiness choice.
OTHER	other as a shared lifecycle, traceability, validation, or readiness choice.

StructuredFormat

Literal	Practical meaning
TEXT	text as a shared lifecycle, traceability, validation, or readiness choice.
JSON	json as a shared lifecycle, traceability, validation, or readiness choice.
YAML	yaml as a shared lifecycle, traceability, validation, or readiness choice.
TOML	toml as a shared lifecycle, traceability, validation, or readiness choice.
XML	xml as a shared lifecycle, traceability, validation, or readiness choice.
MARKDOWN	markdown as a shared lifecycle, traceability, validation, or readiness choice.
ASL_JSON	asl_json as a shared lifecycle, traceability, validation, or readiness choice.
IAM_POLICY_JSON	iam_policy_json as a shared lifecycle, traceability, validation, or readiness choice.
CLOUDFORMATION_INTRINSIC	cloudformation_intrinsic as a shared lifecycle, traceability, validation, or readiness choice.
OTHER	other as a shared lifecycle, traceability, validation, or readiness choice.

ExpressionLanguage

Literal	Practical meaning
NATURAL_LANGUAGE	natural_language as a shared lifecycle, traceability, validation, or readiness choice.
OCL	ocl as a shared lifecycle, traceability, validation, or readiness choice.
FEEL	feel as a shared lifecycle, traceability, validation, or readiness choice.
JSONPATH	jsonpath as a shared lifecycle, traceability, validation, or readiness choice.
JSONATA	jsonata as a shared lifecycle, traceability, validation, or readiness choice.
JAVASCRIPT	javascript as a shared lifecycle, traceability, validation, or readiness choice.
TYPESCRIPT	typescript as a shared lifecycle, traceability, validation, or readiness choice.
PYTHON	python as a shared lifecycle, traceability, validation, or readiness choice.
SQL	sql as a shared lifecycle, traceability, validation, or readiness choice.
REGEX	regex as a shared lifecycle, traceability, validation, or readiness choice.
OTHER	other as a shared lifecycle, traceability, validation, or readiness choice.

ExpressionPhase

Literal	Practical meaning
DESIGN_TIME	design_time as a shared lifecycle, traceability, validation, or readiness choice.
VALIDATION_TIME	validation_time as a shared lifecycle, traceability, validation, or readiness choice.
RUNTIME	runtime as a shared lifecycle, traceability, validation, or readiness choice.
GENERATION_TIME	generation_time as a shared lifecycle, traceability, validation, or readiness choice.

Marker interfaces

Marker interfaces do not declare attributes. They identify capabilities used by the metamodel and transformations, such as deployability, invocation, routing, policy targeting, or configuration.

DeployableElement, InvocationSource, InvocationTarget, FunctionTarget, WorkflowTarget, SubscriptionTarget, RoutingTarget, FlowEndpoint, ProtectedResource, PolicyTarget, DataAccessTarget, ExternalCallTarget, EnvironmentTarget, CredentialRequirementLike, RouteEndpoint, EventCarrier, and ConfigurableElement.

KeyValue

Represents key value in the SHARED vocabulary and provides the primary place to record this modeling concern.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
key	String [1]	The lookup key in a small named-value pair, such as a configuration name or tag key. Its meaning comes from the owning collection, so it should be unique where that collection treats pairs as a map. 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.
value	String [1]	The value associated with the key. It keeps a small extensible piece of metadata together without creating a new metaclass for every optional annotation/configuration detail. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/cfn.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/iam.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: READY.

Relationships

This class declares no direct relationships.

Annotation

Represents annotation in the SHARED vocabulary. It specializes KeyValue with the details needed for this modeling concern.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
source	String [1]	The namespace or tool that owns the annotation, such as generator or review. It prevents similarly named annotations from different concerns being mistaken for one another. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/cfn.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/contracts.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Annotation Source.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
owner → ModelElement	reference, [1]	References the model element element(s) used as owner by this annotation; the target may be shared elsewhere in the model.

ModelElement

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

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
id	String [1]; identifier	The stable EMF identity of the element. References and trace links use it to find the same model object across saves and transformations; changing it can break provenance and incremental synchronization. Semantic validation: ModelElementIdIsPresentAndUnique (model element id is present and unique) in mde/validation/shared/kernel-constraints.evl the value must be present and non-blank. ModelElementIdRequired (model element id required) in mde/validation/pim/rules/core.evl the value must be present and non-blank. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/contracts.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/naming.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: order-123.
name	String [1]	The model-facing name used to identify the element in diagrams, diagnostics, trace reports, and generated explanations. It is not necessarily an AWS physical name, which is why provider-specific resources have separate naming fields. Semantic validation: ModelElementIdRequired (model element id required) in mde/validation/pim/rules/core.evl the feature participates in a semantic validation condition. PortableNameRecommended (portable name recommended) in mde/validation/pim/rules/core.evl the value must be present and non-blank. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/contracts.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/naming.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: ModelElementExample.
summary	String [1]	A compact statement of the element's meaning, intended for lists, palettes, search results, and readiness reports where the full description would be too much detail. Semantic validation: ModelElementHasExplanation (model element has explanation) in mde/validation/cim/rules/core-kernel-trace.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/contracts.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Model Element Summary.
description	String [1]	The fuller human explanation of what the element means in the domain or architecture. It preserves intent that cannot be recovered from a class name or a set of references and is therefore part of reviewable model content. Semantic validation: ModelElementHasExplanation (model element has explanation) in mde/validation/cim/rules/core-kernel-trace.evl the value must be present and non-blank. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/contracts.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/templates/cicd/github-actions-deploy-dev.egl.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Processes confirmed orders for the owning capability..
documentation	String [1]	Long-lived guidance attached to the element, such as assumptions, examples, operating notes, or usage instructions. It lets the model carry the explanation needed by a future modeller instead of relying on external meeting memory. Semantic validation: ModelElementHasExplanation (model element has explanation) in mde/validation/cim/rules/core-kernel-trace.evl the value must be present and non-blank. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/contracts.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/templates/docs/readme.egl.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Model Element Documentation.
modelTags	String [*]	A set of searchable classification labels, for example pii, critical, or legacy-integration, that supports navigation and governance without changing the element's formal type or behavior.	A collection of values. Example: [Model Element Model Tags, Model Element Model Tags-2].
externalId	String [1]	The identifier of the corresponding backlog item, workshop record, source-system object, or imported artifact. It anchors model traceability to an external authority without replacing the EMF id. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/naming.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: order-123.
lifecycleStatus	LifecycleStatus [1]	The governance state of the element, from draft/incomplete through approved and transformation/deployment readiness to deprecated or blocked. Readiness EVL uses this lifecycle vocabulary to separate modelling progress from business semantics.	Exactly one of: DRAFT, INCOMPLETE, REVIEW_REQUIRED, APPROVED, TRANSFORMATION_READY, DEPLOYMENT_READY, PRODUCTION_READY, BLOCKED, DEPRECATED. Example: DRAFT.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
annotations → Annotation	containment, [*]	Contains the annotation element(s) that make up this model element; the contained objects belong to this model element.
incomingTraces → TraceLink	reference, [*]	References the trace link element(s) used as incoming traces by this model element; the target may be shared elsewhere in the model.
outgoingTraces → TraceLink	reference, [*]	References the trace link element(s) used as outgoing traces by this model element; the target may be shared elsewhere in the model.

NamedModelElement

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

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
displayName	String [1]	The readable label shown to people when the technical name is unsuitable for presentation. It supports human review and generated documentation without changing the stable identity used by transformations. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/cfn.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/naming.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: NamedModelElementExample.

Relationships

This class declares no direct relationships.

TraceableElement

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

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
sourceReference	String [1]	The concise human reference to the source requirement, story, workshop decision, or upstream model element from which this element was understood. It gives reviewers a navigable origin without requiring them to inspect the full trace graph. Semantic validation: GeneratedElementShouldBeTraceable (generated element should be traceable) in mde/validation/pim/rules/core.evl the value must be present and non-blank. TraceableElementHasSourceOrRationale (traceable element has source or rationale) in mde/validation/cim/rules/core-kernel-trace.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: Traceable Element Source Reference.
sourceExcerpt	String [1]	The relevant source wording captured alongside the reference. It protects the model's rationale when the original discussion is difficult to access and helps a reviewer check whether a refinement still matches the source intent. Semantic validation: TraceableElementHasSourceOrRationale (traceable element has source or rationale) in mde/validation/cim/rules/core-kernel-trace.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: Traceable Element Source Excerpt.
sourceQualifiedName	String [1]	The fully qualified name of the source element, used when a short label is ambiguous across packages or DSML levels. Transformation tooling can use it to explain exactly which upstream concept produced the current element. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/naming.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: TraceableElementExample.
sourceUri	String [1]	The URI or repository location of the source artifact. It makes provenance actionable: a modeller can move from a generated PIM/PSM object back to the requirement, source model, or document that justified it. Semantic validation: GeneratedElementShouldBeTraceable (generated element should be traceable) in mde/validation/pim/rules/core.evl the value must be present and non-blank. TraceableElementHasSourceOrRationale (traceable element has source or rationale) in mde/validation/cim/rules/core-kernel-trace.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: https://example.com/orders.
sourceLine	String [1]	The source line or location associated with the origin. It narrows a large artifact to the exact evidence used for the model decision and is particularly useful in generated validation reports.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Traceable Element Source Line.
traceId	String [1]	The identifier used to correlate this element with transformation trace records. It is generated/checked as part of traceability and allows reports to explain how a CIM choice became a PIM concept or AWS resource. Semantic validation: GeneratedElementShouldBeTraceable (generated element should be traceable) in mde/validation/pim/rules/core.evl the value must be present and non-blank. GeneratedElementHasOrigin (generated element has origin) in mde/validation/cim/rules/core-kernel-trace.evl the value must be present and non-blank. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/naming.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/validation.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: order-123.
generatedFrom	String [1]	The upstream model identity from which this element was generated. It is the provenance edge stored directly on the target and is required by validation for generated elements that must remain explainable. Semantic validation: GeneratedElementShouldBeTraceable (generated element should be traceable) in mde/validation/pim/rules/core.evl the value must be present and non-blank. GeneratedElementHasOrigin (generated element has origin) in mde/validation/cim/rules/core-kernel-trace.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: Traceable Element Generated From.
generatedByTransformation	Boolean [1]	Whether the element was materialized by an ETL transformation rather than authored directly. Validation uses the flag to demand origin information, and manual maintenance can then be distinguished from generated content. Semantic validation: GeneratedElementShouldBeTraceable (generated element should be traceable) in mde/validation/pim/rules/core.evl the feature participates in a semantic validation condition. GeneratedElementHasOrigin (generated element has origin) in mde/validation/cim/rules/core-kernel-trace.evl the flag must be enabled for this rule to pass.	Either true or false. Example: false.
rationale	String [1]	The reasoning behind the element or an intentional deviation from an obvious mapping. PIM validation uses rationale for deliberately detached workflow steps and manually maintained elements; it is the place to explain a modelling exception, not to repeat the name. Semantic validation: GeneratedElementShouldBeTraceable (generated element should be traceable) in mde/validation/pim/rules/core.evl the feature participates in a semantic validation condition. RationaleRecommendedForManuallyMaintainedElements (rationale recommended for manually maintained elements) in mde/validation/pim/rules/core.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/validation.eol.	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..
reviewStatus	String [1]	The human review state of the element, such as pending review, accepted, or needing clarification. It keeps review progress distinct from lifecycle/deployment status.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: ACTIVE.
reviewNotes	String [1]	Open reviewer questions, decisions, or follow-up instructions attached to this exact element. Keeping them here prevents unresolved review context from disappearing when a model is transformed. Semantic validation: RationaleRecommendedForManuallyMaintainedElements (rationale recommended for manually maintained elements) in mde/validation/pim/rules/core.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: Traceable Element Review Notes.
manuallyMaintained	Boolean [1]	Whether generated content is intentionally edited or owned by a modeller. The flag tells validation and future synchronization that regeneration may overwrite a human decision, so rationale and review are needed. Semantic validation: RationaleRecommendedForManuallyMaintainedElements (rationale recommended for manually maintained elements) in mde/validation/pim/rules/core.evl the feature participates in a semantic validation condition.	Either true or false. Example: false.

Relationships

This class declares no direct relationships.

SemanticRelationship

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

Declared attributes

TraceModel records the exact source/target revisions and transformation provenance for a trace baseline. These fields make cross-level change impact and release evidence inspectable rather than dependent on filenames or informal notes.

Attribute	Type and multiplicity	Meaning
sourceModelId, sourceRevision	String [0..1]	Identity and revision of the source model used for the trace run.
targetModelId, targetRevision	String [0..1]	Identity and revision of the refined/generated target model.
transformationId, transformationVersion	String [0..1]	Transformation profile and version used to produce the trace.
generatedAt	Date [0..1]	Timestamp of the transformation or trace generation run.
generatedBy	String [0..1]	Tool, process run, or actor that generated the trace baseline.

Relationships

This class declares no direct relationships.

Multiplicity

Represents multiplicity in the SHARED vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
lowerBound	Integer [1]	The minimum number of values allowed by the multiplicity contract. It expresses structural cardinality, such as required versus optional, rather than a business quantity and is used when the combined Ecore model is validated or inspected.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
upperBound	Integer [1]	The maximum number of values allowed when the collection is bounded. It prevents a model from accepting more related values than the abstract syntax permits.	A numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
unbounded	Boolean [1]	Whether the collection has no finite upper limit. It makes an unbounded relationship explicit instead of overloading a sentinel number and is read together with upperBound.	Either true or false. Example: false.
ordered	Boolean [1]	Whether collection position has meaning. An ordered collection preserves sequence for model consumers; an unordered one should not be used to smuggle workflow precedence into containment order.	Either true or false. Example: false.
unique	Boolean [1]; default true	Whether duplicate values are forbidden in the collection. The default true protects references and attributes from silently carrying the same value twice when uniqueness is part of the Ecore contract.	Either true or false. Example: true.

Relationships

This class declares no direct relationships.

Cardinality

Represents cardinality in the SHARED vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
lowerBound	Integer [1]	Records the lower bound value for cardinality. 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. 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.
upperBound	Integer [1]	For a cardinality, the model records the upper bound 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 numeric Integer value; use the unit or boundary documented for this attribute. Example: 1.
unbounded	Boolean [1]	For a cardinality, the model records whether unbounded 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.
ordered	Boolean [1]	Records precedence value for ordered for cardinality. It keeps deterministic ordering or precedence 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.	Either true or false. Example: false.
unique	Boolean [1]; default true	Records whether unique applies to cardinality. 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

This class declares no direct relationships.

Expression

Represents expression in the SHARED vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
language	ExpressionLanguage [1]	The language in which body is written, such as FEEL, JSONPath, SQL, or natural language. It is essential to interpretation: the same text can have completely different semantics without this discriminator. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/paths.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/templates/docs/generation-report.egl.	Exactly one of: NATURAL_LANGUAGE, OCL, FEEL, JSONPATH, JSONATA, JAVASCRIPT, TYPESCRIPT, PYTHON, SQL, REGEX, OTHER. Example: NATURAL_LANGUAGE.
body	String [1]	The actual expression text evaluated, validated, or carried into generation. It is separate from language so tooling can preserve the original expression while choosing the correct parser or provider mapping. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/contracts.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/templates/infrastructure/sam-template.egl.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Expression Body.
phase	ExpressionPhase [1]	When the expression is meaningful, design time, validation time, generation time, or runtime. The phase prevents a modeller from assuming that a runtime predicate can be evaluated during transformation or that a design note is executable.	Exactly one of: DESIGN_TIME, VALIDATION_TIME, RUNTIME, GENERATION_TIME. Example: DESIGN_TIME.
sideEffectFree	Boolean [1]	Whether evaluating the expression is expected not to change model or business state. This tells validation and transformation whether it is safe to use the expression for a check, routing decision, or derived value.	Either true or false. Example: false.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
referencedElements → ModelElement	reference, [*]	References the model element element(s) used as referenced elements by this expression; the target may be shared elsewhere in the model.

TraceModel

Represents trace model in the SHARED vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Declared attributes

This abstract relationship class has no declared attributes; it exists to give semantic relationships a common traceable supertype.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
links → TraceLink	containment, [*]	Contains the trace link element(s) that make up this trace model; the contained objects belong to this model element.

TraceLink

Represents trace link in the SHARED vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
transformationRule	String [1]	The ETL rule or named transformation decision that created the trace link. It turns a generic provenance edge into an explainable statement about how the source became the target.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: $.status == 'READY'.
confidenceRationale	String [1]	Why the trace is considered reliable or uncertain. It records the judgement behind confidence rather than pretending every generated correspondence has the same evidential strength.	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..
confidenceScore	Double [1]	A numeric confidence estimate for the correspondence. Reports can use it to distinguish deterministic mappings from heuristic or manually confirmed links.	A numeric Double value; use the unit or boundary documented for this attribute. Example: 1.
sourceElementId	String [1]	The source element identity stored in the trace record. It makes the link resolvable even when the human name changes or several elements share a label. Semantic validation: TraceLinkHasReferenceOrExternalId (trace link has reference or external id) in mde/validation/shared/kernel-constraints.evl the value must be present and non-blank. TraceLinkHasReferenceOrExternalId (trace link has reference or external id) in mde/validation/pim/rules/readiness.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: order-123.
targetElementId	String [1]	The generated/refined element identity at the other end of the trace. Together with sourceElementId it supports incremental synchronization and audit of model-to-model transformation. Semantic validation: TraceLinkHasReferenceOrExternalId (trace link has reference or external id) in mde/validation/shared/kernel-constraints.evl the value must be present and non-blank. TraceLinkHasReferenceOrExternalId (trace link has reference or external id) in mde/validation/pim/rules/readiness.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: order-123.
linkType	TraceLinkType [1]	The meaning of the correspondence, derives, refines, satisfies, constrains, maps to, and so on. Consumers need this distinction to tell a requirement satisfaction from a simple transformation origin.	Exactly one of: DERIVES_FROM, REFINES, SATISFIES, CONSTRAINS, GENERATED_FROM, VALIDATES, MITIGATES, CONFLICTS_WITH, MAPS_TO, TRANSFORMS_TO, REALIZES, IMPLEMENTS, DEPLOYS_TO, OBSERVES, OTHER. Example: DERIVES_FROM.
confidence	TraceConfidence [1]	The controlled confidence category for the trace, from low or manual through verified. It gives human review and readiness tooling a compact decision about whether the correspondence can be trusted.	Exactly one of: LOW, MEDIUM, HIGH, VERIFIED, MANUAL. Example: LOW.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
traceModel → TraceModel	reference, [1]	References the trace model element(s) used as trace model by this trace link; the target may be shared elsewhere in the model.
source → ModelElement	reference, [?]	References the model element element(s) used as source by this trace link; the target may be shared elsewhere in the model.
target → ModelElement	reference, [?]	References the model element element(s) used as target by this trace link; the target may be shared elsewhere in the model.

TransformationAssumption

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

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
assumptionStatement	String [1]	The unresolved interpretation or choice made while moving between DSML levels. It prevents the ETL from hiding uncertainty and gives the model owner a concrete statement to accept, reject, or refine.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: ACTIVE.
validationApproach	String [1]	How the assumption will be checked, for example by stakeholder confirmation, source-system evidence, prototype, or a formal validation rule. It turns an uncertainty into an actionable work item.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Transformation Assumption Validation Approach.
accepted	Boolean [1]	Whether the responsible modeller has consciously accepted the assumption for the current increment. It is not a claim that the assumption is universally true; it is a governance decision about allowing refinement to proceed.	Either true or false. Example: false.
acceptedBy	String [1]	The person, team, or authority that accepted the assumption. It supplies accountability when a transformation choice later proves wrong.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Transformation Assumption Accepted By.
acceptedOn	Date [1]	The date on which the assumption was accepted. It lets reviewers judge whether the decision predates a requirement or architectural change and needs revalidation.	A Date value. Example: 2026-01-15.

Relationships

This class declares no direct relationships.

StructuredDocument

Represents structured document in the SHARED vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
format	StructuredFormat [1]	The serialization format of content, such as JSON, ASL JSON, IAM policy JSON, or CloudFormation intrinsic syntax. Generation and validation use it to choose the right parser/serializer and to avoid treating provider documents as ordinary text. Transformation role: ETL rule Schema2StructuredDocument in mde/transformations/pim-to-awspsm/contracts-external-policy.etl assigns or materializes this feature while refining StructuredDocument. ETL rule EventType2StructuredDocument in mde/transformations/pim-to-awspsm/contracts-external-policy.etl assigns or materializes this feature while refining StructuredDocument. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/contracts.eol. The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/paths.eol.	Exactly one of: TEXT, JSON, YAML, TOML, XML, MARKDOWN, ASL_JSON, IAM_POLICY_JSON, CLOUDFORMATION_INTRINSIC, OTHER. Example: TEXT.
content	String [1]	The document body retained in the model when the typed metamodel does not represent every detail. It is the exact structured payload that generation can emit or validation can inspect; it should not be used to duplicate a value already represented by typed attributes. Transformation role: ETL rule Schema2StructuredDocument in mde/transformations/pim-to-awspsm/contracts-external-policy.etl assigns or materializes this feature while refining StructuredDocument. ETL rule EventType2StructuredDocument in mde/transformations/pim-to-awspsm/contracts-external-policy.etl assigns or materializes this feature while refining StructuredDocument. 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/contracts.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Structured Document Content.
externalUri	String [1]	The external location of the structured document when its body is maintained outside the model. It makes the source artifact explicit so generators and reviewers do not guess which file is authoritative. Transformation role: ETL rule Schema2StructuredDocument in mde/transformations/pim-to-awspsm/contracts-external-policy.etl assigns or materializes this feature while refining StructuredDocument.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: https://example.com/orders.

Relationships

This class declares no direct relationships.

ProductionReadinessAssessment

Represents production readiness assessment in the SHARED vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
assessedAt	Date [1]	When readiness was evaluated. This timestamps a decision that can become stale as requirements, transformations, or infrastructure change. Semantic validation: ReadinessAssessmentHasAssessor (readiness assessment has assessor) in mde/validation/cim/rules/governance-readiness.evl the value must be present and non-blank.	A Date value. Example: 2026-01-15.
assessedBy	String [1]	The person or role accountable for the readiness judgement. EVL requires an assessor so a production-ready flag is not an anonymous assertion. Semantic validation: ReadinessAssessmentHasAssessor (readiness assessment has assessor) in mde/validation/cim/rules/governance-readiness.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: Production Readiness Assessment Assessed By.
gateId	String [0..1]	The lifecycle or release gate for which this assessment was recorded.	A gate identifier, for example pim-to-psm.
assessedRevision	String [0..1]	The exact model or artifact revision assessed.	A revision identifier, for example pim-42.
evidenceUri	String [0..1]	Location of the report, checklist, test result, or decision evidence supporting this assessment.	A repository, tracker, or evidence URI.
openBlockingCount	Integer [0..1]	Snapshot count of open blocking findings when the assessment was recorded.	A non-negative integer.
transformationReady	Boolean [1]	Whether the current model has passed the checks needed to move from intent to the next DSML level. It is distinct from deployment readiness because a model can be internally coherent while still lacking an implementation mapping. Semantic validation: ProductionReadyRequiresPassedChecksAndNoBlockingFindings (production ready requires passed checks and no blocking findings) in mde/validation/pim/rules/readiness.evl the feature participates in a semantic validation condition.	Either true or false. Example: false.
deploymentReady	Boolean [1]	Whether the generated/provider-specific design is sufficiently complete and validated for deployment preparation. It should not be set merely because transformation succeeded. Semantic validation: ProductionReadyRequiresPassedChecksAndNoBlockingFindings (production ready requires passed checks and no blocking findings) in mde/validation/pim/rules/readiness.evl the feature participates in a semantic validation condition.	Either true or false. Example: false.
productionReady	Boolean [1]	The explicit release decision that the model and its artifacts are acceptable for production use. EVL cross-checks it against passed checks and blocking findings so it cannot become an unsubstantiated convenience flag. Semantic validation: ProductionReadyRequiresPassedChecksAndNoBlockingFindings (production ready requires passed checks and no blocking findings) in mde/validation/pim/rules/readiness.evl the feature participates in a semantic validation condition. ProductionReadyAssessmentIsConsistent (production ready assessment is consistent) in mde/validation/cim/rules/governance-readiness.evl the flag must be enabled for this rule to pass.	Either true or false. Example: true.
readinessStatus	LifecycleStatus [1]	The controlled summary of readiness progress. It gives reports a single lifecycle value while the contained findings, checks, and manual decisions preserve the evidence behind it. Semantic validation: ProductionReadyAssessmentIsConsistent (production ready assessment is consistent) in mde/validation/cim/rules/governance-readiness.evl the feature participates in a semantic validation condition.	Exactly one of: DRAFT, INCOMPLETE, REVIEW_REQUIRED, APPROVED, TRANSFORMATION_READY, DEPLOYMENT_READY, PRODUCTION_READY, BLOCKED, DEPRECATED. Example: DRAFT.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
findings → ReadinessFinding	containment, [*]	Contains the readiness finding element(s) that make up this production readiness assessment; the contained objects belong to this model element.
checks → ReadinessCheck	containment, [*]	Contains the readiness check element(s) that make up this production readiness assessment; the contained objects belong to this model element.
manualDecisions → ManualDecision	containment, [*]	Contains the manual decision element(s) that make up this production readiness assessment; the contained objects belong to this model element.

ReadinessFinding

Represents readiness finding in the SHARED vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
ruleId	String [1]	The stable identifier of the validation or transformation finding that raised the issue. It lets reports, suppressions, and remediation guidance refer to the same kind of problem across model runs. Transformation role: ETL rule Risk2ReadinessFinding in mde/transformations/cim-to-pim/integration-deployment.etl assigns or materializes this feature while refining ReadinessFinding. ETL rule Assumption2ReadinessFinding in mde/transformations/cim-to-pim/integration-deployment.etl assigns or materializes this feature while refining ReadinessFinding. 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: order-123.
message	String [1]	The concrete problem statement shown to the modeller or release reviewer. It should describe the violated expectation in model terms, not merely repeat an implementation exception. Semantic validation: FindingShouldRecommendRemediation (finding should recommend remediation) in mde/validation/pim/rules/readiness.evl the value must be present and non-blank. BlockingFindingHasRecommendation (blocking finding has recommendation) in mde/validation/cim/rules/governance-readiness.evl the value must be present and non-blank. Transformation role: ETL rule Risk2ReadinessFinding in mde/transformations/cim-to-pim/integration-deployment.etl assigns or materializes this feature while refining ReadinessFinding. ETL rule Assumption2ReadinessFinding in mde/transformations/cim-to-pim/integration-deployment.etl assigns or materializes this feature while refining ReadinessFinding.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Order could not be completed..
recommendation	String [1]	The suggested next action for resolving the finding. It turns validation output into usable workflow guidance rather than leaving the modeller to reverse-engineer the fix. Semantic validation: FindingShouldRecommendRemediation (finding should recommend remediation) in mde/validation/pim/rules/readiness.evl the value must be present and non-blank. BlockingFindingHasRecommendation (blocking finding has recommendation) in mde/validation/cim/rules/governance-readiness.evl the value must be present and non-blank. Transformation role: ETL rule Risk2ReadinessFinding in mde/transformations/cim-to-pim/integration-deployment.etl assigns or materializes this feature while refining ReadinessFinding. ETL rule Assumption2ReadinessFinding in mde/transformations/cim-to-pim/integration-deployment.etl assigns or materializes this feature while refining ReadinessFinding.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Readiness Finding Recommendation.
blocking	Boolean [1]	Whether this finding prevents the relevant transformation, deployment, or production decision. Readiness EVL uses it to ensure a blocking item cannot be silently treated as informational. Semantic validation: BlockingFindingHasRecommendation (blocking finding has recommendation) in mde/validation/cim/rules/governance-readiness.evl the flag must be enabled for this rule to pass. Transformation role: ETL rule Risk2ReadinessFinding in mde/transformations/cim-to-pim/integration-deployment.etl assigns or materializes this feature while refining ReadinessFinding. ETL rule Assumption2ReadinessFinding in mde/transformations/cim-to-pim/integration-deployment.etl assigns or materializes this feature while refining ReadinessFinding.	Either true or false. Example: false.
severity	Severity [1]	The impact level of the finding, from informational to blocker. It helps prioritize remediation and controls how strongly a pipeline should react. Transformation role: ETL rule Risk2ReadinessFinding in mde/transformations/cim-to-pim/integration-deployment.etl assigns or materializes this feature while refining ReadinessFinding. ETL rule Assumption2ReadinessFinding in mde/transformations/cim-to-pim/integration-deployment.etl assigns or materializes this feature while refining ReadinessFinding.	Exactly one of: INFO, WARNING, ERROR, CRITICAL, BLOCKER. Example: INFO.
findingType	FindingType [1]	The reason category, missing information, inconsistency, security risk, deployment risk, transformation assumption, and so on. It helps teams route remediation to the right kind of work. Transformation role: ETL rule Risk2ReadinessFinding in mde/transformations/cim-to-pim/integration-deployment.etl assigns or materializes this feature while refining ReadinessFinding. ETL rule Assumption2ReadinessFinding in mde/transformations/cim-to-pim/integration-deployment.etl assigns or materializes this feature while refining ReadinessFinding.	Exactly one of: MISSING_INFORMATION, INCONSISTENCY, BLOCKING_RISK, BLOCKING_HOTSPOT, VALIDATION_WARNING, VALIDATION_ERROR, TRANSFORMATION_ASSUMPTION, POLICY_VIOLATION, SECURITY_RISK, DEPLOYMENT_RISK, OTHER. Example: MISSING_INFORMATION.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
assessment → ProductionReadinessAssessment	reference, [1]	References the production readiness assessment element(s) used as assessment by this readiness finding; the target may be shared elsewhere in the model.
affectedElements → ModelElement	reference, [*]	References the model element element(s) used as affected elements by this readiness finding; the target may be shared elsewhere in the model.

ReadinessCheck

Represents readiness check in the SHARED vocabulary. It specializes TraceableElement with the details needed for this modeling concern.

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
checkId	String [1]	The stable identifier of a pass/fail readiness check. It gives automated reports a durable key even when the human message changes. Transformation role: ETL rule KPI2ReadinessCheck in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining ReadinessCheck.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: order-123.
passed	Boolean [1]	Whether the check's condition was satisfied at assessment time. A passed check is evidence for readiness, not a replacement for the overall production decision. Semantic validation: FailedCheckShouldHaveRemediation (failed check should have remediation) in mde/validation/pim/rules/readiness.evl the related value or object must be explicitly provided. FailedReadinessCheckHasRemediation (failed readiness check has remediation) in mde/validation/cim/rules/governance-readiness.evl the flag must be enabled for this rule to pass. Transformation role: ETL rule KPI2ReadinessCheck in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining ReadinessCheck.	Either true or false. Example: false.
message	String [1]	The result explanation presented with the check. It tells a reviewer what was evaluated and why the result matters. Semantic validation: FailedCheckShouldHaveRemediation (failed check should have remediation) in mde/validation/pim/rules/readiness.evl the value must be present and non-blank. FailedReadinessCheckHasRemediation (failed readiness check has remediation) in mde/validation/cim/rules/governance-readiness.evl the value must be present and non-blank. Transformation role: ETL rule KPI2ReadinessCheck in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining ReadinessCheck.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Order could not be completed..
remediation	String [1]	The action needed when the check fails. It makes the readiness record operationally useful instead of a bare boolean list. Semantic validation: FailedCheckShouldHaveRemediation (failed check should have remediation) in mde/validation/pim/rules/readiness.evl the value must be present and non-blank. FailedReadinessCheckHasRemediation (failed readiness check has remediation) in mde/validation/cim/rules/governance-readiness.evl the value must be present and non-blank. Transformation role: ETL rule KPI2ReadinessCheck in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining ReadinessCheck.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Readiness Check Remediation.
severity	Severity [1]	The consequence of a failed check. It allows the same assessment to contain advisory checks and release-blocking checks without conflating them. Transformation role: ETL rule KPI2ReadinessCheck in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining ReadinessCheck.	Exactly one of: INFO, WARNING, ERROR, CRITICAL, BLOCKER. Example: INFO.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
assessment → ProductionReadinessAssessment	reference, [1]	References the production readiness assessment element(s) used as assessment by this readiness check; the target may be shared elsewhere in the model.
affectedElements → ModelElement	reference, [*]	References the model element element(s) used as affected elements by this readiness check; the target may be shared elsewhere in the model.

ManualDecision

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

Declared attributes

Attribute	Type and multiplicity	What it captures and why it exists	Accepted values and example
question	String [1]	The unresolved question that requires a human answer before a transformation or release can proceed. A precise question is what makes a manual gate actionable. Semantic validation: BlockingManualDecisionHasOwner (blocking manual decision has owner) in mde/validation/cim/rules/governance-readiness.evl the value must be present and non-blank. Transformation role: ETL rule Stakeholder2ManualDecision in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining ManualDecision. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/validation.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Manual Decision Question.
decision	String [1]	The human answer to the question, captured in the assessment rather than left in chat, email, or a meeting. It closes the governance loop for decisions that cannot be derived automatically. Semantic validation: BlockingManualDecisionMustBeAnswered (blocking manual decision must be answered) in mde/validation/pim/rules/readiness.evl the value must be present and non-blank. BlockingManualDecisionHasOwner (blocking manual decision has owner) in mde/validation/cim/rules/governance-readiness.evl the feature participates in a semantic validation condition. Generation role: The artifact generator references this feature in mde/generation/awspsm-to-artifacts/lib/validation.eol.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: Manual Decision Decision.
state	ManualDecisionState [0..1]	Lifecycle state of the decision: open, accepted, rejected, waived, or deferred. It prevents an answered question from being mistaken for an accepted decision.	One of OPEN, ACCEPTED, REJECTED, WAIVED, DEFERRED.
decisionOwner	String [1]	The person or role expected to answer the decision. Readiness validation uses ownership to keep blocking questions from becoming abandoned model metadata. Semantic validation: BlockingManualDecisionMustBeAnswered (blocking manual decision must be answered) in mde/validation/pim/rules/readiness.evl the value must be present and non-blank. GeneratedBlockingManualDecisionShouldHaveOwner (generated blocking manual decision should have owner) in mde/validation/pim/rules/readiness.evl the value must be present and non-blank. Transformation role: ETL rule Stakeholder2ManualDecision in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining ManualDecision.	A free-form String, subject to this class's semantic meaning and any EVL constraints. Example: orders-team.
decisionRecordedAt	Date [0..1]	When the current decision state was recorded.	A Date value.
expiryDate	Date [0..1]	Optional expiry for a waiver or deferred decision.	A Date value.
dueDate	Date [1]	The date by which the decision is expected. It gives unresolved transformation assumptions and release gates a visible follow-up point. Semantic validation: ManualDecisionHasDueDate (manual decision has due date) in mde/validation/cim/rules/governance-readiness.evl the related value or object must be explicitly provided.	A Date value. Example: 2026-01-15.
blocking	Boolean [1]	Whether the unanswered decision must stop progress. It distinguishes a useful clarification from a gate that makes the generated design unsafe to accept. Semantic validation: BlockingManualDecisionMustBeAnswered (blocking manual decision must be answered) in mde/validation/pim/rules/readiness.evl the feature participates in a semantic validation condition. GeneratedBlockingManualDecisionShouldHaveOwner (generated blocking manual decision should have owner) in mde/validation/pim/rules/readiness.evl the feature participates in a semantic validation condition. Transformation role: ETL rule Stakeholder2ManualDecision in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining ManualDecision.	Either true or false. Example: false.
severity	Severity [1]	The impact of leaving the decision unresolved. It helps reviewers prioritize decisions even when several are open. Transformation role: ETL rule Stakeholder2ManualDecision in mde/transformations/cim-to-pim/root-scaffolding.etl assigns or materializes this feature while refining ManualDecision.	Exactly one of: INFO, WARNING, ERROR, CRITICAL, BLOCKER. Example: INFO.

Relationships

Relationship	Kind and multiplicity	Meaning in the model
assessment → ProductionReadinessAssessment	reference, [?]	References the production readiness assessment element(s) used as assessment by this manual decision; the target may be shared elsewhere in the model.
affectedElements → ModelElement	reference, [*]	References the model element element(s) used as affected elements by this manual decision; the target may be shared elsewhere in the model.