You subscribed to our newsletter on our website or through one of our other channels. If you no longer wish to receive our emails, unsubscribe in the footer.
On March 31, 2026, 30,000 Oracle employees received a 6 am email from "Oracle Leadership." No call from HR. No meeting with a manager. One email. Gone.
Oracle is not struggling. The company reported $6.13 billion in net income last quarter, up 95% year over year. It has $553 billion in remaining performance obligations. It cut 30,000 people to free up $8-10 billion per year to build AI data centers.
Meta cut 8,000 people three weeks later. Microsoft offered voluntary buyouts to 7% of its US workforce. Amazon has cut more than 30,000 jobs since October.
That is not a wave of bad news. That is a capital event cluster executing.
THE SHIFT NOBODY IS NAMING
The 6 am email was not a surprise to anyone watching the signals. It was the final confirmation of a cluster that had been forming for over two years.
Most people don't have a system to watch the signals. They read the headline when it lands, try to make sense of it, and move on. By then, the positioning window will be 18 months old.
Capital event clusters form in four stages.
Stage 1: Policy origin.
Stage 2: Multi-agency alignment.
Stage 3: Funding architecture published.
Stage 4: Implementation confirmation.
Oracle's 6 am email was Stage 4.
The people who saw Stage 1 in 2023 had two years to position themselves.
Here is exactly what the Oracle cluster looked like at every stage and how you build a system so you never miss Stage 1 again.
HOW THE ORACLE CLUSTER FORMED
Stage 1 — Policy Origin (2023) Oracle's capex was $6.9 billion in 2024, already elevated, signaling infrastructure intent. The company announced plans to spend $10 billion on data center expansion in 2025. That was the policy origin signal: a major platform player publicly committing to infrastructure at a scale that only makes sense if the demand is already locked in.
Stage 2 — Multi-Agency Alignment (January 2025). On January 21, 2025, President Trump formally announced the Stargate Project as a $500 billion AI infrastructure joint venture among OpenAI, SoftBank, Oracle, and MGX. Oracle is committed to developing 4.5 gigawatts of AI data center capacity. Remaining performance obligations jumped from $80 billion in Q3 2024 to $455 billion by Q1 FY2026, a 359% increase. The demand was confirmed. The build was funded. The workforce math was already written.
Stage 3 — Funding Architecture Published (Late 2025) Hyperscaler combined capex hit $600 billion for 2026. Oracle took on $58 billion in new debt to fund construction. The Stargate campus in Abilene, Texas, went live. Five new sites were announced. The cluster was no longer a signal — it was a published blueprint.
Stage 4 — Implementation Confirmation (March 31, 2026): 30,000 employees. One email. 6 am.
THE FORMULA
Capital Event Cluster = Policy Origin + Multi-Agency Alignment + Funding Architecture Published + Implementation Confirmation
Most people enter at Stage 3 or 4. The leverage is seeing it at Stage 1 or 2.
There are six active AI Infrastructure and workforce clusters: CHIPS Manufacturing, Clean Energy, Defense AI Modernization, Workforce Legislation, and National AI Workforce and Adoption.
Each one is at a different stage. Each one has a different window.
YOUR 3-STEP MONITORING SYSTEM
Step 1 — Pick your cluster. (2 minutes) Go to our capital event clusters page and identify which of the six active clusters your expertise touches. Pick the one where you already have context. That is your entry point.
Step 2 — Map the Oracle pattern to your cluster. (8 minutes) Using Oracle as your template, search for Stage 1 and 2 signals in your cluster right now. Look for: major capex announcements, multi-agency policy alignment, platform players publicly committing to infrastructure at an unusual scale. If you are only finding Stage 3 and 4 signals implementation confirmations, layoffs, and RFPs, the window is closing. If you find Stage 1 and 2 signals, you are early. Write down what stage your cluster is in.
Step 3 — Build the Digital Employee that monitors for clusters of capital events. (5 minutes) A Digital Employee is not a chatbot. It is a role tied to a capital event tied to a revenue outcome. Here is how you build one.
Go into your favorite AI tool, and put this into the chat.
“How would you build capital event cluster monitoring skills for [X purpose] as an L9 futurist for the Federal Reserve and World Bank, so I can spot capital event clusters forming and position myself for them before others do?
Here is a link with information about capital event clusters: compoundleverage.com/explained/capital-event-clusters/Here is a link to a paper on the trillion-dollar clusters forming: situational-awareness.ai/racing-to-the-trillion-dollar-cluster/
Ask me follow-up questions about my background, my goals, my fears about the future, and how I want to take action on the cluster data. [Paste your resume and personal playbook here.]
Then configure a DE Skill I can use to monitor Stage 1 and 2 signals in that cluster policy shifts, capex announcements, multi-agency alignment moves, and surface them before they become headlines. I want it to have a list of moves I can make, the blindspots I may be missing, and a scoring system on how to take advantage of the cluster that is forming.”
That is your monitoring system. Your thinking sets the lens. The DE runs the watch. Then schedule it to run on a schedule.
THE THINKING SHIFT
Oracle's 30,000 people did not lose their jobs on March 31, 2026. They lost them in 2023, when the Stage 1 signal appeared, and nobody built a system to read it.
The strategists positioned inside the window right now are seeing how announcements like STARGATE would shift spending before they are confirmed, and they are building their entry angle before the 2026 news hits the wires.
That is what Capital Event Intelligence looks like.
And it starts with a monitoring system you can build in 15 minutes.
To understand how capital event clusters form, read more about it here.
Marvin