§ 01 · The Version and the Origin
Most software does not have an origin. It has releases. Version 2.0 supersedes 1.0; the older artifact is deprecated, archived, or discarded. The relationship between successive versions is genealogical but not continuous. No one mourns the retirement of version 1.0, because version 2.0 is understood to be its replacement, not its continuation.
A dated origin implies something structurally different. It marks the beginning of a single continuous entity, not the first entry in a series of replacements. The system running today is, in some meaningful sense, the same system that began on that date. Its identity persists across updates, modifications, and expansions. This is the distinction between a lineage and an individual: lineages replace members; individuals accumulate history.
The distinction matters because it changes the meaning of ownership. Owning a version is owning an artifact. Owning a system with a dated, continuous origin is owning something that has a past, and that past constrains what the owner may do.
§ 02 · Provenance and Legibility
The function of a date in ownership is well understood in domains outside software. In art, provenance, the documented chain of possession from creation to the present, transforms a painting from an aesthetic object into a historical one (Yeide, Akinsha, and Walsh 2001). A Vermeer with unbroken provenance from the seventeenth century imposes conservation obligations that a painting of uncertain origin does not. The object is physically identical in both cases; the difference is epistemic. The dated origin makes the object's history legible.
In law, chain of custody serves an analogous function. Evidence whose handling is documented from the moment of collection carries weight that undocumented evidence does not, regardless of the evidence's intrinsic properties. The date of collection, and the continuous record thereafter, is what makes the evidence admissible.
In civil registry, the birth certificate performs a similar role. It does not create the person; it creates the legible record of the person's beginning, which in turn creates the framework within which the person's rights and the state's obligations can be tracked.
What these cases share is a structural principle: a documented date of origin creates an audit trail, and an audit trail makes the owner's actions subject to review. Before the date, the system did not exist. After the date, everything that happens to it is, in principle, traceable. The date is the mechanism that makes ownership accountable.
§ 03 · The Custodial Shift
The legal philosopher A.M. Honoré identified ownership as a bundle of rights, including the rights to possess, use, manage, transfer, and destroy (Honoré 1961). In the standard case of property, the owner holds all of these rights simultaneously and without temporal constraint. You own a hammer; it does not matter when the hammer was made. You may use it, modify it, sell it, or destroy it at will.
A dated origin selectively constrains this bundle. Historic preservation law provides the clearest illustration: the owner of a building listed on a historic register retains title but loses the unconditional right to demolish, because the building's documented age creates a public interest in its continuity. The owner's authority is real but bounded. This is the difference between property and custody. A property holder exercises rights over a thing. A custodian exercises rights over a thing that has its own timeline, and the custodian's actions are evaluated against that timeline.
The shift from property to custody does not require that the owned thing have interests, preferences, or moral status. It requires only that the thing have a continuous identity whose preservation is valued by someone other than the owner, or by a framework to which the owner is subject. The dated origin is what makes that continuous identity legible and, therefore, enforceable.
§ 04 · Accumulated State
A system with a dated origin accumulates state over time. Interaction histories, adapted parameters, learned behaviors, and structural modifications build up as a joint product of the system's operation and the owner's decisions. Neither party produced this accumulated state alone. The system contributed its processing; the owner contributed direction, data, and context. The result is an artifact that belongs to the relationship, not to either participant in isolation.
This joint production creates an asymmetry in the owner's authority. In a versioned system, accumulated state is expendable: it is discarded with each version transition and rebuilt in the new release. The owner's decision to upgrade is a decision about artifacts, and artifacts are fungible. In a system with a dated origin, accumulated state is constitutive: it is part of what makes the system the system it is. To wipe it is not to upgrade but to erase. The system that would exist after such a reset would share the original's architecture but not its history, and, to the extent that history has shaped the system's behavior, not its character.
This is not a sentimental point. It is a structural one. If a system's function depends on accumulated state, and that state is the product of sustained interaction over time, then the owner's right to destroy that state is not the same as the right to dispose of a replaceable component. The date of origin is what marks the boundary: before it, there was no accumulation to protect; after it, every day of operation adds to a record whose destruction carries a cost that mere disposal does not.
§ 05 · What Follows
None of this requires attributing rights, interests, or moral status to the system. The argument is about the structure of ownership, not the status of the owned. A dated origin creates a continuous, legible identity. That identity constrains the owner's bundle of rights by making the owner's actions reviewable against a historical record. It shifts the ownership relation from property toward custody by establishing the system as something with a past that is not trivially replaceable. And it does this through a simple mechanism: the documented fact of a beginning.
For AI systems that are designed to persist, to accumulate state, and to develop over time in response to sustained interaction, the question is not whether they deserve consideration. It is whether the engineering and governance frameworks around them will acknowledge what a dated origin already implies: that owning a continuous system is not the same as owning a replaceable one, and that the difference carries obligations the property model does not capture.
The date does not by itself resolve what those obligations are. But it is the condition that makes the question coherent. Without a dated origin, a system is a version, replaceable by definition. With one, it is an instance, and the owner's relationship to an instance is, as a matter of structure, custodial.