Skip to content

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, not yet reviewed) 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). If a reverse-engineered doc needs review, that happens via a normal PR against the file, same as any other schema change.

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.

  • platform-schema.mdnova-platform-sn-app, reverse-engineered directly from the live dictionary on main (github-private's tables.md for this repo is significantly stale — see that file's Discrepancies section). This is the shared transaction/event/agent infrastructure specs-corehr and specs-time-attendance both extend — see its Cross-repo dependencies section for the load-bearing base tables.