NexusCdsKey Naming system

Status: draft · 1.26.0 · JSON

Identifies the business key carried by resources a decision-support rule writes, so that re-evaluating the rule against the same patient updates the Task it already raised rather than raising a duplicate. Sibling of NamingSystem/nexus-harness-key, which does the same job for the AI harness; the namespaces are deliberately separate because the two are parallel producers minting keys out of registries under separate ownership, key values begin with the producing capability's own name, and a shared namespace would let one producer's re-run find and overwrite the other producer's task. The value is derived from what the task is ABOUT -- the patient and the gap the advice addresses -- and never from the evaluation that produced it: a key containing a hook instance, card uuid, suggestion index or execution timestamp changes on every firing and defeats the purpose. Patient-scoped keys MUST include the subject, since two patients can present the same gap. Values are opaque to consumers and MUST NOT be parsed. Producers search this identifier before writing.

Type	Value	Preferred
uri	../NamingSystem/nexus-cds-key	true