# EMEA PQL — reference implementation

EMEA is the **production reference** ([emea_lambda_tasks](https://github.com/pingcap-inc/pingcap-support/tree/main/emea_lambda_tasks)) the other regions fork. It runs today (TiDB `regional_support` +
`emea_lambda_tasks` Lambdas + Slack/HubSpot), scoring an additive Activity+Fit+Urgency model and, in
the v1 upgrade, the three-queue floor design.

## Start here
- [`EMEA-Signal-Model-v0.sql`](EMEA-Signal-Model-v0.sql) — live tier/scoring spec (Activity 40 + Fit 30 + Urgency 30 → P0/P1/P2 gates).
- [`emea-pql-model-upgrade-proposal-20260624/`](emea-pql-model-upgrade-proposal-20260624) — v1 upgrade: three action queues (paid-unconnected, spending-limit-unconnected, recent-imports), P1 floors, engineering handoff, validated SQL.
- [`emea-account-relationship-categorization-proposal-20260724.md`](emea-account-relationship-categorization-proposal-20260724.md) — adopts APAC's account-relationship categories (net-new / open opp / win-back / account-no-opp / partner-verify / active customer) as a business routing layer. Business idea only — no APAC code or scoring ported.
- [`EMEA-Daily-Intelligence-Brief.sql`](EMEA-Daily-Intelligence-Brief.sql) / `.md` — the daily ops bot query + brief.
- [`entity-ai-category-rubric.md`](entity-ai-category-rubric.md) — the fit classification rubric.
- [`emea-emails-operating-pack/`](emea-emails-operating-pack) — outreach templates + ops tracker.
- AWS Activate program docs + `scripts/` — adjacent program tooling.

## Relationship to the rest of the repo
EMEA proved the live signals APAC needs (QPS via Clinic API, domain/AI fit via `domain_intelligence`
+ OpenAI). Spending-limit is a **v1-planned** item on EMEA's own roadmap, not yet built. The shared
model contract these feed is in [`../universal/`](../universal); the APAC adaptation is in
[`../apac/`](../apac).