A Button and an Action Are Not the Same

In Part 2, we drew ontology with objects and relations. What exists, and how it is entangled. But there is one axis we haven’t yet raised: Action.

If object and relation speak of “what exists and how it connects,” action speaks of “so what do we do.” In an ordinary IT system, actions live outside the data. A button sits somewhere on the screen, and what that button does is scattered across program code. Who pressed it, why, and what changed as a result — none of that is fully preserved anywhere. Action and data drift apart.

Ontology pulls action inside the structure. So for us, an action is not a functional button. It is an act that leaves behind — intact — who did what, when, for what reason, and how that changed the world. The moment an action executes, it becomes a record, and that record always carries a subject.

The Three Questions Every Action Must Answer

Designing actions means making sure every task in the hospital can always answer these three questions:

  • What is its state right now?
  • What can be done in this state?
  • Whose responsibility is that work?

They sound simple. But if you count how many tasks in your hospital can answer these three questions right now, the weight of the question sinks in. Data that cannot answer these three, no matter how much accumulates, is nothing but a number on a report. Only data that can answer becomes the language of operations. This is why the structure of knowing built in Part 2 must meet action in Part 3.

The World’s Frontier Reached the Same Conclusion

Interestingly, Palantir Foundry — often cited as the world’s most advanced operational platform — reached the same conclusion. They say, “It is more accurate to say we design actions than to say we design data.” Data exists to explain action; action exists to leave accountability behind.

They say one more thing. This kind of structure cannot be drawn for you by a tech team or an outside consultant. Only those who have made countless real decisions on the ground can draw it. That is why they are famously known for embedding engineers on the customer’s site.

We stand one step further inside. We are not a company dispatched to the site — we are the site, directly responsible for hospital operations. For eight years running hospitals as an MSO, the person deciding and the person building the structure were the same person, within us. The place the world tries to reach through theory and dispatch, we have already lived through daily operations.

”That’s Just How Everyone Has Done It” Disappears

The biggest change action-structure brings to a hospital is, surprisingly, a change in language.

When something goes wrong, meeting rooms echo with familiar lines. “I only did what I was told.” “That’s just how everyone has done it.” “That’s not our team’s job.” You know these aren’t the words of bad employees. In a structure where nobody’s actions are recorded, even the most conscientious staff can only speak this way.

The moment every action carries subject, timestamp, and grounds, these lines lose their footing. Records speak instead. Who saw which state at what time and executed what — it’s all there. The time once spent arguing over fault vanishes; only the time to discuss what to fix remains. In the hospitals we run, blame games got shorter — not because our staff became nicer, but because the structure made the argument unnecessary.

Records Protect the Hospital

And these records protect the hospital.

When a patient taps confirm on the consent screen in our system, that timestamp is preserved. The moment guidance went out, the moment the patient responded, the moment the consultant moved to the next step — all preserved as a single thread. Later, nobody can say “such a procedure never existed.” Because action is record, and record is responsibility.

For you, the director, what this means is clear. The hospital’s days accumulate together with evidence. And at the most painful moments — when problems arise — the record already stands on the hospital’s side.

It is not only the hospital that is protected. Staff are protected too. For the employee who did their work exactly by procedure, having a record that proves that precision is a great reassurance. In a hospital without records, honest employees can be wronged. In a hospital with records, honesty simply shows. This is one of the conditions that makes good employees stay.

Actions are not functional buttons but declarations that leave responsibility. And those declarations, stacked, protect the hospital.