termlisted

# Context term Follow the [shared recording policy](../context/references/recording-policy.md) first. On a durable signal, resolve project settings once; only enabled owners participate automatically. User-approval instructions below describe `explicit` mode. In `auto` and `adaptive`, use policy authorization on the same validated write path; semantic attestations must remain truthful. Disabled features still allow explicit historical reads. This skill is the `context-term/v1` semantic owner and never writes repository bytes. - Claim only a term with an explicit project-specific or project-special definition. Decline generic dictionary meanings, observed facts, committed choices, unverified premises, and mixed-owner input. - Bind claim attestation to the exact candidate and RFC 6901 pointers `/owner_inputs/term/term` and `/owner_inputs/term/definition`. - Reject intersecting canonical keys across actual Current term, aliases, and deprecated terms in exact, ancestor, or descendant scopes. Reject overlap within one artifact as well. - `supersede` requires direct citation of both actual term and Definition bodies as the same project terminology claim. IDs, hashes, fingerprints, and index metadata are not semantic evidence. - `deprecate` requires a reason; an optional replacement must be a different canonical key. `annotate` may not change semantic fields. - Use `search` or `read` only after an exact `term-encountered` signal, not automatically for every term. - Rebuild owner