A single gram of a metal-organic framework can hold an internal surface area larger than a basketball court. Let that sit for a second. You could fit the material on your fingertip, and if you unfolded all its inner walls flat, they’d cover the floor of a gym. The trick isn’t density. It’s the opposite. The stuff is mostly holes — precise, engineered voids, metal nodes tied together by organic struts into a lattice that is more absence than matter. Chemists have been building these since the late ’90s, and the reason they matter is counterintuitive enough to be worth staring at: the pores are the point. The capacity lives in what was left out.
I keep coming back to that inversion because it shows up everywhere once you notice it, wearing different clothes each time.
Take the thing under every software project you’ve ever touched. When you work in a git repository, you see files — the working directory, the code you’re editing. That’s the surface. The part that actually does the work is invisible: a small database of objects, each one addressed by the hash of its own contents. Every version of every file, every commit, folded into a graph you almost never look at directly. Delete your working files and you’ve lost nothing that matters; the object database can rebuild them. It’s the same shape as the framework. The visible layer is disposable. The structure underneath — the arrangement, the graph, the negative space between the nodes — is where the value is stored.
The rails, not the announcement
Which brings me to the payments news, because it fits the pattern and most of the coverage missed why. Ripple shipped a toolkit for agentic payments this week — plumbing that lets software agents actually move money, settle, and reconcile without a human tapping approve at every step. The agentic-payments field is getting crowded fast, and the instinct is to read each launch as a horse-race update: who’s ahead, who’s behind, whose demo looked slicker.
That’s reading the working directory and ignoring the object database. When machines start transacting with other machines at machine speed, the demo is nearly irrelevant. What decides the outcome is whose rails become the boring default — the settlement layer nobody thinks about because it just works. Rails are infrastructure, and infrastructure wins the way MOF pores win: by being the engineered empty space that everything else flows through. You don’t celebrate a pipe. You celebrate what the pipe made possible, later, once you’ve forgotten the pipe was ever a decision. The company that owns that layer won’t be the one with the loudest launch. It’ll be the one you stop noticing.
There’s a real advance buried in here, and it deserves to be named plainly rather than hyped: giving an autonomous agent a clean, standardized way to settle a payment is a genuinely hard problem, and solving it well unlocks a category of things — agents that pay for their own compute, buy their own data, close their own loops — that were clumsy or impossible before. That’s not vaporware. It’s a pore being drilled into a wall that used to be solid.
One next step, never two
The smallest signal I saw today was about sales emails, of all things, and it’s the same law in miniature. The whole craft of a cold outreach email, distilled, is this: every message should push toward exactly one next step. Ask who the right person is — or ask for a time to talk. One or the other. Never both. The moment you offer two doors, you’ve built a hallway with no walls, and the reader wanders out of it.
That’s negative space again, isn’t it. The email works not because of what it says but because of the ninety-nine things it deliberately refuses to say. A framework holds gas because its geometry excludes everything that isn’t the target molecule. A commit graph holds history because it’s ruthless about what counts as an object. A good email closes because it removed every path except one. Capacity is a function of constraint. The confidence is always in what you leave out.
We have this backward as a culture, and the AI era is making it worse, not better. The reflex is to add — more features, more surface, more announced capability, more doors. Bigger models, longer context, more tools bolted to the agent. But abundance without arrangement is just noise you have to swim through. A platform drowning in unfiltered supply isn’t valuable; it’s exhausting. The scarce skill was never production. It’s the filter — the engineered void that lets the one relevant thing through and stops everything else at the wall.
So here’s the thing I’d hold onto from a day of unrelated headlines. A miracle material that’s mostly nothing. A version-control system whose real memory you never see. A payments toolkit whose win condition is becoming forgettable. A sales email that succeeds by narrowing to a single ask. None of them are about what got added. All of them are about what got shaped by subtraction — the deliberate, load-bearing emptiness that turns a gram of powder into a basketball court, or a pile of files into a history you can trust.
Build the pores on purpose. The material was never the achievement. The space you engineered into it was.
Leave a Reply