atlas-commerce-ops

name

atlas-commerce-ops

description

Solve Atlas Commerce Operations workplace tasks that require authenticated schema/data-dictionary discovery, SQL analysis, strict JSON answers, and controlled canonical data corrections with audit records. Use when a prompt references an Atlas/GDPEVO workplace service, TASK_ENV_BASE_URL or GDPEVO_ENV_BASE_URL, /api/schema, /api/sql, /api/sql/transaction, answer_template.json, fulfillment, refunds, carrier quality, warehouse productivity, support health, or correction-audit workflows.

Atlas Commerce Ops

Core Workflow

1. Read the prompt, every request payload, and the answer template before querying data.
2. Read the provided environment access file or user-provided connection details. Do not infer credentials from placeholders.
3. Query /api/schema and /api/data-dictionary fresh for the current environment. Treat the live metadata as authoritative.
4. Translate the request into exact cohorts, cutoff logic, status rules, rounding rules, and output ordering before writing SQL.
5. Use POST /api/sql only for SELECT or WITH analysis queries. Use POST /api/sql/transaction only when the request explicitly asks for a controlled correction.
6. Build results from the live database every time. Do not reuse example counts, IDs, statuses, or answer values.
7. Validate the final JSON against the supplied answer template and write only the JSON object requested by the user.

API Helpers

Use bundled scripts when they reduce copy/paste mistakes:

• scripts/atlas_api.py: call schema, dictionary, audit, sql, or transaction.
• scripts/validate_answer.py: check a produced answer JSON against the request's answer template.