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:06-archetype-classification-model:06-2-ecosphere [2026/06/25 14:43] – ↷ Page moved and renamed from fxdemo:01-part:05-2-ecosphere to fxdemo:01-part:06-archetype-classification-model:06-2-ecosphere owen | fxdemo:01-part:06-archetype-classification-model:06-2-ecosphere [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== 5.2 Ecosphere ====== | ====== 5.2 Ecosphere ====== | ||
| - | **Discussion:** | + | [[fxdemo:01-part: |
| - | An Ecosphere identifies | + | See the definition: [[dido: |
| - | For financial systems, the Ecosphere identifies the broad financial area in which an archetype operates. Later ecosystems, domains, logical profiles, implementation profiles, deployment profiles, and evidence plans inherit that high-level scope unless they explicitly define a different classification path. | + | ---- |
| - | **Definition: | + | <WRAP centeralign> |
| - | //broad governed area of activity within an Archetype Classification Model// | + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. |
| - | **Source:** | + | </ |
| - | Adapted from **FX Demo Reference Architecture**, | ||
| - | |||
| - | **Note:** | ||
| - | |||
| - | An Ecosphere is not a runtime identifier, deployment namespace, DDS Domain ID, repository path, or implementation boundary. | ||
| - | |||
| - | **Example: | ||
| - | |||
| - | Structured information-processing archetypes may use Finance, Healthcare, Public Administration, | ||