Spoke

worker-resolution

Two-pass self-healing merges — fortified indices, deterministic merges, lineage + failure rosters.

Character

HRIS fragmentation after M&A or multi-source payroll leaves duplicated humans everywhere analytics expects uniqueness.

Problem

External. Headcount KPIs inflate because Workday IDs never reconciled Greenhouse hires post-close.

Internal. Glue sheets become tribal knowledge—with zero deterministic replay when auditors ask “why merged?” weeks later.

Philosophical. Identity resolution must be repeatable infrastructure—not bespoke analyst SQL heroics rewriting merges nightly.

Guide

PASS 1 fortifies auxiliary indices (Index_Reference-style semantics) aligning nicknames/emails/supplemental ladders; PASS 2 applies deterministic merges with vault precedence, supplemental fills obeying governance overlays, tenure-sensitive termination guards acknowledging rehire windows, surfaced failures exporting structured remediation rosters—all behind PAT-11 service-key POST ergonomics mirrored by MCP. Stateless boundary keeps ingestion anchored in segmentation-studio or toolbox.etl while maintaining explicit contracts for automation. worker-resolution emphasises deterministic introspection—not ML blackboxing.

Abstract

Background. Workforce analytics crumbles silently when heterogeneous extracts disagree on uniqueness keys—yet heavyweight MDM deployments exceed mid-market practicality absent API-callable merges.

Methodology. Index fortification primes subsequent merges aligning alias maps; deterministic merge kernels enforce hierarchical precedence respecting HRIS vault rules, supplementary column policy toggles (fill / overwrite / ignore), ladder escalation heuristics, failure enumerations aiding triage, plus terminator guards protecting reactivation flows when policy demands.

Scope. Stateless over caller payloads—won’t scrape vendor APIs proactively; ingestion stays upstream integrations.

Contribution. MCP + typed HTTP payloads enable regression-tested merges versus bespoke notebook improvisation and pair naturally with segmentation identity clusters when orchestrated externally.

Evidence / Provenance. README cites consulting Apps Script lineage (ETL_Pipeline.gs) with traceability nuances captured in PAT session reports—not vendored verbatim.

Plan

  1. 01

    POST multi-source bundles

    Supply aligned HR rows + governance flags enumerated in README contract appendices respecting service-key requirements.

  2. 02

    Inspect lineage + failures

    Consume structured outputs distinguishing confident merges versus operator queue candidates rather than blindly trusting fused ids.

  3. 03

    Iterate auxiliary indices

    Feed discovered aliases downstream when failure rosters exceed SLAs mandated by organisational risk appetite.

  4. 04

    Chain segmentation pipelines

    Pair outputs with segmentation-studio ingestion so canonical employee anchors remain synchronised downstream.

Call to Action

Direct. Rehearse PAT README examples once service-key environment configured for developer sandboxes leveraging synthetic fixtures.

Transitional. Read session dossier bridging Apps Script lineage vs Postgres implementation deltas.

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.

Worker resolutionINPUTSMAIN ACTIONSOUTPUTSAnchor HRIS extractsSystemOfRecordRowsSupplemental feedsShadowSourcePackTwo-pass self-healing joinReconcile dupes + aliasesGolden worker identitiesMasterRowGraph↳ merge lineageCOMPOSES WITHsegmentation-studioorg-graph

Try it now

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

worker-resolution.health

GET

POST merges require payloads + PAT-11 key; heartbeat verifies namespace wiring before scripted merges.

curl -sS "https://people-analytics-toolbox.vercel.app/api/spokes/worker-resolution/health"

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/worker-resolution/contracts/types.ts

Source path: src/spokes/worker-resolution/contracts/types.ts · GitHub

Try in Dev ConsoleRead the explainerBack to all spokes

Failure

Payroll accruals double-count commuters; pulses spam alumni merges guessed incorrectly—confidence in People Analytics plummets externally.

Success

Transparent lineage objects accompany merges—risk + analytics teams rerun identical payloads reproducing merges under audit glare.