Spoke

wage-compliance

Jurisdictional wage engine — hierarchies + temporal precedence + roster evaluation + DOL/state refresh posture.

Character

You align total rewards narratives with multiplying federal/state/local mandates without standing up payroll software yourself.

Problem

External. Data vendors hawk rate tables but skip inheritance, supersession timelines, rooftop precision nuances, jurisdictional overlays.

Internal. Compliance counsel asks traceable rule chains per pay slip date—your spreadsheets cannot replay them faithfully.

Philosophical. Payroll compliance behaves like compilers—edge cases cascade; treat it programmatically—not as PDF scrapbooks.

Guide

Hierarchical jurisdictions, temporally versioned statutes, cite-backed payload rows (rule_versions), deterministic evaluation paths with explicit traces, PAT-97 advisory classifier layering industry hints (healthcare/computer professional/etc.), alert + temporal diff scaffolding for refresh agents, MCP mirrors REST for agentic ingestion—paired with integrations toward metrics-catalog compliant KPIs (compliance.pay-floor.*) and segmentation geo joins downstream. wage-compliance positions itself operational—not merely archival data resale.

Abstract

Background. Payroll risk escalates materially when locality ordinances supersede statewide minima inconsistently—and stakeholders still expect instantaneous roster-scale adjudication narratives.

Methodology. PAT-79 models nested jurisdictions referencing parent chains, merges families (minimum-wage seeded with extensibility toward OT thresholds), evaluates employees against effective windows emitting traces for audit, surfaces advisory classifications using curated statutory excerpts (explicitly disclaiming lawyer substitute), persists alert + temporal diff artefacts for monitoring automation (PAT-87 family). Geographic precision flags upcoming rooftop commitments transparently (rooftopPending) while seeds expand under PAT-80/PAT-86 initiatives.

Scope. Computational compliance guidance—not legal verdicts; synergy with segmentation geo dimensions + anycomp complianceFloor; does not ingest entire ERP ledgers implicitly.

Contribution. MCP + typed contracts unify agents + scripted bulk evaluation with deterministic logs vs opaque vendor black boxes.

Evidence / Provenance. PAT-79 briefing pack + roadmap cross-links enumerated in README + vision docs inside docs/.

Plan

  1. 01

    Resolve jurisdictions

    Translate structured geo inputs into deterministic jurisdiction chains aligning with seeded coverage when migrations complete.

  2. 02

    Evaluate rosters

    Bulk POST employees under PAT-11 service keys persisting discrepancy metadata when PAT-94 persistence toggled for review queues historically filed.

  3. 03

    Monitor deltas + alerts

    Subscribe to PAT-87-driven tables once refresh agents populate temporal diff payloads + alert ingestion streams.

  4. 04

    Integrate downstream

    Feed compliance floors toward anycomp evaluation + metrics-catalog definitions for KPI rollups surfaced on decks.

Call to Action

Direct. Try public-read rule-change summaries once seeds land; practise evaluation POST payloads in sandbox with service-key headers.

Transitional. Digest WAGE-COMPLIANCE-VISION positioning memo linked from README intros.

Spoke I/O (visual language v1)

Every toolbox spoke shares the same abstract choreography: typed inputs on the left, distilled verbs in the center, typed outputs on the right, and (when relevant) cross-spoke HTTP composition along the bottom rail. Source package: @people-analytics-toolbox/spoke-illustrations.

Wage complianceINPUTSMAIN ACTIONSOUTPUTSJob offer envelopeCompOfferFactsJurisdiction fingerprintRuleStackRefResolve hierarchical rulesEmit verdict + remediationCompliance outcomeVerdictCard↳ FLSA ⇄ stateCOMPOSES WITHjob-family-agent

Try it now

Copy this curl. Paste in any terminal. Public read — no auth needed.

wage-compliance.rule-changes.recent

GET

Public read listing recent temporal diff artefacts once populated (may be sparse pre-seeding).

curl -sS "https://people-analytics-toolbox.vercel.app/api/spokes/wage-compliance/rule-changes/recent?limit=5"

Vendor the contract

The Zod contract is the source of truth. Vendor a copy into your consumer app — you keep it; we don't break it underneath you. Re-vendor when the version bumps.

// Vendor canonical types:
// src/spokes/wage-compliance/contracts/types.ts

Source path: src/spokes/wage-compliance/contracts/types.ts · GitHub

Try in Dev ConsoleRead the explainerRegistry tooling on /operatorBack to all spokes

Failure

Local ordinance tweaks invalidate centrally published “national minima” spreadsheets overnight—risk teams discover tardily during litigation questionnaires.

Success

Transparent jurisdiction traces + citations travel with evaluations so finance + legal reconcile pay dates defensibly—even under rooftop precision growth roadmaps (PAT-89 family).