Schema

Files directly in this folder are the current data contract — only what has passed the schema-first gate. Nothing here is draft or pending review.

• Feature Sets propose changes via feature-sets/<slug>/schema-changes.md. Once the gate is signed, this folder is updated to match and the proposing delta file's frontmatter status flips to applied.
• Schema documented outside the Feature Set flow (e.g. reverse-engineered from an existing app) goes directly in this folder too, with status: applied and derivation: reverse-engineered in its frontmatter — there is no separate schema/pending/ holding area (retired per github-private/docs/ai-dlc/decisions.md's 2026-08-07 entry).

Do not read feature-sets/<slug>/schema-changes.md as current state — only files directly in schema/ are current. Everything else is a historical or in-flight record of how we got here.

One file per app/sub-domain, since this repo spans several -sn-app repos:

• core-hr-schema.md — nova-corehcm-sn-app (derivation: reviewed, confirmed against the live app by Ravi Buddharaju)
• edm-schema.md — nova-edm-sn-app (Worker Document Management)
• onboarding-schema.md — nova-onboarding-sn-app
• compensation-schema.md — nova-compensation-sn-app (Payroll & Benefits)

All four were reverse-engineered directly from each app's live dictionary on main (not from tables.md, which each file's own Discrepancies section notes as stale in places). Each links its own cross-repo dependency (mainly on Worker/Person/Company/JobProfile in core-hr-schema.md, and on specs-platform's TransactionInstance/EventQueue base tables).