Skip to content

What this is

JobFrame is the flagship canonical work-intelligence layer — a governed Job Family × Focus × Level model (SOC/O*NET-rooted) that resolves messy titles, job descriptions, and HRIS rows into one canon, then maps, prices, and constructs jobs from it. It is the spine every other JobFrame and compensation capability maps into. MVP-0 (the Canonical Mapping Diagnostic) is live in production in the job-family-agent spoke (contract 1.16.0).

Capabilities

  • Classify — resolve a title/JD into the canonical Family × Focus × Level. GET /api/spokes/job-family-agent/classify · MCP job-family-agent.classify · UI /jobframe
  • Coordinates ("Pantone for jobs") — per-profile computable coordinates in measurable spaces with 3-state Delta-E matching and versioned editions. …/coordinates · job-family-agent.coordinates
  • Enterprise Job Architecture Workspace — top-down constructor with a draft-to-approved versioned lifecycle, tenant overlays, and a job-person-position graph. …/enterprise-jobframe/profiles
  • Analytics + Clarification Campaigns — 5-state value provenance + minimal-question campaigns that turn corrections into governed evidence. …/jobframe-analytics/analytics

Who it's for

Enterprises standing up or cleaning a job architecture; comp teams needing a stable spine to price against; HRIS owners resolving noisy records into a canon.

Why a canon

Pricing, benchmarking, and similarity all break on inconsistent titles. JobFrame gives every downstream capability one governed reference — so the same job means the same thing across comp, analytics, and planning.

Honest scope

Some pieces are staged (e.g. pay@1 and semantic coordinate spaces vs. live structural/content) — trust the registry and manifest status for what's callable today.

See also

AnyComp · Architecture · Concepts