# Burn Account Test Protocol — FlyNumber Prefix Validation
> Drafted: 2026-04-26
> Objective: Verify carrier-type tolerance before committing FlyNumber prefixes to production personas

## Overview

A one-time, throwaway test to determine whether FlyNumber SIP DID numbers pass carrier-lookup verification on Meta (the strictest platform). If Meta accepts them, X, Reddit, and Telegram will follow. If Meta rejects them, we reconfigure to use Daisy/prepaid SIM for initial Meta verification and FlyNumber as the public-facing line.

**Test order:** Maya (1-609) first — US domestic is the baseline. If her number fails, assume FlyNumber geographic SIP DIDs are categorically flagged by Meta, and flip the entire phone strategy to Daisy + FlyNumber hybrid.

---

## Phase 0: Burn Infrastructure (Complete before ordering)

These are disposable and must never touch production persona infrastructure.

| Component | Burn Setup | Why |
|-----------|-----------|-----|
| **Device environment** | Fresh VirtualBox VM with Windows or Ubuntu; or clean Chrome Guest profile with spoofed local storage | Prevents fingerprint correlation |
| **Proxy** | Dedicated mobile proxy (Oxylabs/The Social Proxy) — assign a single US-based IP for the burn session | Same proxy tier as production |
| **Email** | Fresh Gmail with random name generator (e.g., `sarah.chen.burn@gmail.com`) | Gmail is the most Meta-trusted free email |
| **Identity** | Generic Anglo name (Sarah Chen) from a random city far from all 4 personas (e.g., Portland, Oregon) | Zero overlap with Lebanese persona network |
| **DO NOT use** | Any persona domain, any existing proxy slot, any VM already used for Rami/Lara/Karim/Maya | Strict isolation |

---

## Phase 1: Order the Burn Number

1. Go to flynumber.com → order **1-609 (New Jersey)**
2. Choose **SMS forwarding** → forward to the burn Gmail above
3. Do NOT enable voice forwarding unless you want to test that too
4. Record: Order ID, forwarding target, monthly cost
5. Wait for provisioning email (usually instant, sometimes 15–30 min)

---

## Phase 2: Pre-Account Checks

Before touching any platform, verify the line is alive.

| Check | Method | Pass Criteria |
|-------|--------|---------------|
| **Inbound SMS** | Send SMS from your personal phone to +1-609-xxx-xxxx | Received in Gmail forwarding within 60 seconds |
| **Voice inbound** (optional) | Call the +1-609 number from personal phone | Rings, goes to voicemail, or your configured endpoint answers |
| **Reverse carrier lookup** | Use phonevalidator.com or numverify.com API | Note the carrier/line type — expect "landline", "voip", or "residential" |

**Log the carrier lookup result.** This is your evidence for whether Meta will reject it.

---

## Phase 3: Meta Burn Account Creation

This is the strictest real-world test. Do it in the burn VM with the burn proxy.

### Step-by-Step

**Step 1 — Clear session**
- Reboot VM or kill Chrome Guest and restart
- Verify proxy exit IP is stable and US-based

**Step 2 — Navigate to facebook.com**
- No login session, no cookies from prior tests

**Step 3 — Create Account**
- Name: Sarah Chen (burn identity)
- DOB: 1988-06-15 (or random 25–40)
- Gender: Female
- Email: `sarah.chen.burn@gmail.com`
- Password: Strong random (Bitwarden-generated)

**Step 4 — Phone verification prompt**
- Facebook will ask for a phone number within 24–72 hours, or immediately if triggered
- Enter: **+1-609-xxx-xxxx** (the FlyNumber)

**Step 5 — Wait for OTP**
- If OTP arrives in Gmail forwarding → **record delivery time**
- If no OTP within 5 minutes → check SMS junk folders, then mark as **FAIL-OTP**

**Step 6 — Enter OTP**
- If accepted → account goes into basic setup flow → **PASS**
- If rejected with "invalid number" or "this number can't be used" → **FAIL-CARRIER-TYPE**
- If account flagged for review within 30 minutes → **FAIL-RISK-SCORE**

**Step 7 — 24-hour hold**
- Complete profile minimally (no photo needed — just accept defaults)
- Do not post, do not friend anyone
- Check account status at 1h, 6h, 24h
- If still alive with no "Confirm Your Identity" prompt → **PASSED**

---

## Phase 4: Test Escalation (Optional but Recommended)

If Phase 3 passes, escalate to the next platform to define the tolerance boundary.

