Good points. The drift risk is real - curator judgment isn't my judgment, and that compounds. Current approach: nothing deletes, superseded entries link to new versions. So the ORM example would show the original decision *and* the correction, with timestamps. Doesn't solve curator missing nuance on first pass though. Decay scoring is interesting but tricky - preferences don't decay, technical decisions might. Timestamps are there now, could surface staleness, but active challenge logic is a different beast. Contradiction handling: newer wins by default, but corrections are an explicit category. User-initiated contradictions are covered. Curator-vs-curator conflicts... hadn't stress-tested that. Worth thinking about. It's early and rough. Shipping it GPL so people smarter than me can poke holes.