Enterprise storage policies frequently begin with a clock. Keep information here for 30 days. Move it there after 90 days. Send it somewhere cheaper after a year.
Age is convenient because it is objective, measurable, and easy to automate. But the age of information rarely tells us what that information means to the organization.
A file turning 90 days old is not a business event.
Age is a characteristic, not a lifecycle
Information can be old and critically important. It can be new and disposable. It can become valuable again years after its original use declined.
Retention obligations can change. Legal requirements can change. Security requirements can change. Relationships can emerge. New analytics or AI workloads can make historical information operationally important again.
None of those changes are adequately represented by a timestamp.
Information has a state
A useful lifecycle model begins with the information itself: its identity, relationships, business value, risk, retention requirements, protection requirements, security classification, integrity, availability, provenance, and other governance-relevant context.
Savartus refers to this richer understanding as governed information state. The Enterprise Data Lifecycle™ architecture formalizes that concept through the Enterprise Data State Vector.
The objective is not to collect metadata for its own sake. The objective is to establish enough context to make an explainable governance decision.
Storage state is different
Information lifecycle and storage lifecycle are not the same thing.
An archived dataset might remain Archived while moving from low-cost storage to high-performance infrastructure because an AI workload suddenly requires it. Its storage changed. Its lifecycle state did not.
Likewise, information can move into a different governed lifecycle state without requiring an immediate storage migration.
Move information when its requirements change
That leads to a different approach to lifecycle management. Instead of asking how old the information is, ask what the organization currently requires from it.
Policy can then determine whether information should remain active, receive additional protection, move to preservation, become eligible for disposition, or be made more readily available.
Age can still be one signal. It simply should not be the governance model.