# SME roster — ASHR.work

Contract item **A5** of `docs/b2b/PRODUCT-INTEGRATION-PACK.md`.

**This file names roles, not people, and that is deliberate.** Certification is
gated by humans at three points. Appointing those humans is a human decision
with real accountability attached — an Angoff rating sets a cut score that
decides whether a person passes or fails. An agent inventing plausible names to
satisfy the contract's "at least 2 SME contacts" rule would produce a roster
that looks complete and certifies nothing.

**Status: unfilled.** Tracked as `TRACKER.md` row **M6-01** and
`UNBLOCK-REGISTER.md` **UB-06**.

## The three gates, and who has to staff them

| Gate | What the human actually does | Minimum | Role that should hold it |
|---|---|---|---|
| **Angoff cut-score panel** | Rates every item: "what fraction of minimally-competent candidates get this right?" The panel's output *is* the cut score. | 3 SMEs per track | `ashr-ops`: People Operations Lead + Payroll Operations Lead + one practising customer-side HR admin. `ashr-posh`: POSH Designated Point of Contact + the reviewing lawyer or an external POSH practitioner + one non-HR employee representative. |
| **Item / blueprint review** | Reviewer-role sign-off that promotes items to `live` and blueprints to published. | 1 reviewer per track, not an author of the items | Product Owner for `ashr-ops`; the Designated Point of Contact for `ashr-posh`. |
| **Drift review** | When the Miatz crawler flags changed ASHR.work docs (`content.drift_detected`), confirms whether the affected items still hold. | 1 per track, standing commitment | Same reviewers. |

## Constraints a filled roster must satisfy

1. **Three, not two.** The contract's A1 rule is "at least 2 SME contacts"; the
   A5 Angoff panel needs "3+". Three is the real floor. The manifest lists three
   role-shaped contacts for that reason.
2. **`ashr-posh` needs a POSH-competent panel, not the ops panel.** The people
   who know how a payroll run locks are not thereby qualified to rate an item
   about a Local Committee's statutory timeline. `docs/POSH_POLICY.md` itself
   requires legal review before adoption; the same review should cover the item
   bank.
3. **A reviewer must not review their own items.** The contract separates
   authoring from the sign-off that promotes items to `live` — one person doing
   both removes the gate.
4. **The `ashr-posh` panel should include someone who is not HR.** The policy's
   own redressal design assumes a complainant may need a route that does not run
   through the people who manage them; a panel drawn entirely from HR will not
   see where that route is unclear.
5. **Names go in `miatz.product.json` `contacts.smes`**, in the contract's
   `name <email>` form, replacing the role placeholders — and the roster's status
   line above changes from "unfilled" in the same commit.

## What is NOT blocked on this

Publishing the pack. The manifest, tracks, blueprints, items and credentials are
all authored and served regardless; the roster gates *certification*, not
publication. Miatz can crawl and mirror this pack today and hold the item bank
in `draft` until the panel exists.