How does Crossplane's model differ from a Terraform pipeline for provisioning cloud infrastructure?

Why this is the answer

Crossplane turns cloud resources into Kubernetes objects that controllers reconcile constantly, so drift is corrected without a run being triggered, whereas Terraform compares configuration with its state file when a plan and apply are executed. Putting a locked state file on Crossplane and in-cluster state on Terraform inverts the two, HCL and YAML are the wrong way round, and Crossplane's whole purpose is provisioning resources beyond Kubernetes.