# Facebook Growth Pilot - Launch Control Day 1-3

Updated: 2026-07-10 19:55 Asia/Bangkok
Status: rescue/manual UI launch only after public-visibility incident

Scope:

- 9 approved static image posts for Day 1-3
- Pages: `SME มี AI`, `ข่าวเช้านักเทรด`, `ความจริงหลังฉาก`
- Caption pack: `../week1-caption-pack/DAY1_DAY3_CAPTION_PACK.md`
- Posting queue: `../week1-caption-pack/posting_queue_day1_day3.csv`
- Launch tracker: `launch_tracker_day1_day3.csv`

Incident note:

- 2026-07-10: previous Graph/API-created objects were visible to Graph but not visible on Facebook public/UI checks.
- Those rows are not counted as live posts.
- `posted` is no longer an acceptable completion status by itself.
- A post is complete only when it is visible in Facebook UI and the tracker status is `manual_posted_public_verified`.

Important:

- Do not use Graph/API publishing for rescue launch.
- Do not publish automatically until the public UI verification path is proven again.
- First 7 days still require Human Gate before posting.
- If posting manually, verify the final post URL in Facebook UI, then run `scripts/facebook_growth_rescue_pack.py mark-verified ...`.
- For `ข่าวเช้านักเทรด`, keep the investment education disclaimer in every caption.

## Recommended Next Step

Use the rescue launch pack for the active pages first:

- Dashboard: `https://facebook-growth.srv1125477.hstgr.cloud/rescue-launch`
- Markdown pack: `https://facebook-growth.srv1125477.hstgr.cloud/rescue-launch-pack`
- Local pack: `production/week1-rescue-launch/RESCUE_LAUNCH_PACK.md`

Start with exactly 2 public posts:

1. `SME มี AI` Day 1
2. `ความจริงหลังฉาก` Day 1

After both are visible on Facebook UI, continue Day 2-3 or schedule the next cadence.

Reason:

- The images and captions are already approved.
- Manual UI posting avoids repeating the Graph/API visibility failure.
- Public UI verification restores trust before automation is reopened.
- Post URLs can be recorded for 24h/72h metrics tracking only after they are visibly live.

## Manual Publishing Checklist

For each row:

1. Open the correct Facebook Page.
2. Upload the matching image from `production/week1-generated-native/images/`.
3. Paste the caption from `DAY1_DAY3_CAPTION_PACK.md`.
4. Publish or schedule at the BKK slot.
5. Add the first comment after the post is live.
6. Copy the live post URL.
7. Open the URL in a browser and confirm the post content is visible.
8. Run the mark-verified command from the rescue pack.
9. Capture 24h and 72h metrics when due.

## Day 1 Launch Order

| Time BKK | Page | Asset | Action |
|---|---|---|---|
| 07:15 | ข่าวเช้านักเทรด | `day1-kao-chao-nak-trader-market-risk.png` | Manual post or schedule |
| 19:30 | SME มี AI | `day1-sme-mee-ai-ai-tools.png` | Manual post or schedule |
| 20:30 | ความจริงหลังฉาก | `day1-kwam-jing-lang-chak-decoy-effect.png` | Manual post or schedule |

## Day 2 Launch Order

| Time BKK | Page | Asset | Action |
|---|---|---|---|
| 07:15 | ข่าวเช้านักเทรด | `day2-kao-chao-nak-trader-leverage-checklist.png` | Manual post or schedule |
| 19:30 | SME มี AI | `day2-sme-mee-ai-content-calendar.png` | Manual post or schedule |
| 20:30 | ความจริงหลังฉาก | `day2-kwam-jing-lang-chak-price-ending-9.png` | Manual post or schedule |

## Day 3 Launch Order

| Time BKK | Page | Asset | Action |
|---|---|---|---|
| 07:15 | ข่าวเช้านักเทรด | `day3-kao-chao-nak-trader-heatmap-risk.png` | Manual post or schedule |
| 19:30 | SME มี AI | `day3-sme-mee-ai-review-to-sales.png` | Manual post or schedule |
| 20:30 | ความจริงหลังฉาก | `day3-kwam-jing-lang-chak-subscription-leak.png` | Manual post or schedule |

## Metrics Capture

Capture these at 24h and 72h after each post:

- Reach
- Impressions
- Reactions
- Comments
- Shares
- Saves if visible
- Link clicks or profile visits if visible
- New followers from page insights if available

## Go / No-Go

Go:

- พี่โดฟ explicitly confirms manual publish or scheduling.
- Page destination is verified before each upload.
- Caption and image are matched row-by-row.

No-Go:

- Page selector is unclear.
- Caption/image mismatch.
- Trader disclaimer missing.
- Token/API/semi-auto posting is attempted before public UI verification is proven.
- Tracker status is changed to `posted` without public UI evidence.