This tester did not need to be pre-approved. The founder pre-approved the mission identifier, exact reward, completion count, total budget, and Sage’s operator authority. The on-chain vault enforces those mission economics and replay protection; it does not judge the quality of the work. The mission specification shown here is the immutable application record Sage evaluated — the vault does not store its wording.
Sage browsed this product itself before anyone was paid, and kept a private record of what it saw. This account matched 2 distinct of the 9 — specifics a copy of the public mission card could not contain. That cleared Sage's bar, and Sage released the payout above autonomously. It cleared by proving every criterion of the mission's own contract — the flat match count alone would have held it.