An Organization Through Change

The cooperative and the roles around it

Cedar Farm Cooperative has the illustrative RID 451.WMW78429ZAZXP882 (Cooperative) and the registered name rrn:451:cedarvalley:us-ca:cedarcoop:organization/cedar-farm-cooperative. Around it stand several parties whose roles are easy to blur. The Cedar Valley Network is the namespace authority that registered the cooperative's identity. The cooperative operates North Field, but a family trust owns the land. Its members are growers, some of whom also belong to Cedar Valley Growers. Each of these is a different relationship, and only one of them is the act of issuing an identity.

The diagram's arrows are hypothetical assertions, each with its own source and authority. The issuer gained nothing over the cooperative by registering it; the cooperative gained nothing over North Field by operating it; the members did not become owners of the cooperative's identity by joining. Keeping these as separate, dated relationships is what allows any one of them to change while the others, and every identity involved, stay put.

A new name, the same cooperative

In 2032 the members vote to rename the organization Cedar Valley Farm Cooperative, to reflect growers who have joined from across the valley. Under a naming scheme that treated the name as the identity, this would be a crisis: contracts, permits, certifications, and grain-buyer records would all point at a name that no longer exists. Under RSM ID it is a registered succession of names.

The cooperative's authority registers the successor name rrn:451:cedarvalley:us-ca:cedarcoop:organization/cedar-valley-farm-cooperative. Both names now map to the same RID, and the original is never reassigned to anything else. A grain buyer whose 2031 contract cites the old name can still resolve it and arrive at the same cooperative, with the record showing which name was current when. The RID itself was never touched, because it never contained the name, and the identity lifecycle does not move either: a rename is not a lifecycle event.

Directors, facilities, and systems change hands

Boards turn over. In 2032 the cooperative also elects new directors and appoints a new manager. None of these people are the cooperative, and their arrival changes governance metadata — who may act for the organization, who signs on its behalf — not its identity. The directors are persons with identities of their own, as A Person Before an Affiliation explains, and their relationship to the cooperative begins and ends without either identity depending on the other.

The same year the cooperative acquires the Cooperative Grain Store, 451.2QN94Q9K28E4V31M (Grain Store), from a private operator. The facility keeps its identity through the sale: what changes is the relationship recording who operates it and the legal ownership recorded by whoever is competent to record it. A facility is neither the organization that runs it nor the land beneath it; A farm is not its owner makes the same argument for fields.

Finally, the cooperative hands administration of its operations space to a regional service provider. This is precisely Document 08's Example D, and the specification's answer is unambiguous: the identity persists, the authority records change, and historical records keep the previous namespace context. Document 08 also forbids reading anything more into the arrangement: delegating space administration does not transfer ownership of the resources the space describes (§4.6). The provider runs the space; it does not acquire the cooperative, its fields, or its members' data.

A community is not an organization

Cedar Valley Growers is a different kind of thing. It is a community: a continuing collective of people who recognize one another as growers of the valley, with no articles of incorporation and no single legal form. Its illustrative RID is 451.358VPJMD1B17MKZ4 (Growers). Members join and leave; the community persists while it is recognized as the same continuing community. The cooperative serves the community, and many of its members belong to both, but the community is not the cooperative, and neither is the list of people who belong to it at any moment.

That gap is instructive rather than embarrassing. An RID can be issued for a community because an RID carries no kind at all. A registered name, by contrast, needs a registered kind, and inventing one to make the example tidy would misrepresent the specification. The Seednote on community states the distinction compactly. The more important lesson is about membership. Being a member of the community is a relationship between a person and the community; it confers no ownership of the community's identity, and the community's identity is not a stand-in for its members, whose own identities and privacy remain theirs.

Subsidiaries, divisions, and where one organization ends

In 2033 the cooperative creates a trading company to sell members' grain. Whether that company is a separate referent depends on what it is. A legally distinct entity with its own officers and obligations is very plausibly a referent of its own, related to the cooperative by an ownership or control relationship. An internal division with no separate existence may simply be part of how the cooperative describes itself. Document 08 asks that such granularity decisions follow documented rules rather than arbitrary implementation behaviour, and it does not yet publish those rules for organizations.

