P2-REQ-16-7-002

The Logical Architecture / PIM SHALL define the following Logical Interaction Patterns:

  • Register Node;
  • Report Node Status;
  • Publish Domain Information;
  • Subscribe to Domain Information;
  • Issue Control Command;
  • Acknowledge Control Command;
  • Request Policy Decision;
  • Record Audit and Provenance; and
  • Replay or Reconstruct Information.

Part 2, Section 16.7: Logical Interaction Requirements.

These Logical Interaction Patterns establish the minimum set of reusable interactions required to support coordination, information exchange, governance, auditability, and operational continuity within the Logical Architecture. They provide a consistent architectural vocabulary that Domain Logical Profiles may specialize while preserving common architectural meaning.

This requirement applies to the Logical Interaction Model.

It applies specifically to:

  • Logical Interaction Patterns;
  • Logical Nodes;
  • Domain Logical Profiles; and
  • Implementation Profiles.

Verification SHALL confirm that each required Logical Interaction Pattern is explicitly defined.

Verification activities should include review checks confirming that:

  • all required Logical Interaction Patterns are present;
  • each pattern has a distinct architectural purpose;
  • the patterns remain platform independent; and
  • Domain Logical Profiles preserve the inherited interaction patterns.

This requirement supports traceability between the Logical Interaction Model and the standard interaction patterns defined by the Logical Architecture.

Related requirement identifiers:

Related source section:

Draft


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

  • dido/99_annexes/annex-d-requirements/part-02/p2-req-16-7-002.txt
  • Last modified: 2026/07/18 12:33
  • by 127.0.0.1