Can You Delete the Table?

That forum thread is a petition to a lord. It is polite, it is reasonable, and it will be read by someone whose job is to decide whether your request fits the estate. The word in the corner of your screen is a courtesy title, the kind a duke gives a younger son: real enough to be addressed by, never enough to own the land.

We do not usually talk about software this way. We talk about features, prices and ease of use. But underneath every app is an older question, the one every human order has always answered first. Who gets to declare the structure, and who only gets to write inside it?

Rank is what you are allowed to declare

Start with a blank sheet of paper. Before anything is drawn, every place on it is equally anything. Nothing is in front of anything else. I think of it as a kind of superposition: all things and no things at once. Then you draw a single point in the center, and for the first time there is a foreground and a background. That is the first distinction there is. It comes before symmetry, before significance, before fairness, because you cannot have any of them until something stands in front of something else. This is why I treat hierarchy as the first of the cardinal ideas. Rank and order begin with the first declaration.

A database makes this literal. The table is the field. The columns are the frame drawn on it. The rows are the marks people make inside the frame. Engineers describe what you can do to data with four verbs: create, retrieve, update, delete. What almost nobody notices is that, for nearly every person who has ever used software, those four verbs apply only to rows.

You can add a row. You can read some rows. You can edit a row, and sometimes delete one. You cannot add a column. You certainly cannot create a table, or drop one. Most people have never imagined that they could, and if they did, they would picture a hacker. Even reading is rationed. There are seven thousand records in the system and you are shown three. That is not a missing feature. It is your rank, expressed in permissions. Software, at bottom, is the layer that hides those four verbs from you and decides on your behalf how much of them you get.

The chief executive is not exempt. The head of a large company cannot add a column to the table inside the CRM his company pays for. In the order that governs software, he is a very well-dressed tenant.

We have watched an order break before

Feudal rank was settled at birth. The firstborn inherited the land. The third son had no land to inherit, so some third sons went to sea, and a few came home with pepper and silk to sell. At that point something strange happened. The shipowner found himself thinking of his elder brother, the lord, as a customer. Feudalism had no word for customer. It had no word for profit, or competitor, or market price. A lord did not ask what his land would fetch. A new order arrived carrying a vocabulary the old one could not even say. I have written about that marker in The Blender Marker, and about how the castle paid for its own replacement in Feudalism Didn’t Collapse.

What matters here is that neither side felt threatened. The lords loved the merchants: they got spice without risking their own ships and men to pirates. The merchants loved the lords: they were the best customers alive. Early on, Dutch investors put money into a single voyage and waited to see whether the ship came home. That was the whole instrument. Then in 1602 came a company chartered to raise soldiers, build forts, sign treaties and make war. Nobody would call the Dutch East India Company a department of the state. If anything it was nearly a state of its own.

Later the money began buying the titles. By the Gilded Age the American barons held no titles of nobility. Their fortunes were built on railroads, oil and banks, not on inherited land. In 1895 a Vanderbilt daughter married the Duke of Marlborough; the railroad supplied the money, much of it to keep up the indebted ducal palace, and the old estate supplied the title. Today nobody books a king as the keynote speaker. Kings still exist. Monarchs still reign, and they still have land. They simply do not run your day. It took centuries.

Super admin is a different order, not a better feature

Here is what is new. An AI agent creates and drops tables all day long. It adds columns, reshapes schemas and builds the software that sits on top of them. Pair one with a database that belongs to you, a personal Postgres instance like Supabase, and you are no longer asking anyone. You are the super admin. A twelfth grader in Thailand can do this. So can a forty-three-year-old mother who homeschools her children and keeps the lessons, her job, the dentist, the prescriptions and the carpool in one database of her own. So can a CEO.

The logic is short. If I can delete the table, I am not in the order where a vendor governs the table. My rank changed, so my order changed. That is why I do not accept the comfortable view, most popular among people who build software, that AI is just more software. A serf granted his plot on a hundred-year lease has had his terms improved inside feudalism. Tell the lord you are building a hotel on it and you find out quickly that you were not authorized for that level. The break is the deed with no conditions.

You can see who has not noticed by listening to the announcements. Every software company now has a new AI feature inside its product, and you may use it as long as you use it exactly the way they built it. You can change the prompt, but it is a prompt inside a prompt inside a prompt. It is a nicer lease.

The old order also reveals itself when it squeezes. After Broadcom bought VMware in late 2023, it stopped selling perpetual licenses in favor of subscription bundles, and many customers reported steep increases they could not easily escape, because moving their virtual machines elsewhere is hard. In the old order, the only reply available is yes, sir. That strategy can work for a few years. It is also the best advertisement for rolling your own that anyone has ever written, and every dollar it extracts becomes somebody’s migration budget.

1. “Can you delete the table?” becomes the buying question.

   Before adopting any system, people and companies will ask what layer they get to declare. A title that says Admin will impress nobody. The useful answer will be yes or no.

2. Your database first, theirs second.

   Work will happen in a system of record the person owns, and the company’s CRM, school portal or patient system will receive a scheduled copy. Enterprise software becomes the place you report to, not the place you work.

3. Built-in AI features will read as courtesy titles.

   Assistants that live inside a vendor’s frame will be used for what they are good at and routed around for everything else. People will run their own agent beside the platform, and outside it, as naturally as they now carry their own phone into the office.

4. Terms of service turn generous.

   A product built for billions of individuals competes on its terms. The winning ones will say something no enterprise license has ever said: I do not inspect your database. You are the super admin.

5. Software companies become nobility.

   They will still exist, still be rich, still serve billions of customers. They will still be large in 2026 and in 2027. But within a generation they will hold the position the crown holds now: real, respected, ceremonial, and no longer the thing that decides how your day goes.

I teach this with one exercise. I ask my advanced students to set up a database that is unmistakably theirs, one their AI can manage, and then answer the four questions in Figure 01 out loud. Then I ask them to do all their work there first and let the enterprise system receive a copy on a schedule. Nobody needs convincing after that. They feel the rank change before they can name it, and it feels good, the way every promotion does. People who know they are the super admin walk differently. They talk like a king, and they negotiate like one. I wrote the field-guide version for contractors in Own Your CRM, and the version for organizations in Bring Your Own AI. This is the reason underneath both.

How this could be wrong

Already true

Anyone with an AI agent and a personal database can create and drop tables today without asking a single person. The capability exists. The habit does not yet, and neither does the self-image.

What has to happen

People have to believe they are allowed. Rank is mostly a state of mind until it is exercised. And the things a vendor quietly provided, security, backups, recovery when something breaks at two in the morning, have to become things a person’s own AI does reliably.

Where I am probably wrong

Sovereignty sends a bill. Feudalism lasted as long as it did because protection was worth the rent, and many people may decide they would rather be well-kept tenants than kings of a leaky castle. There is also a floor under every personal stack: somebody’s cloud. If the hosting layer consolidates and starts writing terms the way the software layer did, I will have described a revolution that moved the throne one floor down. My bet is that hosting stays easy to swap, and a landlord you can leave in an afternoon holds no leverage. If that stops being true, so does this.

Go back to the forum thread from three years ago. In the world coming, nobody petitions. You tell your AI when the shipping email should go out, and it changes the table. The word in the corner of the screen can still say Admin. It will finally mean it.

You draw the table now.