Can I vibe code Wunderkind?

Build a lightweight First-Party Identity and Behavioral Trigger Engine using Next.js (App Router), PostgreSQL (with Prisma ORM), and Redis for event queuing.

1. DATA MODEL & SCHEMA
Define the following models in Prisma:
- Merchant: id, name, apiKey, webhookUrl, created_at.
- VisitorProfile: id, merchantId, hashedEmail (indexed, nullable), persistentCookieId (unique), firstSeenAt, lastSeenAt.
- IdentityAlias: id, visitorProfileId, aliasType (e.g., 'IP_USER_AGENT', 'LOCAL_STORAGE_HEM'), aliasValue, matchedAt.
- Event: id, visitorProfileId, eventType ('PAGE_VIEW', 'PRODUCT_VIEW', 'ADD_TO_CART', 'EXIT_INTENT', 'FORM_SUBMIT'), payload (JSONB), timestamp.
- TriggerRule: id, merchantId, name, eventType, threshold (JSONB, e.g., { minScrollDepth: 70, timeOnPageSec: 30 }), actionType ('SHOW_POPUP', 'SEND_KLAVIYO_EVENT'), actionPayload (JSONB), isEnabled.

2. CLIENT-SIDE SDK (JS SCRIPT)
Create a lightweight vanilla JS script snippet that:
- Generates or reads a 365-day persistent first-party cookie (`_fpid`).
- Tracks scroll depth, mouse exit movement towards browser top bar (exit intent), idle time, and product page URL parameters.
- Sends beacon requests (`navigator.sendBeacon`) to `/api/v1/events` containing payload: { cookieId, eventType, pageUrl, timestamp, hashedEmail (if captured via input blur) }.
- Listens for JSON responses from `/api/v1/events` to dynamically render custom exit-intent or capture popups without blocking main thread execution.

3. IDENTITY RESOLUTION ENGINE
Build an API endpoint `/api/v1/identify` that:
- Receives payload: { cookieId, email, ip, userAgent }.
- Hashes incoming email using SHA-256.
- Checks if `VisitorProfile` exists for `hashedEmail` or `cookieId`. If found, merges aliases into a single unified profile.
- Persists the mapping to PostgreSQL and caches active sessions in Redis for low-latency lookups (<20ms).

4. TRIGGER EXECUTION & INTEGRATION ENGINE
- Evaluate event streams in real time using Redis streams or queue workers.
- When an event matches an active `TriggerRule` (e.g., `EXIT_INTENT` + `ADD_TO_CART` present in recent events), verify if the user has already received a trigger within a 24-hour frequency cap.
- If verified, dispatch event to downstream ESP (stub Klaviyo API event push to `/track` with event name 'Behavioral Trigger Fired') or return popup creative payload to client SDK.

5. OUT OF SCOPE
- Do not build a third-party cross-site data sharing graph.
- Do not build email template drag-and-drop builders (use raw JSON payload execution).
- Do not build complex ML attribution models. Use deterministic last-touch control vs. treatment split testing.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs