```xml <result> <column_name>cost_usd</column_name> <family>additive</family> <subtype>ordinal_additive</subtype> <confidence>0.85</confidence> <requires_user_confirmation>false</requires_user_confirmation> <sum_meaningful>true</sum_meaningful> <signed>false</signed> <reducers> <primary_reducer>sum</primary_reducer> <valid_reducers>sum, mean, min, max, median, count, distribution</valid_reducers> <excluded_reducers>product (not a ratio), geomean (not a ratio)</excluded_reducers> <average_semantics>arithmetic_mean</average_semantics> </reducers> <inner_outer_measure> <inner_measure_reducer>sum</inner_measure_reducer> <outer_measure_reducer>sum</outer_measure_reducer> </inner_outer_measure> <multiplicative_partner_derivable>true</multiplicative_partner_derivable> <reasoning> Table type is PATH with sequence axis, so ordinal_additive is plausible. Column name "cost_usd" is a strong additive signal (currency unit, cost token). Statistics show strictly non-negative values with 22.7% zeros, mean 0.012, max 1.70 - absolute magnitude centered far from 1.0, consistent with an extensive quantity. The presence of zeros excludes multiplicative. This is a per-step cost on a PATH table: summing across entities at a fixed timestamp is meaningful (total cost at that moment), but along the sequence it represents instantaneous cost levels that should be treated ordinally rather than accumulated via simple sum. Classified as ordinal_additive rather than real_additive because this is a rate/flow measure (cost per time step) on a PATH table, not a cumulative total. </reasoning> <table_type_conflict>false</table_type_conflict> </result> ```