A durable-execution platform’s own outages counted against its tenants’ retry budgets and left their runs marked Running, so from inside a tenant’s code the platform being down looked like the function being slow. A run record needs a way to say whose failure an attempt was.
A sample ID like SITE04-PRT19-2021-00381 is four definitions promoted into a key. The audit trail can correct any column in the record and can’t touch the key, and then the key gets printed on a tube that sits in a freezer for decades. No steward ever gets to retire that one.
A shared platform ends up at the strictest requirement any of its consumers carries, and onboarding is when that gets decided. Vendors fence off the strict part. An internal platform team usually can’t, and the mark only ever moves up.
Naming a system of record settles which copy to believe after two numbers already disagree. The fork itself gets created at write time, by every screen that leaves a copied field editable.
A public API can force you off an old version by making the endpoint go dark on a date. An internal platform has the same compatibility burden and no way to ever pull that lever, so nothing it ships ever gets retired.
Months ago I listed what a system needs before an agent can run unattended and treated the list as finished. It wasn’t. A stop button handles the runaway. It does nothing for the run that dies on step nine of fourteen.
The moment you harvest a platform out of an app, the app stops being something you can change quietly. That standing cost lands hardest on the team that built it, and most extraction plans never budget for it.
I argued the way to find a platform’s real boundary was to watch the second team that wanted in. The catch I keep running into: two consumers tell you what they have in common, and that’s not the same thing as what the platform is.
Someone asked how many samples we have and three systems gave three different numbers. The dependency order behind vocabulary, ontology, semantic layers, catalogs, and contracts, and why the piece everything stands on is a role most orgs never seat: the data steward.
Birgitta Böckeler’s harness-engineering framework treats iteration as human work. Someone watches, notices, edits the rules. That assumption breaks the moment agents run overnight. The next move is sensors with memory.