[M0-D06a] Identify the first client's HRIS and roster export shape

[smiggleworth]

Note

Follow-up discovery issue from M0-D06 #63. It produces a recorded decision, not product code.

Decision needed

Which HRIS does the first client use, and what shape is its roster export?

M0-D06 (2026-09-22) decided that an HRIS roster export is the authoritative workforce source, with the identity-provider directory corroborating it and a manual roster accepted when no HRIS exists. It did not name the first client's HRIS or collect a sample export, because those are organization-specific facts. Per the 2026-09-22 product direction, no import is built until the canonical data shape and storage internals are settled, so this does not block recording the roster manually.

Questions to answer

• Name the first client's HRIS (for example Rippling, Gusto, or BambooHR), or confirm the client has none and will use the manual roster.
• Collect a de-identified sample roster export and record its stable worker identifier, status, manager, and date columns.
• Record which columns map to the M0-D06 minimum worker attributes and which contain restricted fields.

Involve

Compliance lead, HR or people operations.

Done when

• The decision, rationale, decision owner, and date are recorded in this issue.
• Record whether an HRIS import is actually needed. If it is, create a separate P1 R1-11 import delivery slice with backend and frontend children that cite the validated export shape and depend on EN-05 [EN-05 backend] Import with preview, reconciliation, and safe replay #195; keep manual R1-11a backend [R1-11a backend] Record workforce roster with source precedence #219 independent.

Source

M0-D06 remaining uncertainty, 2026-09-22.