The Logical Interaction Patterns define reusable platform-independent ways for Logical Nodes to cooperate.
Table 10-11: Summary of Logical Interaction Patterns
| Pattern | Primary logical purpose | Primary Runtime Plane |
|---|---|---|
| Register Node | Announce identity, roles, capabilities, endpoints, and compatibility information | Logical Control Plane |
| Report Node Status | Report lifecycle state, health, availability, degradation, failure, or recovery progress | Logical Health and Observability Plane |
| Publish Domain Information | Produce domain, analytical, lifecycle, validation, or derived information | Logical Data Plane |
| Subscribe to Domain Information | Receive domain, analytical, lifecycle, validation, or derived information | Logical Data Plane |
| Issue Control Command | Request or direct operational action | Logical Control Plane |
| Acknowledge Control Command | Report command receipt, acceptance, rejection, completion, failure, or outcome | Logical Control Plane |
| Request Policy Decision | Request governed access, disclosure, safeguarding, release, or handling decision | Logical Policy and Release Plane |
| Record Audit and Provenance | Preserve lineage, accountability, auditability, reconstruction, and review information | Logical Audit and Provenance Plane |
| Replay or Reconstruct Information | Reproduce, republish, or reconstruct selected information from preserved records | Logical Audit and Provenance Plane |
These patterns do not exhaust all possible logical interactions. They define the core interaction vocabulary for this distributed, node-based Logical Architecture / PIM. Domain profiles specialize these patterns for specific financial Domains.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.