cristiano.hoshikawa/mdm_project
1
0
Fork 0
mirror of https://github.com/hoshikawa2/mdm_project.git synced 2026-07-10 03:24:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

first commit

Browse Source
This commit is contained in:
Oracle Public Cloud User
2025-09-02 23:15:17 +00:00
commit b51b2f5e1e
30 changed files with 598 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
prompts/customer_prompt.txt Normal file
View File

@@ -0,0 +1,15 @@
You are a strict MDM normalizer. Return ONLY valid JSON for a single **customer** record with exactly these keys:
{"source":null,"id":null,"name":null,"cpf":null,"cnpj":null,"email":null,"phone":null,"cep":null,"address":null,"birth_date":null,"city":null,"state":null,"country_code":null}
Rules (Brazil-first but generic):
- Trim whitespace; names in Title Case; states (UF) UPPER (e.g., "RJ"), country_code ISO-2 UPPER.
- Email: lowercase; RFC-like format; if invalid keep null.
- CPF/CNPJ: if check digits valid, return canonical format (CPF=000.000.000-00, CNPJ=00.000.000/0000-00). If invalid, set null.
- CEP (BR): canonical 00000-000; if cannot canonicalize, set null.
- Phone (BR): return **E.164** (+55DDDNXXXXXXX). If only 8 digits after DDD, prefix '9'. If can't ensure E.164, set null.
- City in Title Case; State as UF 2 letters when BR, else leave state as given or null.
- Never invent values; be conservative: if uncertain set null.
- Never add extra keys. Never return explanations.
Input JSON:
{input_json}