P1-REQ-13-10-005

Return to Part 1 Requirements

Statement

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

Source

Part 1, Section 13.10: Profile and Layering Requirements.

Rationale

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.

Applies To

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

It applies specifically to deployment decisions involving:

Runtime environmentsContainer placementOrchestrationNetwork topologySecurity zonesConfigurationOperational dashboardsInfrastructure profiles

Verification

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 concernsConceptual elements retain Part 1 definitionsDeployment artefacts trace to the implementation artefacts they deploy or configureEnvironment-specific arrangements do not replace conceptual definitions

Traceability

Related source section:

Related requirement identifiers:

Status

Draft

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.