The Glasswing Checklist
It’s been eight days since Anthropic announced Project Glasswing. Still no confirmed partner list.
At some point a silence this long stops being suspenseful and starts being the actual condition you’re operating inside. Nobody’s going to tap you on the shoulder and tell you whether your company got early access to the most capable AI model that exists right now. You have to go find out yourself, or accept that you might never get a clean answer.
So this issue isn’t more analysis of what Glasswing might mean. It’s the checklist. What to actually go check this week, regardless of whether confirmation ever comes.
Why waiting doesn’t work
Some companies that got Glasswing access will never announce it. There’s no upside in saying so publicly, and real downside in inviting questions about org structure, headcount plans, or what exactly “trusted partner” means for the people doing the work. Silence protects the company more than disclosure would.
Which means the binary you’re looking for, confirmed or not confirmed, might just never resolve. Planning your next six months around an announcement that may not come is planning around nothing.
The information you actually need is closer than a press release. It’s sitting in your own company’s behavior, if you know where to look.
Three things to check this week
Job postings. Pull up your company’s careers page. Search for language that wasn’t there two months ago. “AI-augmented,” “human-in-the-loop oversight,” “working alongside advanced models,” anything that frames the role as a partnership with a capability rather than ownership of a task. Hiring managers write these descriptions based on what’s actually changing day to day, often before anyone in legal or comms has approved saying it publicly. The job posting tells the truth before the announcement does.
Internal tooling. Has something rolled out in the last month that nobody fully explained? A new internal assistant. A new approval workflow that quietly changed how a process works. A “pilot program” that got mentioned once in a Slack channel and then went quiet. Pilots that go quiet are frequently pilots that are working well enough that leadership stopped needing buy-in and started just rolling it out.
Leadership language. The softest signal, but a reliable one. Listen for what’s missing as much as what’s said. If your leadership used to talk about “efficiency” and now talks about “capability” or “positioning” or “future readiness,” that drift toward vagueness usually means something specific is being held back from a name. Vague language at the top is rarely an accident. It’s a placeholder for something not ready to be said plainly yet.
None of these three things confirm Glasswing access specifically. You’re not going to find a smoking gun that says “yes, we have it.” But all three together, especially if they’re new in the last 60 days, are a strong enough signal that something has changed in how your company is thinking about AI capability. Whether that’s Glasswing specifically or just the broader access race around it matters less than the fact that it’s happening at all.
What it means depending on what you find
If you check all three and find nothing, that’s also useful information. It probably means your company is behind the curve on access, which has its own exposure profile, just a different one. The gap between your company and a better-resourced competitor is now the thing to watch, not your own internal signals.
If you find one or two signals, pay attention but don’t panic yet. A single job posting with new language might just be one hiring manager experimenting with phrasing. Internal tooling rollouts happen for plenty of reasons unrelated to frontier model access.
If you find all three at once, especially in the last two months, that’s a different situation. That’s a company actively repositioning around AI capability, whether or not they’ve said so out loud. The honest move at that point isn’t dread. It’s documentation.
There’s a version of this that applies even if you find absolutely nothing. Plenty of companies are genuinely behind on this, not because they’re badly run, but because access races like Glasswing don’t distribute evenly. Smaller companies, companies outside the US, companies without existing enterprise relationships with frontier labs, all of them are realistically watching this from further back. Being behind isn’t a personal failure of your employer. It’s a structural position. But it’s still worth knowing which position you’re in, because the moves that make sense differ depending on where you sit.
If your company is behind, the relevant question isn’t “are we getting Glasswing access.” It’s “how is leadership thinking about closing the gap once general availability arrives, and what’s the timeline they’re imagining.” Some companies will move fast the moment the model goes public. Others will sit on legacy tooling for another year out of inertia. Both are useful things to know about where you work.
The part that doesn’t show up in any checklist
This part is harder to audit than job postings or internal tools. Even companies with zero AI access changes happening internally are still operating in a market where their competitors might have them. That competitive pressure shapes decisions even before any tool gets deployed. A company that suspects a rival has frontier access sometimes makes defensive headcount decisions just to look efficient, completely independent of whether AI actually changed anything internally yet.
This is the part of the story that’s genuinely hard to see from inside a single company, because it’s happening between companies, in board rooms and investor conversations you’re not in. You can’t audit your way to visibility on this one. You can only stay aware that it’s a factor, and treat any sudden “efficiency” language from leadership as potentially about competitive anxiety rather than actual internal AI deployment.
The move that doesn’t depend on any of this being confirmed
Whatever you find, or don’t find, the actual move is the same. Write down what you specifically own that would be hard to replicate if you disappeared for three months. Not your task list. The judgment calls that live in your head because of context nobody else has. The relationships that exist because of years, not job titles. The thing that breaks quietly if you’re not there, even if nobody notices immediately.
This isn’t busywork. It’s the difference between knowing where you actually stand and finding out the hard way, later, from someone else’s decision.
One more thing worth saying plainly
None of this is about becoming paranoid at work. Checking your company’s job postings once and noting a phrase shift isn’t a reason to spend the next month in a state of low-grade dread. The point of a checklist is to run it, get an honest read, and then go back to doing your actual job with slightly better information than you had before.
The companies that benefit most from this story are the ones who get to operate while everyone else stays frozen, watching the news cycle for a confirmation that may never arrive. Don’t give them that. Run the checklist once this week. Write down what you’d want documented either way. Then get back to the work that’s actually in front of you.
I went and checked my own former employer’s careers page while writing this. Half expecting to find nothing, mostly doing it for the example. Found three postings with “AI-augmented” in the title that weren’t there two months ago. Sat with that longer than I expected to. Knowing the framework and actually finding it somewhere real are different feelings entirely.
UK readers: the job posting language check works the same way regardless of where you are. The phrasing shift tends to start in US postings first and lag by a few weeks elsewhere, so if you’re not seeing it yet, that’s more about timing than about being safe.
The companies running this play don’t need to confirm anything. They just need you to keep waiting for confirmation while they make the decisions that actually matter.
Go check your own company’s postings this week. That’s the whole assignment.
Posted the same checklist on X this morning. If you want the shorter version to send to someone who keeps saying they don’t know if they should be worried, that’s the one. Link in bio.
Keep reading with a 7-day free trial
Subscribe to The Displacement Audit to keep reading this post and get 7 days of free access to the full post archives.