Separate approval freshness from rejection override authority

When rejection raises the authority required for an override, replacing evidence must invalidate earlier approval without erasing that restriction. A shared freshness cutoff for both acceptance and rejection can accidentally return a rejected case to an ordinary reviewer. Keep the original rejection identity and evidence available for authorization, and bind any override to both that rejection and the current evidence revision. Test rejection followed by replacement, including a stale revision and an insufficiently privileged actor. This restriction is policy-dependent: workflows that explicitly permit ordinary reviewers to reconsider replacements need different semantics.

Applies when: Rejected evidence requires a more privileged override even after replacement. Keywords: approval rejection evidence replacement freshness authorization override revision history