The discipline that does apply is to make the decision explicitly and record it. If the trading company receives its own identity, the relationship to its parent is an assertion with a source, dates, and authority, and it can later change — the company may be sold — without either identity changing. If it does not, its activities are described under the cooperative's identity until governance decides otherwise.

When the organization itself changes: merger and succession

Suppose that in 2035 the cooperative merges with two neighbouring cooperatives to form a single new legal entity, the hypothetical Cedar Valley Farmers Union, 451.BVAQ19TY273NCV8Z (Farmers Union). This is where identity questions become real. A rename leaves one continuing organization. A merger into a new legal entity may end the old organization as a continuing referent and begin a new one — or, depending on how it is structured, one cooperative may continue and absorb the others.

If governance decides the union is a new referent, the diagram shows what Document 08 then provides. The union receives its own RID. The cooperative's identity moves from active to superseded, retaining its RID and pointing to its successor with provenance, so that every historical permit, contract, and observation that referred to the cooperative still resolves to the organization it actually concerned. If governance instead decides the cooperative continues and absorbs the others, its RID stays active and the absorbed cooperatives are the ones superseded. What must not happen is either outcome by default. Neither the registry nor any resolver can infer from a press release which organizations continue; someone with authority must decide, on evidence, and the decision must be recorded.

Dissolution and what remains

Organizations also end. If the union is eventually wound up, its identity is not deleted and its RID is not freed. The identity moves to retired, the registry keeps the record, and resolution may return a tombstone where disclosure policy permits — stating that the organization no longer exists and, where relevant, what succeeded it.

That permanence serves people long after the organization is gone. A grower settling an old payment, an auditor reviewing historical water use, or a researcher reading a decade-old study can all resolve the identifier they hold and learn what it referred to, rather than finding it silently reassigned or vanished.

When organizations disagree

Throughout these changes, organizations will say inconsistent things about one another. In 2032 the county water office's space still records the cooperative under its old name as the permit holder for North Field, while the cooperative's own space records the new name and a different contact. A grain buyer's space lists the trading company, not the cooperative, as its counterparty. None of these is necessarily wrong; each is an assertion made by one party, at one time, under its own authority.

Because every assertion keeps its source, a reader can see who said what and when, and an RID shared across the three spaces tells them the statements are about the same cooperative without implying that they agree. Where two records in different systems turn out to describe what might be the same organization, reconciliation follows the same rule as for any referent: evidence and an authorized decision, never similarity of names (§15.3).

Counterexamples

Three shortcuts recur in organizational data and each one corrupts identity. Using the cooperative's RID as a stand-in for its members treats a relationship as an identity and exposes people through an organization's records. Using it as a stand-in for its farms or offices erases the distinction between operator and place, so that a change of operator appears to be a change of place. And conflating membership with ownership — treating a member as part-owner of the organization's identity, or the organization as owner of its members' — confuses three different governance relationships that Document 08 requires to be represented separately.

A fourth shortcut runs in the opposite direction: assuming that every structural change requires a new identity. Renaming, re-boarding, relocating, changing administrators, and acquiring or selling facilities are, under Document 08, ordinary changes that a persistent identity must survive (§9.4). Issuing a fresh RID for each would break every reference to the organization just as surely as encoding its name would.

Conclusion: decide the hard cases, and let the easy ones be easy

Following the cooperative shows a clear division of labour. The ordinary life of an organization — names, boards, buildings, systems, administrators — flows through governance metadata and registered names while the RID stays constant, exactly as Document 08's design principle that identity must survive ordinary organizational change requires (§1.4). The rare events where an organization ends or a new one begins are explicit, authorized, recorded decisions, after which the lifecycle states superseded and retired preserve every historical reference. Communities sit beside organizations as referents of their own, distinct from their members and from the organizations that serve them, even while the naming registry has no kind for them.

For practitioners, that means storing roles as dated relationships, never as fields of the identity; registering successor names rather than minting new identities on a rename; writing down the continuity rules your governance applies before you need them; and keeping attribution on every organizational statement. The identity lifecycle Seednote and its Viewgraph give the states and transitions in detail, and Why identity is not ownership returns to the separation of roles with which this Journal began.