WTH Yaml uses ‘platform’ in triggers and ‘condition’ in conditions?

When I write in yaml I got used to the fact that i need to start with Platform: in the trigger part but in the condition part I need to start with condition. Couldn’t this be aligned? E.g. Both use platform: state or alternative trigger: state and condition: state.

It’s because conditions can be used in the action section of an automation too.

Thank you for the explanation. This is indeed a good one. Still not sure why the trigger uses platform in stead of trigger but in my head the logic is there now :+1:t2:. Thank you