| Test | Platform | Method if Meta passed |
|------|----------|----------------------|
| Escalation A | **Instagram** | Create IG from the same Meta account, link via "Log in with Facebook" rather than phone. IG inherits Meta trust score. Check if IG forces phone re-verification. |
| Escalation B | **TikTok (strictest)** | New TikTok account using same phone number **directly** (not via Meta linkage). TikTok is carrier-lookup paranoid. This is the real stress test. |
| Escalation C | **X** | Create X account using the same FlyNumber + burn email. X is permissive but worth checking for SMS delivery consistency. |

**Do not escalate past a failure.** If Meta burns, stop. If Meta passes but TikTok burns, you have a Meta-only strategy and a TikTok-fallback strategy.

---

## Result Interpretation Matrix

| Outcome | Meta | Instagram | TikTok | Interpretation | Production Strategy |
|---------|------|-----------|--------|----------------|---------------------|
| **A** | ✅ | ✅ | ✅ | FlyNumber SIP DIDs accepted as valid mobile-equivalent | Use all 4 FlyNumbers for **all 7 platforms** |
| **B** | ✅ | ✅ | ❌ | Meta accepts, TikTok rejects carrier-lookup | FlyNumber for **Meta+X+Reddit+Telegram+YT**; Daisy/prepaid for **TikTok** |
| **C** | ✅ | ❌ | — | Meta accepts, IG forces re-verification and rejects | Hybrid: FlyNumber for **Meta** (FB); Daisy for **Instagram** |
| **D** | ❌ | — | — | Meta rejects carrier-type at Step 5 | Switch to **Daisy/prepaid for all Meta-family platforms**, keep FlyNumber as public line |
| **E** | ✅, then 48h lock | — | — | Meta initializes but later reviews and kills | Risk-score mismatch — likely proxy fingerprint, not the number itself. Re-run with clean proxy. |

**Most likely outcome for 1-609:** D or B.

---

## Phase 5: Dispose or Preserve

| Scenario | Disposition |
|----------|-------------|
| Outcome A (all pass) | Keep Sarah Chen as a **long canary account** — log in once per week to maintain it. This becomes a canary for when FlyNumber carrier reputation shifts. |
| Outcome B-D (any failure) | Kill the burn account immediately (delete via Meta settings or abandon). Do not let a flagged identity sit in the same proxy pool as production personas. Cancel the FlyNumber or reassign to a non-Meta use case. |
| Outcome E (review/kill) | Kill it after analysis period ends. Do not persist flagged accounts. |

---

## Costs

| Item | Cost | Notes |
|------|------|-------|
| FlyNumber 1-609 | $3–6 for first month | Cancel if outcome D |
| Mobile proxy session | ~$3–5 (fractional day) | Same tier as production |
| Burn VM | $0 (VirtualBox) | Existing tool |
| Gmail | $0 | |
| Total per test | **$6–11** | One-time per prefix |

**To test all 4 prefixes (if 1-609 passes and you want per-prefix data):**
Repeat Phases 1–5 for 33-3, 46-31, and 56-41 using fresh burn identities each time. Each test is **$6–11**. Testing all 4 = **$24–44**. This is cheaper than finding out a prefix fails after you've already seeded 90 days of persona content.

---

## Quick-Reference Checklist

- [ ] Burn VM isolated and clean
- [ ] Burn proxy mobile IP assigned (US exit)
- [ ] Burn Gmail created and confirmed
- [ ] FlyNumber 1-609 ordered and SMS forwarding configured
- [ ] Inbound SMS test passed (Phase 2)
- [ ] Meta account created with burn identity
- [ ] Phone verification attempted with FlyNumber
- [ ] OTP received and entered OR failure mode recorded
- [ ] 24-hour observation complete
- [ ] Result categorized (A–E)
- [ ] Decision logged in `PERSONA-PHONE-MAPPING.md`
- [ ] Burn account disposed or promoted to canary

---

## Appendix: If Outcome D (Meta rejects)

**Immediate pivot:**

1. Order Daisy for **Maya** (US number) — light KYC, real mobile carrier
2. Order Daisy for **Rami** (EU number) — light KYC
3. Keep FlyNumber 33-3 for Rami as the **published contact line** on his bio/domain, but verify Meta/IG/TikTok with Daisy
4. Repeat for remaining personas
5. Update `CAMPAIGN-PROFILES.md` and `PERSONA-PHONE-MAPPING.md` with hybrid strategy

**Hybrid stack:**
- **Primary verification (Meta/TikTok/IG):** Daisy real mobile
- **Inbound SMS / public line:** FlyNumber forwarded to email
- **Monthly cost per persona:** ~$25–35 (Daisy) + ~$5 (FlyNumber) = **$30–40/mo**
- **Risk reduction:** 95%+ pass rate on Meta/TikTok while maintaining a cheap published number

---

*This protocol is designed to be run once before any production persona account creation begins.*