# Exact unsent Grok prompt — EM-PEO-09

Independent enterprise metamodel review. Do not browse, invent identifiers or claim publication readiness.

EM-PEO-09 covers CompensationBand, CompensationAssignment, BenefitPlan, BenefitEnrollment and CompensationReview. No target IDs are allocated. Complete drafts cover Payroll / Compensation, Employment, Position, Money / Instrument, Price / Valuation, Decision / Approval Record, Payment, Projection / Disclosure Policy and Observation / Measurement. Privacy Aggregation Floor and Public Benefit / Program are reservations without current specs.

Assess this proposal: create identifier-unassigned Compensation Band, Compensation Assignment, Benefit Plan and Benefit Enrollment roots; keep plan eligibility and enrollment coverage as owned components; reject Compensation Review as a root and profile authoritative outcomes on WM-REC-010. Profile WM-ECO-031 for payroll calculation/payslip; reuse WM-ECO-009, WM-ECO-004, WM-ECO-002 and WM-XCT-003. Allocate no identifier.

Separate band/range, individual terms, employment, review decision, payroll calculation, payslip, payment settlement, statutory remittance, benefit-plan eligibility, enrollment/election, coverage, claim, valuation and aggregate disclosure. Every amount pins currency, basis, period, frequency, FTE normalization and source. Range is not an assignment. Payroll result is not payment. Employee benefits are not public programs. Aggregate releases must resist singleton, differencing, repeated-query and join attacks.

Test part-time work, multiple currencies, a mid-period change, benefit coverage independent of payroll and overlapping aggregates that would isolate one person.

Return <=900 words with: Verdict; strongest evidence; strongest counterexample; identity/mastership; band/range; assignment/components; review/decision; benefit plan/enrollment; payroll/payment; currency/time; aggregation/privacy; scenario; at least 10 invariants; minimum model set; blockers. Decide every candidate and relation/spec gap.