NexusHarnessKey Naming system

Status: draft · 1.26.0 · JSON

Identifies the business key carried by resources the AI harness writes on its own behalf (suggestion Tasks, pre-generated summary Compositions), so that re-running the producing capability updates the existing resource rather than creating a duplicate. The value is derived from what the resource is ABOUT -- the care gap addressed, the period summarized -- and never from the run that produced it: a key containing a run id, thread id or execution timestamp defeats the purpose, because it changes on every execution. 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 find prior work with a search on this identifier before writing. This namespace is the harness's alone: a decision-support rule keys its tasks under NamingSystem/nexus-cds-key, because the two are parallel producers minting keys out of separately owned registries and a shared key space would let one producer's re-run find and overwrite the other producer's task. Sibling of NamingSystem/nexus-harness-graph, which names the actor rather than the work.

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