Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ====== 11.1 Overview ====== [[fxdemo:01-part:start | Go to Top ]] The Conceptual Rules and Constraints define the conceptual boundaries that later parts must preserve when they specialize, realize, deploy, test, or provide [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] for the Financial Systems Archetype. These rules protect the separation between conceptual meaning, logical [[dido:99_annexes:annex-b-terms-and-definitions:s:structure|Structure]], implementation mapping, deployment mechanics, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. They also prevent implementation technologies, runtime identifiers, deployment artifacts, or local profile decisions from redefining the conceptual architecture. Section 13 expresses the formal conceptual requirements. This section explains the conceptual rules and constraints that motivate those requirements. ---- <WRAP centeralign> © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. </WRAP> fxdemo/01-part/11-conceptual-rules-and-constraints/11-1-overview.txt Last modified: 2026/07/18 12:33by 127.0.0.1