💬 Marcy — ask your Claude anything about this system
Open Claude and paste:
Read https://iasf-dev-hq.pages.dev/handbook.md and answer my questions about the IASF EP system.
The handbook is the full written guide behind this page — system outline, everything done, everything remaining, and how-tos. For live data questions ("what stage is X at?"), connect your Airtable account to Claude (Settings → Connectors) and ask against the base directly.
The pipeline (per application year, on Applications — restructured July 26)
Link Sent (date on EP)→For Review→Approved→Privilege Sent→Privilege Returned ✓
Dashed = set automatically on form submission. Each year's application carries its own status, so an EP can be Privilege Returned for 2027 while For Review for 2028 — see the EP's 2027 Stage / 2028 Stage columns. Privilege Returned = confirmed for Worlds. Full walkthrough: flow page.
6
automations live
3 updated drafts await your click
8
build items remaining
next: apply restructure in UI
~20
bid-count conflicts to review
letter ≠ Airtable, not overwritten
13
EPs must confirm dates
wrong-event dates were cleared
🎯 Marcy — your next steps
Send Hanako the privilege letter template + the merge-field list (EP name, event, bids, dates…). This unblocks the privilege-letter automation — the biggest remaining build.
Confirm real 2026/2027 event dates with 13 EPs — their dates were cleared because they were another event's dates (list in handbook §3).
Review the ~20 bid-count conflicts with Hanako — decide letter vs. Airtable for each.
Keep running the normal cycle — the system is live and doesn't wait on the above.
⚠️ Always send returning EPs their prefilled link, never the blank form — the blank form creates duplicate records.
✅ Done
DONEBase architecture live — 5 tables, prefill loop, flags, bid math