```xml <result> <column_name>% of largest cluster when first operational</column_name> <family>additive</family> <subtype>intensive_additive</subtype> <confidence>0.82</confidence> <requires_user_confirmation>false</requires_user_confirmation> <sum_meaningful>false</sum_meaningful> <signed>false</signed> <reducers> <primary_reducer>mean</primary_reducer> <valid_reducers>mean, min, max, median, distribution</valid_reducers> <excluded_reducers>sum (summing percentages across entities is meaningless), product (not a ratio change)</excluded_reducers> <average_semantics>arithmetic_mean</average_semantics> </reducers> <inner_outer_measure> <inner_measure_reducer>min</inner_measure_reducer> <outer_measure_reducer>max</outer_measure_reducer> </inner_outer_measure> <multiplicative_partner_derivable>false</multiplicative_partner_derivable> <reasoning> DIMENSION table with no sequence axis makes multiplicative highly implausible (gate prior). The column name contains "%" which could suggest ratio_multiplicative, but the values represent a snapshot LEVEL (percentage of largest cluster at a point in time), not a rate of change. The range [0.01, 1.0] is bounded and represents an intensive property (relative size) that should be averaged, not summed, when aggregating entities. This is a percentage-as-level, not a percentage-as-change, making it intensive_additive despite the "%" token in the name. </reasoning> <table_type_conflict>false</table_type_conflict> </result> ```