I’ve done something similar as @George_B describes. I have a checkbox and an invisible Required Choice Component right after it. When the person clicks the checkbox, I have all the other elements of the form turn on. I also make the checkbox disappear when it’s checked so that they can’t uncheck the box after filling out the rest of the form. In the place of the checkbox I have a Rich Text component appear that has been styled with CSS to look exactly like the checkbox and its corresponding text but filled in. It’s just for aesthetics. It can’t be unchecked obviously, but gives the effect of a checked box. Once the box has been checked, they can only cancel out the entire form and subsequent submission.
Alternatively, you could just use the Choice Component instead of the checkbox to require agreeing to terms and conditions, since that component can be Required. Just have the Choice Component point to a column with only one row of data: “Yes” or “I Agree”.
But I’m guessing that was just an example and you have another reason for wanting your checkbox’s ‘TRUE’ state required. I would love to see this come to Glide as well. For app flow purposes, Checkboxes are just much smoother than Choice Components when used in this way.