SRS: UC_9.15 — Flow 33: Amplify Bounty Verification

1. UC Index

UC_9.15 — Flow 33: Amplify Bounty Verification

2. Trigger

Trader runs Discord slash command /submit-bounty [url] in #bounty-submissions. After bot-side checks pass (§5 Steps 1–2), the bot fires a webhook to Zapier Flow 33.

(Source: RFQ_ Stack Trading Prop Tech V7.pdf §2.3; Zapier Integration V7.pdf §Flow 33)

3. Pre-conditions

4. Post-conditions

5. Basic Flow

Step 1 — URL format validation (Discord Bot, client-side)

Bot checks the input is a valid TikTok or YouTube Shorts URL before accepting. Invalid → Alt-1.

(Source: RFQ_ Stack Trading Prop Tech V7.pdf §2.3 — Validation)

Step 2 — Rate limit (Discord Bot)

One submission per 24 hours per discord_user_id. Exceeded → Alt-2.

Implementation (BA assumption): Redis SET bounty_rate:{discord_user_id} 1 NX EX 86400; key exists → reject.

(Source: RFQ_ Stack Trading Prop Tech V7.pdf §2.3 — Rate Limiting)

Step 3 — Webhook to Zapier

Payload: discord_user_id, url, platform (tiktok | youtube_shorts), timestamp.

Step 4 — Audit Step 1: URL uniqueness

Zapier calls GET /bounty/check-url?url=[URL-encoded]. Middleware queries bounty_submissions.

• is_unique = false → stop; DM: "This link has already been used to claim a reward." (Alt-3)

(Source: Zapier Integration V7.pdf §Flow 33 Step 1; RFQ V7 §API Check Bounty URL)

Step 5 — Audit Step 2: fetch metrics

Zapier fetches Views, Likes, Comments from the TikTok / YouTube API. On API error, retry 3 times with exponential backoff (within 10 seconds). All retries fail → Exc-1.

(Source: QnA_BACKGROUND_MECHANISMS_CRON.md [BG-015] — client sheet 2026-11-04)

Step 6 — Audit Step 3: quantitative filter (Zapier Filter)

Both must pass. Otherwise → Alt-4 (Math Failure).

(Source: Zapier Integration V7.pdf §Flow 33 Step 3)

Step 7 — Audit Step 4: Gemini 1.5 Pro forensic audit

1. PII redaction — strip emails, phone numbers, account identifiers, payment details, full names from all text before sending to the LLM.
2. Input — video description + top 10 comments.
3. Prompt (intensive reasoning task, not a basic spam classifier): "Analyze these comments for bot-farm patterns (repetitive emojis, generic praise, identical phrasing). Return 'AUDIT_PASS' or 'AUDIT_FAIL'."
4. Storage — store only the derived AUDIT_PASS / AUDIT_FAIL in Google Sheets (no raw comments).
5. AUDIT_FAIL → Alt-5.

(Source: Zapier Integration V7.pdf §Flow 33 Step 4 — LLM Analysis (Privacy-Safe))

Step 8 — Audit Step 5: reward (on PASS)

1. Call POST /generate-promo-code (type = Associate Track 100%, origin_user_id = submitting trader).
2. Record URL as rewarded in bounty_submissions.
3. DM trader: "Success. Your impact is verified. Your free Associate Track code is [promo_code]. It has also been sent to your email."
4. Query Users by discord_user_id. If a linked user with an email exists → send the code to that email via AWS SES. If no linked account → skip the email; the Discord DM is the only delivery.

(Source: Zapier Integration V7.pdf §Flow 33 Step 5; QnA_BACKGROUND_MECHANISMS_CRON.md [BG-013], [BG-014] — client sheet 2026-11-04)

6. Alternative Flows

(Source: Zapier Integration V7.pdf §Flow 33 Steps 1, 5 — Communication Matrix)

7. Exceptional Flows

Exc-1 — Social API unavailable after 3 retries / URL invalid, private or deleted: no reward; the attempt counts toward the 24h rate limit for that discord_user_id; DM the user that verification failed and they may resubmit in 24 hours (copy — see Q5); log to BPS_Audit_Log. (Source: QnA [BG-015] — client sheet 2026-11-04)

Exc-2 — Gemini timeout / malformed output (not exactly AUDIT_PASS / AUDIT_FAIL): treat as not passed (fail-closed); no reward; log for manual review. (BA assumption)

Exc-3 — POST /generate-promo-code failure after PASS: do not mark URL rewarded; Ops alert to #ops-marketing; trader DM pending manual issue. (BA assumption)

Exc-4 — Discord DM blocked by user privacy settings: linked user → email still sent on PASS; log DM failure. Unlinked user → no email either, so the code is not delivered; log for Ops follow-up.

8. Business Rules

BR_9.15.1: Structured Input Only

#bounty-submissions accepts only the /submit-bounty slash command (Send Messages off for @everyone, Use Application Commands on).

(Source: RFQ_ Stack Trading Prop Tech V7.pdf §2.3)

BR_9.15.2: Supported Platforms

Only TikTok and YouTube Shorts URLs are accepted; validated by the bot before submission.

(Source: RFQ_ Stack Trading Prop Tech V7.pdf §2.3)

BR_9.15.3: One Submission per 24 Hours per discord_user_id

The 24h rate limit and the anti-bot strike count are tracked by discord_user_id (linked or not). Failed verifications (API error after retries, invalid/private URL) also count.

(Source: RFQ_ Stack Trading Prop Tech V7.pdf §2.3; QnA_BACKGROUND_MECHANISMS_CRON.md [BG-013], [BG-015] — client sheet 2026-11-04)

BR_9.15.4: One Reward per URL

GET /bounty/check-url returns is_unique = false for any URL already rewarded. Only rewarded URLs block resubmission.

(Source: RFQ_ Stack Trading Prop Tech V7.pdf §API Check Bounty URL)

BR_9.15.5: Quantitative Thresholds

Views ≥ 50,000 AND (Likes + Comments) / Views ≥ 0.015. Both inclusive.

(Source: Zapier Integration V7.pdf §Flow 33 Step 3)

BR_9.15.6: LLM Privacy

PII is redacted before any text reaches the LLM; only the derived PASS/FAIL is stored (Google Sheets); enterprise LLM config with defined retention.

(Source: Zapier Integration V7.pdf §Flow 33 Step 4)

BR_9.15.7: Reward Definition

Single-use, 100% off Associate Track, transferable, origin_user_id logged for audit. (usage_limit = 1 per QnA STAGE1-074.)

(Source: RFQ_ Stack Trading Prop Tech V7.pdf §API Generate Promo Code · QnA_STAGE1_CHECKOUT_ONBOARDING.md STAGE1-074)

BR_9.15.8: Message Copy Is Fixed

Discord DM copy for Alt-3/4/5 and PASS follows the V7 Communication Matrix verbatim (English).

(Source: Zapier Integration V7.pdf §Flow 33 Step 5)

9. Acceptance Criteria

10. API Reference

GET /bounty/check-url

Response: { "is_unique": true }

POST /generate-promo-code

Request (per V7: type, origin_user_id):

{
  "type": "ASSOCIATE_TRACK_100",
  "origin_user_id": "94a2b1c8-3f4e-4b21-a123-890abcdef123"
}

Response: { "promo_code": "STRING" }

type enum values are not defined in V7 — ASSOCIATE_TRACK_100 is a BA placeholder (see Q3).

(Source: RFQ_ Stack Trading Prop Tech V7.pdf §API)

11. Open Questions

12. Changelog