When the same three companies are each other's customer, lender, and supplier, a miss in one contract hits the others. Founder @AnishDAC maps that circle.
These are genuinely nice charts, @a16z. But you skipped circular financing, so I made a quick video on it (see below 👇).
A little about me and why this is relevant. The weekend before Lehman failed, I was on the advisory team that helped issue their final CLO. I spent the whole great financial crisis (GFC) in CDOs, CLOs, and CDS. What I took away from that period of time was EVERYTHING runs through the agreements, and those agreements are all interrelated.
So when Oracle’s 5yr CDS hit a record last week, wider than 08, I decided it was time to pay attention. We know debt informs equity, and when protection gets that expensive, you really have to start asking what if?
So let's follow the money:
→ Nvidia funds OpenAI
→ OpenAI buys compute from Oracle
→ Oracle buys chips from Nvidia
But what if demand drifts to cheaper open models (a very real concern at the moment)?
• The labs would grow slower than the projections they raised the debt on
• But they’d still owe the same
• Debt Service Coverage Ratio takes a hit
• Each company’s revenue is another one’s bill, so the whole circle of participants eventually feels it
Btw, you only really see this coming with certainty by understanding the agreements and how they work together. Normally, this takes weeks with intense iteration. But you know what? The market won’t give you weeks when it really matters... The movie Margin Call had it right: be first, be smarter, or cheat.
I’d rather be the first two, never the latter. This is one reason I built DAC: so anyone can SEE and understand the risks and opportunities through scenarios embedded across agreements, before you need them, or instantly if required.
It is very important to know your options before the trade unwinds because when it unwinds... it unwinds fast!
Now, I am not saying this will happen, but it is important to know what-ifs so one can plan and be positioned to react accordingly
75
One Xerox bond issue (yup, they're still in business, believe it or not) lost 13.4% of its market value in two weeks. Roughly $45m.
Here’s why knowing your agreements matters to your money.
Xerox’s $500m of second-lien notes due 2031 traded from 67 on Feb 4 to 58 on Feb 18, 2026.
During that period, Xerox moved IP into a joint venture and raised $450m. Existing debt documents weren’t amended.
Ropes & Gray explained the opening: the venture fell outside the definition of “subsidiary,” so key protections aimed at subsidiaries didn’t reach it.
The permissions were already there.
And the refinancing pressure is building. Octus’s September data shows North American term loan B and high-yield maturities of:
• 2028: $597bn
• 2029: $646bn
• Combined: more than $1.2tn
That gives stressed borrowers more reason to explore LMEs.
Do you know whether your agreements let them:
• Move assets out of lenders’ reach?
• Put new debt ahead of yours?
• Waive protections without your consent?
Those vulnerabilities and protections matter to your price, leverage and recovery.
So does the institutional memory: what was negotiated, why, and what changed. Too much of it sits in spreadsheets, emails, Word docs and counsel’s head.
You need that knowledge available before someone acts on a path you didn’t see.
The video traces Xerox through eight documents and 24 connected steps.
Know your options before you need them. 👇
I’ve written before about what I call Anish's agreement flywheel. Agreements work because of three things: governance, consensus, and enforcement.
NVIDIA just launched the Open Agent Safety Platform with OpenShell and Sentry. That’s a serious step on enforcement.
OpenShell puts a secure runtime boundary around what an agent can touch. Sentry sits out of band and can quarantine an agent in milliseconds if it pushes past those limits. The boundary lives outside the model and the agent harness, which is exactly where it needs to live once agents start taking on real work.
That leaves the other two parts of the flywheel.
Governance is the agreements themselves. Who can act, under whose terms, with what spend, handoff, or return rules. Written so a system can check them before the agent acts.
Consensus is how people and agents settle those rules, revise them when something breaks, and keep a record of what was actually authorized.
That’s what we build at DAC. NVIDIA is nailing enforcement. We can handle governance and consensus, so the safety stack has clear, checkable agreements to enforce.
That AI Trust layer works when all three spin together in the same direction.
AI agents are taking on more critical work.
The security behind them needs stronger boundaries.
We’re building the NVIDIA Open Agent Safety Platform with partners across the industry to help people put agents to work with greater confidence.
Hear from @JensenHuang:
hyperscalers, lenders, private credit: do you know what your agreements commit you to, what protects you and when your options change?
if a tenant goes bust, who has to step in? who can decline? what do they owe if they do?
DAC’s what-if lets you test that before it happens. change the assumptions, see the available paths and trace the answer back to the clauses.
quick illustration below using a public Google / Cipher / Fluidstack agreement.
know your options before you need them. 👇
The answer is @Amazon, Muse can't do @amazon.... but don't worry!
@alexandr_wang watch @Muse try to buy headphones on Amazon, get shut down, then book Hawaii to cope 😂 then he needs a fit, headphones, food. your partners are about to have a day.
scaling agentic commerce without liability controls can get messy fast. ebay / paypal already taught us this: when a buy goes wrong, who owes what? their user agreements and protection policies set the rules for disputes. these were built mostly for humans and mostly after the fact but agents definitely need those rules before they hit buy.
But that's what we do: we make ToS and other agreements usable by agents. map them into rules, check each action, allow or block it, then monitor and track payment and delivery.
i got you. easier to show. video below👇
@vishalshahis @MattPRD @bigT_sheesh @dps @natfriedman @AIatMeta @finkd
🤖 Made with AI
This quoted post is unavailable.
Retrieval can tell an agent what an agreement says.
It can't reliably tell you whether a proposed sequence of actions is permitted once defaults, exceptions, precedence, and consent requirements start interacting.
That's where executable agreement logic comes in.
an llm reading a loan agreement has to infer structure, resolve cross-references, track state, and explain itself in one pass. that's why you can't audit it.
we compile the agreement into a graph first. reasoning is traversal, not inference.
1
106
agreements are supposed to be the guardrails. the hard question is whether an agent can walk a path those guardrails already leave open. this walkthrough by founder @AnishDAC shows one.
There’s a lot of concern right now about AI acting against our interests.
Agreements set the guardrails. Sometimes those guardrails leave room for actions we don’t want.
“Can they move our collateral without our consent?”
In this example, yes. The lender’s agent checks the rules and flags the risk while the transfer is still pending.
You should be able to see those guardrails, understand what they allow and monitor what happens next.
That shouldn’t stay buried in the fine print.
Monitor · 2 of 4
2
45
With all the discussion about AI’s progress this week, I keep coming back to how we govern what these systems actually do.
When an answer or action depends on an agreement, you should be able to see the rules behind it.
Here’s what I mean.
“Can I stop a prepayment?”
The answer might take you through three agreements. You should be able to follow the reasoning and see the language behind it.
If we use agreements to coordinate economic activity, why would we expect AI agents to operate without understanding them like this?
Understand · 1 of 4





