====== P2-REQ-16-10-005 ======

[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]

===== Statement =====

A Domain Logical Profile SHALL NOT introduce implementation technologies, deployment artifacts, runtime scripts, product choices, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]-capture procedures.

===== Source =====

Part 2, Section 16.10: Profile and Implementation Boundary Requirements.

===== Rationale =====

Domain Logical Profiles remain platform-independent logical models. Introducing implementation technologies or deployment concerns would violate the separation between logical architecture and later implementation, deployment, and evidence planning.

===== Applies To =====

This requirement applies to Domain Logical Profiles.

It applies specifically to:

  * Domain Logical Profiles;
  * Implementation technologies;
  * Deployment artifacts; and
  * Evidence procedures.

===== Verification =====

Verification SHALL confirm that Domain Logical Profiles remain independent of implementation and deployment concerns.

Verification activities should include review checks confirming that:

  * implementation technologies are absent;
  * deployment artifacts are not introduced;
  * runtime scripts are excluded; and
  * Evidence-capture procedures remain outside the Logical Architecture.

===== Traceability =====

This requirement supports traceability between Domain Logical Profiles and the platform-independent Logical Architecture.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-001]]
  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-10-006]]

Related source section:

  * [[fxdemo:02-part:16-logical-requirements:16-10-profile-and-implementation-boundary-requirements:start]]

===== Status =====

Draft

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>