# Fuega RoseCard NFC Programming SOP — 2026-04-26

**For:** Brady. Programming 50 physical NFC RoseCards (FU-0001 to FU-0050) for the Fuega series.

**Source:** S83-H81-A. URL list at `~/docs/ecosystem/data/fuega_card_urls_2026-04-26.csv`.

---

## Scope

50 NFC cards in inventory, 3 colors (Burgundy / Gold / Navy). Each card needs:
1. **NFC tag programmed** with a destination URL
2. **Airtable Status** updated to `Programmed` (then `Distributed` once handed out)

Brady's chosen URL strategy: **direct URL, no tracking**. Cards point users straight to the per-card landing page. Trade-off documented below.

---

## URL strategy — TWO options

### Option A — Direct URL (Brady's pick) ✅

```
https://rosecourt.co/r/FU-XXXX/?ref=tap
```

**Pros:**
- 39 chars (well under NFC 250-char limit)
- One redirect-free hop → fastest user experience
- No n8n dependency for the tap to work
- Works even if n8n is down

**Cons:**
- ❌ No automatic tap counting in Airtable
- ❌ No Discord alert on first tap
- ❌ Distribution status flips manually (`In Stock` → `Distributed` → `Tapped`)

### Option B — Webhook URL (alternative)

```
https://roseinthegrove.app.n8n.cloud/webhook/fuega-card-tap?card=FU-XXXX
```

**Pros:**
- ✅ Tap Count increments automatically on every tap
- ✅ Discord #leads alert on first tap per card
- ✅ Last Tap Date + IP captured

**Cons:**
- 86 chars (still fits, just longer)
- One extra hop (302 redirect)
- Requires n8n active workflow

**Brady's choice for this batch:** Option A direct URL. If a future batch wants tracking, switch to Option B in the CSV.

---

## Tools

- **NFC Tools** (mobile app — iOS or Android, free)
- **Phone with NFC reader** (any modern iPhone or Android)
- **Airtable** (browser tab open to Fuega_Marketing_Cards table)
- **CSV** at `~/docs/ecosystem/data/fuega_card_urls_2026-04-26.csv`

---

## Per-card workflow

### 1. Pick the next unprogrammed card

Open CSV. Find the next row where `Status = "In Stock"`. Note the Card ID + Direct URL.

Example: `FU-0001` → `https://rosecourt.co/r/FU-0001/?ref=tap`

### 2. Open NFC Tools → Write tab

Tap **"Add a record"** → **URL/URI** → paste the Direct URL.

### 3. Hold the physical card to your phone's NFC reader

NFC Tools writes the URL. Should take 1-2 seconds. You'll get a "Write complete" confirmation.

### 4. Verify with a second tap

Close NFC Tools. Open your phone's camera or NFC reader. Tap the card again — your phone should prompt to open the URL. Tap "Open" and confirm the per-card landing page renders.

### 5. Update Airtable

Open `Fuega_Marketing_Cards` → find the row for this Card ID → flip `Status` from `In Stock` → `Programmed`.

(Don't worry about `Tap Count` or `Last Tap Date` — those columns stay at 0/null with the direct URL strategy.)

### 6. Repeat for the next card

50 cards × ~1 minute each = ~50 minutes total to program the entire batch.

---

## Distribution lifecycle

```
In Stock      → card sitting in inventory, no URL written
Programmed    → URL written, ready to hand out
Distributed   → handed out to a person/event
Tapped        → (auto-set if using webhook URL; manual if direct URL)
Lost          → card missing or broken; deactivate
```

For direct URL strategy: `Programmed` → `Distributed` is the meaningful state change. `Tapped` is informational only.

---

## Recovery scenarios

### Card lost or scratched
1. Set Airtable `Status='Lost'` for the affected Card ID
2. Take a fresh blank card from inventory
3. Program it with the LOST card's URL (preserves the FU-XXXX number)
4. Optionally: program with a NEW Card ID (FU-0051+) — requires adding row to Airtable first

### Wrong URL programmed
NFC Tools can rewrite tags. Just write the correct URL on top — it overwrites the tag's data.

### Card not detected by reader
Try a slightly different angle. NFC reader needs to align with the chip (usually upper-left or center of the card). If still not detecting after 5 tries, tag may be damaged → mark `Lost`.

---

## Switching strategies later

If Brady decides he wants tap analytics after all:

1. Open the CSV
2. For each card you want to switch: re-program with the **Webhook URL** column instead of Direct URL
3. n8n workflow `YuyrHVBrjScJANCh` automatically logs taps + 302s to the per-card page

You can mix strategies — some cards direct, others webhook. The user experience is identical (lands on the same page either way).

---

## Once distributed

Card hand-off triggers:
1. Update Airtable `Status='Distributed'` + fill `Distributed To` (recipient name) + `Distributed Date`
2. Optional: write `Notes` about the context (event, conversation, vibe)

Per Brady's preference, this is a manual flow for now. Future automation could:
- QR-scan the card on hand-off → triggers Airtable update via tap handler
- Brady audio note → transcribed → notes field
- Recipient email capture → automatic linkage to Master Contacts

For now: open Airtable, type the name, save.

---

## Reference

- **Per-card URL CSV:** `~/docs/ecosystem/data/fuega_card_urls_2026-04-26.csv`
- **Per-card landing pages live at:** `https://rosecourt.co/r/FU-XXXX/`
- **Tap handler workflow (alternative path):** `YuyrHVBrjScJANCh` (RC: Fuega Card Tap Handler)
- **Airtable table:** Fuega_Marketing_Cards (`tblPol965DcBJhv0W`) in RoseCourt base
- **Related SOP:** RoseCard member NFC programming at `~/docs/ecosystem/sops/rosecard_nfc_programming_2026-04-26.md` (S83-H71)

---

## Estimated time

- One card: ~1 minute
- Full batch (50 cards): ~50 minutes
- Best done in one session with NFC Tools + Airtable open side-by-side

Good luck. The cards are physical artifacts of the work — make them feel intentional.