P1-REQ-13-10-005

Return to Part 1 Requirements

A later part SHALL NOT use a deployment decision to redefine a conceptual element.

Part 1, Section 13.10: Profile and Layering Requirements.

Deployment decisions belong to operational realisation. They describe where, how, and under which conditions implementation artefacts execute, connect, scale, observe, secure, or recover. Deployment decisions do not define conceptual architecture meaning.

This requirement prevents deployment arrangements from altering conceptual elements inherited from Part 1. It preserves conceptual stability across local development, test, regulated production, sovereign infrastructure, and restricted environments.

This requirement applies to later parts that introduce or use deployment decisions.

It applies specifically to deployment decisions involving:

• Runtime environments
• Container placement
• Orchestration
• Network topology
• Security zones
• Configuration
• Operational dashboards
• Infrastructure profiles

Verification SHALL confirm that later parts do not use deployment decisions to redefine conceptual elements.

Verification activities include review checks confirming that:

• Deployment decisions appear as deployment concerns
• Conceptual elements retain Part 1 definitions
• Deployment artefacts trace to the implementation artefacts they deploy or configure
• Environment-specific arrangements do not replace conceptual definitions

Related source section:

• 13.10 Profile and Layering Requirements

Related requirement identifiers:

• p1-req-13-10-003
• p1-req-13-10-006
• p1-req-13-10-008
• p1-req-13-2-004
• p1-req-13-7-004

Draft