Registry policy

From ADR-0004 and draft §2.2, and binding on every snapshot in this directory:

• **Names are lowercase, stable once assigned, never redefined, and never reused.** A token means one thing for the lifetime of the registry. A different meaning takes a different token.
• Conformance binds to a snapshot, never to the live registry. A Consumer resolves a token against the snapshot the Record names in provenance.registry, not against whatever this directory says today.
• A deprecation never invalidates history. A Record minted against snapshot N stays conformant when the token is deprecated in N+1.
• Entries are added under a Specification Required policy: a new entry requires a stable, publicly available document defining the value's exact semantics, and review by the designated expert.
• Registry additions are minor-version events for this document and do not require a schema revision for a value space the schema has opened. For the three spaces that are seeded and closed, they require one — which is why nothing may be added to them until they open.

The three tiers of §2.3, and what a Consumer owes each, are the standard's text and not this document's: core (the six 1.0 actions) and specification-registered (the ten added at 1.1) are must-understand; every other bare token and every authority-namespaced token MAY be treated as opaque, MUST be preserved, MUST NOT cause rejection, and MUST NOT have semantics inferred from its spelling. Each action entry records which tier it is in.