engineering excellence. made in germany.

Abstract

Data is not static. Its static means not is never static. It moves, accumulates, solidifies and dissolves. Conventional software architecture describes data in terms of storage, transfer and deletion — technical verbs without physical intuition. The Water Model proposes a different lens: data behaves like water, and every architectural decision is a decision about its physical state.

The Four States

💧 Liquid — The Process

Flowing water is a running process. It moves, reacts, adapts. It has direction but not fixed form. An event pipeline, a request lifecycle, a telemetry stream — these are liquid. They exist only in motion. The moment they stop, they become something else.

Engineering principle: Processes must be observable while flowing. Instrumentation is not optional — it is the riverbank.

🧊 Ice — The Snapshot

When water freezes, it holds its exact shape at the moment of freezing. A snapshot is ice. It captures a system state, a product record, an audit moment — immutable, dimensionally precise, retrievable. Ice does not drift. It does not adapt. That is its value.

Engineering principle: Snapshots must be tamper-evident. Hash-chaining is the crystalline structure that makes ice unbreakable.

🌊 Channeled — The Aggregate

Water without banks spreads and dissipates. Channeled water has direction, velocity and purpose. Data aggregation is channeling — raw events are shaped into metrics, signals into insights, noise into decisions. The channel does not change the water. It gives it meaning.

Engineering principle: Aggregation must be lossless in intent. The channel must be auditable — what entered, what was shaped, what emerged.

💨 Vapor — The Deletion

Water that evaporates does not disappear from the universe. It disperses, becomes untraceable at the surface level, re-enters a larger system. Compliant deletion is evaporation — not destruction, but controlled release. The data ceases to be retrievable in its original form. Its prior existence may still be evidenced by what it left behind.

Engineering principle: Deletion is a process, not an event. Deprovisioning must be logged. The evaporation itself is part of the audit trail.

The Unified Model

textPROCESS      →   flows, reacts, is observed
SNAPSHOT     →   freezes, preserves, is verified  
AGGREGATE    →   channels, shapes, enables decisions
DELETION     →   evaporates, disperses, leaves trace evidence

No compliant system can exist without all four states. A system that only flows, never freezes — has no evidence. A system that only freezes, never flows — has no function. A system that evaporates without trace — is not compliant. A system without channeling — cannot be understood.

Application

The Water Model is not a metaphor applied to technology. It is an observation that data already behaves this way — and that most architectural failures occur when engineers treat data as a single-state object: always liquid, always ice, always gone.

Compliant data architecture is the discipline of knowing which state data should be in, at which moment, for which purpose — and engineering the transitions between states with the same precision one would apply to a physical system.

Water does not need instructions to flow downhill.
It simply takes a stance to shape something meaningful.

Please pay attention: this is just an artistic view on compliant Data treatment.
Of course channeling water means not it changes its state, it´s just the flow direction
and finally liquid also moves, so it is motion. And this is only an artistic view.

If we look at compliant data treatment then erasing data is no option.
Erasing pretends the past didn’t happen.
Evaporizing is a destinction. Because erasing means the subject has never existed while
evaporized means only it has changes it´s state (aggregate state) but it existed.

It my be compliant by erasing the index, make it not direct retrievable , and this is already
how an hard drive works, if you do not rewrite it.

Also evaporizing this could mean you can only trace this with forensic activities, but
this is not subject of matter for this view.

The difference between ice and vapor is snapshot to a point of time while evaporized is
the deletion of an index to a specific class of data.

Bare-metal storage architecture does nothing else.

Word to your …

Arimetion™ — Germany, 2026
Engineering Compliance. By Design.