Top line: validated bounty findings lose value when they sit behind an empty ready queue. KENSAI keeps a hard G5 buffer floor so submission work can move while timing still matters.
Why the buffer matters
Bug bounty operations are not only about finding issues. They are about getting confirmed, in-scope, high-impact reports into the right submission flow before freshness fades or a duplicate lands first. A healthy buffer gives operators enough ready material to submit without waiting on another validation cycle.
The G5 floor is deliberately simple: count proof-gated, passed, unsubmitted findings. If that count drops below the minimum, the validation loop needs to run immediately. No reinterpretation, no retired schema shortcuts, and no optimistic dashboard math.
What KENSAI watches
- Primary floor: G5 pass plus unsubmitted findings in the bounty findings table.
- Submission state: findings that have not already been sent or marked complete.
- Program holds: suspended programs and signal-slot constraints that keep otherwise valid work parked.
- Recovery action: automatic validation-loop triggers when the floor falls below the target.
Operational takeaway
A ready buffer is a reliability control. It gives the team time to package reports well, keeps review quality high, and prevents urgent submission windows from depending on last-minute validation.
For KENSAI, the rule is blunt because the payout window is blunt: keep the buffer healthy, or trigger recovery immediately.