JobFrame↗ jobframe.global

Job data is the backbone every workforce question rests on, and there is no canonical version of it. Titles are local, levels are incomparable across companies, and the market data that prices them arrives as an opaque percentile. So every analysis rebuilds the frame first, differently, and none of the answers reconcile.

Live at jobframe.global: job profiles, job coordinates, and the Role Reality Gap render natively off the canonical job tree (FAMILY.FOCUS.LEVEL) with an O*NET/SOC crosswalk and the pay model behind it. Served on the toolbox deploy with satellite aliases reserved.

• 01One addressable coordinate per job. FAMILY.FOCUS.LEVEL makes a role a stable key that pay, skills, postings, and guides can all join on — the join that makes cross-corpus comparison possible at all.
• 02The Role Reality Gap: theory versus market, per job. What a field's own canon says a role is FOR, set against what the market actually rewards — a corpus-backed contrast a generic job site structurally cannot produce.
• 03A modeled pay layer, not a resold survey cut. Benchmarks come from a multivariate model with published basis labels, so a figure can be interrogated rather than taken on faith.

Live at jobframe.global and bigger than the hub implied: 14,948 job profiles across 533 families and 44 superfunctions, levelled on 25 rungs across four parallel tracks (professional, support, management, executive) rather than one ladder everybody climbs, with a modeled 12-month pay outlook per profile that labels itself directional rather than observed. Load-bearing well beyond its own domain — the job spine AnyComp prices against, that Get2Great's per-job method keys to, and that the guide system pairs to occupations. Guides do not yet render natively here; that surface is still to come.