One spine, many profiles, an honest crosswalk

Before you start

Your team is consolidating five framework obligations onto one internal spine. Your workspace holds exactly what `bash setup.sh ./work` stages on a real machine: the twenty valid 800-53 family abbreviations (`work/spine-families.txt`) and a seed crosswalk with four rows — one of them a deliberately planted orphan. The "Run validator" button runs the same logic as the lab's `validate-crosswalk.ts`, ported and verified byte-for-byte in CI against real runs of the committed validator, always against whatever your crosswalk says RIGHT NOW — its verdicts are earned, never scripted. Where the module's lab redirects output into `validation-before.txt` and `validation-after.txt`, you copy the verdict into those files here; same artifact, same discipline. One familiar face: the seed's `SC-28` row is the data-at-rest claim — the laptop-encryption question you have been asking machines since module 00 — now seen from the MODEL stage, where one encrypted-disk evidence package gets to answer four frameworks at once. One honesty note: the validator checks structure (real families, no orphans, legal labels). Whether a label tells the truth is yours to supply — the lab makes you feel exactly where that line sits.