AI Assistant

Ask in plain English. The router classifies your intent and dispatches to specialist agents — each calling the Workday APIs it needs. A harvester collects results. A composer generates a grounded answer with citations. Every call is logged to ai_decision_log.

How many open headcount reqs in Backcountry?

Show me garnishment compliance for this pay period

Compare Ontario vs California overtime rules for warehouse workers

Which candidates are past the interview stage with no scorecard?

Why is attrition spiking in Sur La Table CA stores?

Multi-Agent Workday Intelligence

Router → Specialist Agents → Harvester → Composer → Validated Answer
All queries are logged. All outputs are validated. All answers cite sources.

You · 14:38 UTC

Show me garnishment compliance for this pay period — any misses?

AI Assistant · 14:38 UTC · 2.4s

Agent execution trace

Intent Router

Classified as STRUCTURED · payroll compliance domain

regex match: "garnishment" + "compliance" → PAYROLL_AGENT

12ms

Payroll Agent

Fetched active garnishment orders + current period deductions

Payroll v46 → Get_Payroll_Results(pay_period=PP-2026-08)

Payroll v46 → Get_Submit_Payroll_Inputs(garnishment_filter=active)

340ms

Staffing Agent

Enriched with employee entity/location data

Staffing v46 → Get_Workers(employee_ids=[48329, 22107, ...])

180ms

Harvester

Merged payroll results with staffing data. Ran deterministic compliance check: active orders with $0 deducted.

45ms

Composer · Claude Sonnet 4.6

Generated grounded narrative from deterministic evidence. Validator: PASS

tool-calling: report_compliance_status()

1.8s

Of 342 active garnishment orders across all 13 entities this pay period, 341 were correctly applied. One miss was detected: employee EMP-48329 (Backcountry, UT) has active child-support order CO-2024-77821 (25% of disposable, effective 2024-11-01) showing $0 deducted in PP-2026-08. This breaks a 14-period successful deduction streak.^[1]

The case has been routed to the Compliance queue as CRITICAL (CASE-7F8A3B). Maria Kowalski was paged 2 hours ago. View in Anomaly Queue →

Metric	This period	Prior period	Status
Active orders	342	338	ON TRACK
Correctly applied	341 (99.7%)	338 (100%)	1 MISS
Court-contempt exposure	1 order	0	CRITICAL
Avg deduction accuracy	99.7%	100%	Target: 100%

Sources: [1] Payroll v46 · Get_Payroll_Results + Get_Submit_Payroll_Inputs · PP-2026-08 · run at 14:38:21 UTC

You · 14:40 UTC

Compare Ontario vs California overtime rules for our warehouse workers

AI Assistant · 14:40 UTC · 3.1s

Agent execution trace

Intent Router

Classified as HYBRID · cross-border compliance + narrative

LLM fallback classifier → CROSS_BORDER_AGENT + NARRATIVE_AGENT

420ms

Cross-Border Agent (CAN)

Fetched Ontario ESA overtime rules + current CAN warehouse headcount

Payroll_CAN v46 → Get_Payroll_Results(province=ON, job_family=warehouse)

Staffing v46 → Get_Workers(location=Toronto, job_profile=warehouse)

290ms

Payroll Agent (US)

Fetched CA DLSE overtime rules + CA warehouse headcount

Payroll v46 → Get_Payroll_Results(state=CA, job_family=warehouse)

Compensation v46 → Get_Compensation_Plans(state=CA)

310ms

Harvester

Merged CAN + US payroll data. Built comparison matrix.

55ms

Composer · Claude Sonnet 4.6

Generated cross-border comparison. Validator: PASS

2.0s

Key differences between Ontario and California overtime for CSC warehouse workers:

Rule	Ontario (ESA)	California (DLSE)	Impact at CSC
Daily OT threshold	None — Ontario has no daily OT	Over 8h/day = 1.5x; over 12h/day = 2x	CA warehouse shifts often hit 10h; daily OT triggers that Ontario doesn't
Weekly OT threshold	Over 44h/week = 1.5x	Over 40h/week = 1.5x	CA triggers 4 hours earlier per week
7th consecutive day	No special rule	First 8h = 1.5x; after 8h = 2x	Sur La Table CA stores with 7-day coverage: double-time exposure
Currency	CAD (min wage $17.20/hr ON)	USD (min wage $16.50/hr CA)	FX variance affects reporting — normalize to USD for board reporting
Affected headcount	47 workers (Toronto DC)	312 workers (CA warehouses)	CA exposure is 6.6x larger by headcount

Recommendation: The pre-payroll anomaly detector already handles CA daily-OT flagging (Anomaly Class #1). For Ontario, the detector should be extended to check the 44h/week threshold rather than the 40h federal US default. This is a one-line rule change in the deterministic check. I've filed this as a knowledge-gap signal for the weekly review.^[1][2]

Sources: [1] Payroll_CAN v46 · Ontario ESA Part VIII · Get_Payroll_Results · run at 14:40:18 UTC
[2] Payroll v46 · CA DLSE · Get_Payroll_Results + Compensation v46 · run at 14:40:19 UTC

            Router: regex first-pass → LLM fallback · Agents: Payroll · Staffing · Recruiting · Comp · Cross-Border · Harvester · Composer · Validator
          