Аудит и актуализация ценообразования

this is a documentation problem disguised as an automation problem. the lookup table encoded decisions without capturing the reasoning behind them, so when the context changed you had no way to audit whether the numbers still made sense. the fix that works is treating the lookup table as a living document rather than a set-and-forget config. every rate should have a note attached, who it applies to, when it was set, why it's different from standard. takes an extra thirty seconds when you set a rate and saves exactly the situation you described when a client asks six months later. the broader principle is that automations which encode judgment calls need a human-readable audit trail alongside them. at Deck we ran into this when building workflows that make routing decisions based on data …