NexusGeneratedSlot Naming system

Status: draft · 1.26.0 · JSON

Marks a Slot as one a Nexus EMR schedule-generation run wrote or is maintaining. Carried as Slot.identifier.system; the value joins the practitioner's identifier to the slot's local start, as {practitioner-id}-{yyyyMMdd-HHmm}.

Ownership marking, not a match key. A run matches a slot to a cell of its grid by the slot's Schedule association and its start instant -- preferring an exact start-and-end match where several slots share a start -- and never by this identifier or by a resource id. The marking carries no behaviour of its own: no reader in Nexus EMR acts on it.

The value is not unique and is not a correlation key. Two slots of different lengths beginning at the same minute produce the same value, and the local start carries no offset, so one value can name two different instants in two time zones. Correlate a slot by its own resource identity, never by this pair.

Presence does not prove the generator created the slot, and absence does not prove it did not. A run stamps every slot it creates. It also ADOPTS slots already standing on its grid: an adopted slot carrying no identifier at all gains this one, and an adopted slot carrying somebody else's keeps what it has. Read the marking as "a generation run is maintaining this cell", which is what it supports, and not as provenance.

It does not scope deletion. A run never deletes. Emptying a practitioner's calendar is a separate explicit action, and it removes every slot on the schedule whether or not it carries this identifier -- so the marking must not be relied on to protect a slot written by anything else.

EMR-local: values are minted per deployment and imply no external governance.

Type	Value	Preferred
uri	../NamingSystem/nexus-generated-slot	true