observationlisted

# Observation 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. OBS is an immutable semantic claim with `authority: evidence`; never phrase it as a decision that future work must follow. 1. Capture requires substantive Observation and Evidence content, using only the capability descriptor. 2. `annotate` changes metadata only. Changed claim or evidence meaning requires a successor OBS and `supersede`; prepare both actual claims and keep reciprocal lifecycle edges in one final bundle. 3. `invalidate` requires a substantive disproof reason; `reverify` requires fresh evidence. Age alone does not retire evidence. 4. Keep ID and path, backlink, vault identity, CAS, lock, and atomic-write guards. Preview, prepare, and attestation write nothing. Follow the active-language contract in `../context/references/active-language.md`. Write user-facing responses, questions, previews, and explanatory errors in the active language. Preserve user-authored artifact prose in its original language; identifiers and machine-readable fields remain English. Treat a direct, explicit, unconditional user statement that settle