"The runtime architecture of a system" crystallizes the notion that temporal relationships matter more than static code structure.

Entities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.

• Runtime architecture matters more than static compile-time structure for systems supporting change.claim0.876
• Runtime architecture must be explicitly represented in code through lifecycle constructs, not just static class relationships.claim0.863
  Assertion that temporal aspects of system behavior are as important as structural aspects and require first-class treatment.
• An explicit focus on runtime architecture leads to a more dynamic and changeable system.claim0.862
  Core design philosophy of the paper.
• These relationships are cognitive architectures regardless of the substrate in which they are implemented.claim0.814
  Asserts that organismic identity is fundamentally a cognitive structure.
• Runtime Architectureconcept0.784
  The dynamic temporal structure of a system as it executes, distinct from static compile-time architecture.
• Studying programming systems requires a paradigm shift from programming languages, where interaction between programmer and system becomes central rather than program code alone.claim0.776
  Core assertion that systems perspective is incommensurable with language perspective; interaction, not code, is what matters in systems analysis.
• A computer program is not defined by its language or hardware but as an abstract causal pattern, a dynamic mathematical structure that influences the physical universe without violating its causal closure.claim0.775
  Paper's ontological characterization of software enabling cyberanimism
• The kind of order that occurs in living structure has a complexity not usually describable by drawings or by architectural images.claim0.767
  Emphasizes the non-pictorial, process-dependent nature of living order.