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.
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



