Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| fxdemo:01-part:11-conceptual-rules-and-constraints:11-11-conceptual-constraints-summary [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:11-11-conceptual-constraints-summary to fxdemo:01-part:11-conceptual-rules-and-constraints:11-11-conceptual-constraints-summary owen | fxdemo:01-part:11-conceptual-rules-and-constraints:11-11-conceptual-constraints-summary [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| - Conceptual elements remain distinct from one another. | - Conceptual elements remain distinct from one another. | ||
| - | - Conceptual architecture does not prescribe execution granularity, | + | - Conceptual architecture does not prescribe execution granularity, |
| - | - Classification values identify business and semantic scope, not runtime | + | - [[dido: |
| - | - Runtime Planes classify architectural purpose, not implementation mechanisms. | + | - [[dido: |
| - | - Implementation mappings | + | - Implementation mappings |
| - | - Deployment | + | - Deployment |
| - | - Evidence supports claims; it does not replace claims. | + | - [[dido: |
| - | - Traceability preserves relationships across layers. | + | - [[dido: |
| - Local profiles preserve parent meaning unless they explicitly define a controlled extension. | - Local profiles preserve parent meaning unless they explicitly define a controlled extension. | ||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | |||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | |||
| + | </ | ||
| + | |||