Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
fxdemo:02-part:10-logical-interaction-patterns:10-3-report-node-status:start [2026/07/03 12:48] – created owenfxdemo:02-part:10-logical-interaction-patterns:10-3-report-node-status:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
Line 2: Line 2:
 [[fxdemo:02-part:start | Go To Top ]] [[fxdemo:02-part:start | Go To Top ]]
  
-The Report Node Status pattern allows a [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] to report its operational condition.+The Report Node Status pattern allows a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] to report its operational condition.
  
-A reporting [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] provides status information such as [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]], lifecycle state, health condition, timestamp, status reason, warning or failure condition, recovery state, and provenance reference.+A reporting [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] provides status information such as [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]], lifecycle state, health condition, timestamp, status reason, warning or failure condition, recovery state, and provenance reference.
  
-The interaction belongs primarily to the [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]]. It also supports the [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Logical Control Plane]] when a status report triggers a command, and it supports the [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]] when the architecture records status history for review, reconstruction, or [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].+The interaction belongs primarily to the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]]. It also supports the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_control_plane|Logical Control Plane]] when a status report triggers a command, and it supports the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_audit_and_provenance_plane|Logical Audit and Provenance Plane]] when the architecture records status history for review, reconstruction, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].
  
 Table 10-2: Report Node Status logical interaction pattern Table 10-2: Report Node Status logical interaction pattern
 ^ Element ^ Logical treatment ^ ^ Element ^ Logical treatment ^
-| Primary Runtime Plane | [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]] |+| Primary Runtime Plane | [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_health_and_observability_plane|Logical Health and Observability Plane]] |
 | Producing Logical Node Role | Status Reporting Node | | Producing Logical Node Role | Status Reporting Node |
 | Consuming Logical Node Role | Health Monitoring, Control, Oversight, or Audit Node | | Consuming Logical Node Role | Health Monitoring, Control, Oversight, or Audit Node |
 | Primary information | Node status report | | Primary information | Node status report |
-| Supporting information | [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]], lifecycle state, timestamp, status reason, warning or failure condition | +| Supporting information | [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_identity|Logical Node Identity]], lifecycle state, timestamp, status reason, warning or failure condition | 
-| Traceability expectation | Status report traces to the reporting [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] and relevant lifecycle state. | +| Traceability expectation | Status report traces to the reporting [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] and relevant lifecycle state. | 
-| Evidence expectation | Captured status reports support operational review, recovery analysis, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] of [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:n:node|Node]] condition. |+| Evidence expectation | Captured status reports support operational review, recovery analysis, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] of [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] condition. |
  
  
  • fxdemo/02-part/10-logical-interaction-patterns/10-3-report-node-status/start.1783108091.txt.gz
  • Last modified: 2026/07/03 12:48
  • by owen