HR-P1 Staging UAT

Production rehearsal before DNS

The UAT gate confirms the new database runtime, standalone access, seed/import flow, multi-company isolation, and employee mobile workflows in staging.

DNS gateUAT firstProduction DNS waits for this suite and runtime readiness to pass against the target database.

Automated checks

Staging UAT suite

API backed

Area	Check	Expected outcome
Runtime	GET /people/v1/runtime-readiness	Postgres ping and required runtime tables
Auth	POST /people/v1/auth/login	Standalone HR admin session
Access	GET /people/v1/admin/company-access	Company grants and sensitivity ceiling
Employee master	GET /people/v1/employees	Scoped employee rows only
Mobile app workflows	GET /people/v1/mobile/home	Employee context, clock methods, leave, OT, payslip
UAT run	POST /people/v1/staging-uat/run	Aggregated pass/fail gate

Exit gates

Before DNS

No fixture dataProduction runtime must be postgres and fixture endpoints must return disabled.

Multi-company isolationAlpha HR cannot read Beta rows unless a company grant or consolidation grant exists.

Admin pathFirst admin bootstrap, login, company access, seed, and import are covered.

Account/ERP readyStable user_account_id, company_id, external mapping columns, and accounting output guard remain intact.