Why Ontology Isn't Just OOP: Lessons from Theseus' Ship for Enterprise Architecture

The article opens with a common misconception: that ontology and object-oriented programming (OOP) are essentially the same because both abstract real-world entities. The author acknowledges that at a formal level they appear similar, but argues they operate at different levels of abstraction.

1. The Ancient Puzzle: Theseus' Ship

The paradox of Theseus' Ship is introduced: a ship preserved by replacing every plank over time. When all parts are replaced, is it still the same ship? If the old planks are reassembled, which ship is the true Theseus' Ship?

This is not a word game; it asks what maintains identity . Aristotle's four causes (material, formal, efficient, final) are referenced. If only material cause matters, the ship changes when planks are replaced. But the ship's form and purpose remain unchanged — it continues to serve as the same warship. The reassembled ship has the original material but lost its function, becoming a mere exhibit.

Key insight: Continuity of existence is maintained not by material but by structure and purpose. Material can be replaced without loss of essence.

2. A Cup: What Are We Really Referring To?

The author observes various tea vessels — clay pot, porcelain cup, glass, bowl — yet all are recognized as "tea utensils." The defining feature is not material, shape, or handle, but a stable structure: a container for holding liquid for drinking.

Ontology is not a specific cup; it is the structural principle that allows different cups to be classified as the same kind of being. Focusing on changing appearances ("form") mistakes the variable for the invariant; seeing the holding structure and purpose ("nature") grasps the essence. This echoes the Buddhist caution against clinging to appearances.

3. Entity vs. Ontology: A Difference in Level

Entity = concrete existence (a cup, a ship).

Ontology = structural principle (the container's holding structure, the warship's sailing structure).

Entities change; ontology remains stable. Tracking only entities leaves one dragged by change; understanding ontology lets one recognize continuity within change.

OOP concerns implementation structure — how to organize code and manage complexity. Ontology concerns existential structure — why an object holds together, what rules preserve its identity. One operates at the engineering level, the other at the level of being. Their forms may resemble each other, but the depth of abstraction differs.

4. Bringing the Thinking Back to Reality

Enterprises constantly "upgrade": system rebuilds, platform migrations, data integration, architecture rewrites — like replacing planks on Theseus' Ship. Yet many organizations find logic fragmenting across systems.

The root cause is often structural, not technical. Without a clear "existential structure," each system replacement causes cognitive rupture: customer definitions drift, rules scatter in code, decision logic becomes untraceable. This is Theseus' Ship replayed in modern organizations.

When ontological thinking enters the modeling layer, the approach shifts: model around the enterprise's essence, not around systems; make rules explicit structural assets rather than hidden code. This is not a technical upgrade but a cognitive level shift.

5. Conclusion

Ontology is not mysterious; it persistently asks: what stays the same amid change? When this question enters enterprise modeling and digital construction, it ceases to be a philosophical proposition and becomes the foundation for governing complex organizations.

Understanding ontology is not for appearing profound. It enables one to discern structure, maintain continuity, and keep direction in an era of constant technological turnover. That is ontology's true value.

Reference: Theseus' Ship, Aristotle .