cors check

A casual check-in directed at someone you address as cuz — a term of familiar address used widely in Black American slang and spread through hip-hop culture. Dropping a cuz check is the conversational equivalent of a well-being ping: you are establishing contact, seeing what is good, and affirming the relationship with the address itself. The cuz check can be a text, a DM, or a shoutout — what matters is the warmth baked into the acknowledgment. It signals genuine closeness rather than transactional communication.

A call-out or self-assessment determining whether someone is playing intentionally badly in a game — deliberately dying, feeding kills, or throwing objectives on purpose. Dropping an int check on a teammate is equal parts accusation and interrogation: are you actually this bad or is something deliberate happening here? The check invites either a confession, a defensive explanation, or a meltdown in chat. A staple of competitive gaming communication, it has migrated into everyday discourse to question whether someone's terrible decision-making is wilful or just genuinely catastrophic.

A cooking check is a request for validation or confirmation that someone is genuinely in a state of peak performance — that they're really, actually cooking right now and not just talking about it. Borrowed from the 'check' suffix used in social media to call out or confirm a trait (e.g., 'vibe check'), a cooking check demands proof of the heat. Drop the cooking check when someone claims they're onto something big and you need to see the receipts before you believe it. Can be used earnestly or as light-hearted skepticism.

A sus check is the quick but intentional pause to evaluate whether someone or something is operating in good faith — a vibe audit, a credibility scan, a moment of deliberate skepticism before you proceed. Borrowed from the Among Us-era slang for calling out suspicious behavior, a sus check has broadened into any context where you stop and ask 'wait, does this track?' It's what you do before forwarding information, before trusting a new contact, before accepting an explanation that sounds fine but feels slightly off. The sus check is the instinct to verify before you commit.

The informal act of running a quick sanity test on your vector embeddings to verify they're actually capturing semantic meaning correctly — kind of like a vibe check but for your ML pipeline. An embedding check might involve querying similar words to see if the model clusters them sensibly, or confirming that cosine similarity scores feel right. It's the unglamorous but essential quality-assurance step that ML engineers do before trusting their retrieval or recommendation systems to work properly.