Survivorship Rules and OV Calculator

Why can't I change the IndividualEnrolmentStatus nested attribute value back to active from cancel?
Why can't I see nested attributes for address in the UI where SAP is defined as the highest priority in survivorship SRC_SYS definition?
Why do I see multiple attribute values surviving rather than just one value?
Why does the Reltio crosswalk value survives and ignores all other values in one case, but that doesn't happen in another case?
Why is my update attribute value being added using LUD (or Recency) survivorship rather than being overridden?
Why a specific attribute type is getting it's values ignored?
Why do I have two OV attribute values when it should be only one based on the fallback strategery of LUD?
Why am I getting two different values - one OV value for the MDM and one OV value in GBQ or Qubole?
Why is the nested attribute value using singleValueByCrosswalkSources being overridden when the aggregation has been applied?
Why do I see two different values for an attribute for the same source on a crosswalk when I am using LUD survivorship?
How does order of data load affect the OV?