Review Relationship State

Operational capability that exists primarily in the interaction between components rather than inside either component.

Some capabilities belong to a working relationship. They emerge from coordination, shared history, timing, protocols, trust, or fit between components and cannot be found entirely inside either one.

Evaluating components separately can miss the capability or fragility created by their interaction. Changes to either side may alter what the pair can do together.

A dispatcher and technician coordinate efficiently because they share shorthand, expectations, and feedback patterns that are not fully documented in either role.

Relationship state is not merely the status of a personal relationship. Here it names operational capability located in an interaction.

The capability lives between the parts.

* [[system|System]] * [[handoff|Handoff]] * [[actor|Actor]] * [[institutional-memory-cliff|Institutional Memory Cliff]]

* [NIST SP 800-160 Vol. 1 Rev. 1, *Engineering Trustworthy Secure Systems*](https://doi.org/10.6028/NIST.SP.800-160v1r1) — explains that system behavior and properties emerge from parts plus the relationships and interactions among those parts and their environment. This supports the interaction-based mechanism behind the Renaissance Solutions term; NIST does not use the label “Relationship State.”

* Explore with [[system|System]], [[handoff|Handoff]], and [[institutional-memory-cliff|Institutional Memory Cliff]].