The compliance badge states the audit window, not a posture
Decided
The trust strip no longer says "SOC 2 Type II aligned". It says "SOC 2 Type II audit underway", and /security publishes the observation window from SOC2_WINDOW_LABEL.
Alternative: keep "aligned", which is a real term of art and does not claim certification.
Why not: the word was defensible in isolation and the site still could not carry it, because the privacy policy stated that Type II "is not represented as achieved anywhere on this site". Both sentences could not be true at once, and a procurement reviewer who notices the pair does not conclude that one of them was carelessly worded. They conclude that the vendor's claims move depending on which page you are on, and every other claim on the site gets re-read in that light.
An audit window is a date range. It is checkable, it is unambiguous, and a buyer can build a procurement timeline on it — which is more useful to them than an adjective. The third trust-strip item was rewritten in the same pass for a related reason: "AWS ca-central-1 tenant isolation" fused two separate controls into one phrase and invited the reader to infer that the region is what isolates tenants. It is not. Row-level security is.
What would make this wrong: the report landing. At that point the badge should state the report and its period, and this decision is superseded rather than reversed.