Crescent Finance Ops
Workflow
Every task in this domain follows the same pattern:
- Read
payloads/environment_access.json— extractbase_url. - Read
payloads/request_memo.json— extract target entity IDs, period ranges, focus list. - Read
payloads/answer_template.json— the exact JSON shape to return. Never add or omit keys. - Query the relevant API endpoints (see Domain Dispatch below).
- Compute metrics using the formulas in the reference files.
- Return exactly one JSON object matching the template.
Use curl -s "<base_url>/endpoint?params" for every API call. Parse JSON with python3 -c or python3 -m json.tool.
Domain Dispatch
Match the task's required endpoints to the domain:
| Domain | Endpoints | Reference |
|---|---|---|
| Finance (branch/regional reporting) | /api/finance/* |
references/finance.md |
| Compensation (summaries, forecasts) | /api/compensation/* |
references/compensation.md |
| Payroll (weekly review) | /api/payroll/* |
references/payroll.md |
Output Conventions (all domains)
- Currency values: 2 decimal places. Use standard round-half-up. In Python:
Decimal(str(value)).quantize(Decimal('0.01'), rounding=ROUND_HALF_UP). - Percent/ratio values: 4 decimal places. Use standard round-half-up. In Python:
Decimal(str(value)).quantize(Decimal('0.0001'), rounding=ROUND_HALF_UP). - Lists of IDs: ascending stable order unless the template says "rank_desc" or similar.
- Enums: use exact string values from the template.
- Keys: include every key in the template; never add extras.
- Period convention: M1–M12 = "FY2024", M13–M24 = "FY2025".
Cross-Domain Rules
- Always cross-check that the computed total equals the sum of its parts.
- For reconciliation fields: compute both the aggregate and the sum-of-parts; the difference should be 0.0.
Verification
Before submitting, verify:
- Every required top-level key from the answer template is present.
- All currency values are rounded to 2 decimals using standard round-half-up.
- All percent/ratio values are rounded to 4 decimals using standard round-half-up.
- Lists use the template-prescribed ordering.
- Enum values match the template exactly (case-sensitive).
- The output is a single JSON object — no wrapping array, no extra text.