EM-PEO-09 · Subject model · W3
Compensation and Benefits
Compensation ranges, individual assignments and benefit plans. Payroll calculation and mandatory rules are attached via jurisdictional profiles.
Partially published; research continues
Claude: complete-initial-study-plus-single-frozen-audit-remediated; Grok: complete-reconciled.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- CompensationBand
- CompensationAssignment
- BenefitPlan
- BenefitEnrollment
- CompensationReview
Deep research questions
- Which components have different periods and bases?
- How is a position range separated from an individual contract?
- How are aggregates published without reconstructing an individual's salary?
Verifiable invariants
- An amount has a currency and a period
- A range is not an individual assignment
- The fact of payment comes from a financial source
End-to-end acceptance scenario
Verify a partial engagement, several currencies, a mid-period change of terms and an unsafe aggregate over a small group.
Negative case
An average salary is disclosed for a group of one person, or via the difference of two reports.
Approaches to compare
- HR Open: exchange of HR data
- W3C ORG and ESCO/SFIA: relationships, skills and levels of responsibility
- HRIS/ATS/LMS practice and independent verification of outcome measurement via SPACE
Candidates in the live catalogue
The boundary and the reuse / extension / new model route are not chosen yet.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.