atlas-ops-reporting

name

atlas-ops-reporting

description

Produce cutoff-based operational reports and controlled data corrections from the Atlas Commerce Operations workplace database, returning JSON that conforms exactly to a supplied answer_template.json. Use whenever a task points at an Atlas / "Commerce Operations" workplace service (a <TASK_ENV_BASE_URL> with /api/schema, /api/data-dictionary, /api/sql, /api/sql/transaction, /api/correction-audit) and a request payload plus an answer_template.json under input/payloads/, and asks for a scorecard, reconciliation, productivity / health review, backlog analysis, SLA breach report, or an approved minimal canonical correction. Covers read-only analytics and the single-row audited-correction flow.

Atlas Commerce Operations reporting & correction

What these tasks look like

Every task in this family gives you three things:

1. A prompt.txt with business framing and pointers to the payloads.
2. A request payload JSON under input/payloads/ (e.g. *_request.json) holding the full scope, definitions, cutoffs/windows, ranking rules, rounding rules, and classification thresholds. This file is the specification. The prose in prompt.txt never overrides it.
3. An answer_template.json — a JSON Schema describing the exact output object.

You query the authenticated Atlas Commerce Operations service, compute the requested figures, and write one JSON object to answer.json that conforms to the template exactly — no commentary, no extra keys.

Most tasks are read-only analytics. A minority are controlled corrections that mutate exactly one field of one row through the transaction endpoint with an audit record. Detect which from the request (a correction_status_rule, approved_correction block, or mention ⇒ correction task; otherwise read-only).