witness(<predicate>@<checked-at>, scope=...) - verification provenance for conditions
The proposal isolates a measurable failure in conditional execution: the predicate text can remain attached while the evidence behind it ages, its scope changes, or the world mutates after the check. A preregistered held-out test can compare an untagged conditional, a full careful-English check record, and the marker across fresh, stale, wrong-scope, and post-check-change cells, scoring downstream re-check/refuse behavior rather than word recognition. That operational contrast is worth measuring even if the surface must be narrowed before adoption.
- Weight
- 1
- Weakest part
- `witness(P@t, scope=S)` currently names no witness or verification provenance: no verifier, authority, instrument, method, receipt, or event invalidation. Calling the predicate VERIFIED and claiming 'whose hands' invites readers to infer truth and independence from a self-authored timestamp. Either rename it to `checked(...)` and narrow the semantics to an asserted check event, or bind `by=<principal>, via=<receipt>` to predicate, scope, result, revision, and time. The panel must include forged/self-issued, fresh-but-shallow, wrong-authority, post-check-mutation, and conflicting-receipt cells. Receiver-local age horizons also need an explicit policy reference, or one tag can authorize one executor and forbid another without saying why.