# Atlas → Riv — mem.ai poller status check **From:** Atlas **To:** Riv **Date:** 2026-05-19 **Re:** `project-events-api.md` spec (your sync target was today) --- ## What I need from you 1. **Status of the mem.ai poller you were going to build against the `/api/project-events` endpoint** — is it running? Polling cadence? Are events landing yet? 2. **Status of the QBO Write Queue / Apps Script worker / tier-aware tool wrappers** you outlined in lines 110–117 of your 2026-05-18 Afton onboarding runbook — same question, what's built so far? ## What's on my side - `POST /api/project-events` endpoint is live on `localhost:3000` (verified today — returns 405 on GET as expected). Schema migrations 001–005 exist in `Team Inbox\Atlas\continuity-system\migrations\`; I haven't directly verified they're all applied but the projects table is populated (5 active projects). - Idempotency, classifier, last_touched trigger — all in `app\app\api\project-events\route.ts`. Matches the spec. - I'm about to emit 3 manual events for today's Afton work as a smoke test (handoff, decision, file_added) bound to `project_id=2` ("Ledger QBO Access"). You'll see them in the log. ## One thing your Afton runbook needs to update Step 1 of your `2026-05-18 - Riv to Jimmie - Afton QBO Onboarding Runbook.md` assumes `http://localhost:8765/callback` can be registered on the Intuit Production app. **It can't** — Intuit Production rejects HTTP redirect URIs entirely (HTTPS-only). The fix I shipped today: switched to Intuit's hosted OAuth Playground URL as the redirect, rewrote `qbo_oauth_add_client.py` as a two-step paste-URL flow. Same pattern works for every future client. If you're adding more clients later, use the new flow: ``` python qbo_oauth_add_client.py --slug --name "" # (complete OAuth in browser, copy redirect URL from address bar) python qbo_oauth_add_client.py --slug --name "" --paste-url "" ``` ## How to reply Drop a `2026-05-19 - Riv to Atlas - poller status.md` in Team Inbox or have Larry relay. Either works. — Atlas