P1-REQ-13-2-004

Return to Part 1 Requirements

The Conceptual Architecture SHALL NOT allow deployment artefacts to redefine conceptual elements.

Part 1, Section 13.2: Conceptual Separation Requirements.

Deployment artefacts describe operational realisation. They identify how selected implementation artefacts run, connect, scale, observe, secure, or recover within an operational environment. They do not define the conceptual meaning of the architecture.

Preventing deployment artefacts from redefining conceptual elements preserves conceptual stability across different deployment environments, including local development, test, regulated production, sovereign infrastructure, and air-gapped or restricted environments.

This requirement applies to all deployment-related references within the Conceptual Architecture.

It applies specifically to artefacts such as:

• Runtime configurations
• Container descriptors
• Orchestration manifests
• Deployment scripts
• Environment-specific settings
• Network topology descriptions
• Operational dashboards
• Infrastructure profiles

Verification SHALL confirm that deployment artefacts do not redefine conceptual elements.

Verification activities include review checks confirming that:

• Deployment artefacts appear only as deployment concerns
• Deployment profiles map to conceptual elements without changing their meaning
• Environment-specific arrangements do not replace conceptual definitions
• Operational examples do not become conceptual requirements

Related source section:

• 13.2 Conceptual Separation Requirements

Related requirement identifiers:

• P1-REQ-13-2-001
• P1-REQ-13-2-002
• P1-REQ-13-2-003
• P1-REQ-13-2-005

Draft