docs(cv): complete builder implementation evidence

docs/work-programmes/decisions.md

@@ -359,3 +359,13 @@
 - **Consequences:** users receive a native discard decision for in-app navigation and browser-standard warning on unload. A blank name stays unsaved until corrected. The deeper builder redesign and browser checks remain CAREER-002 work.
 - **User approval required:** No; this is a reversible data-loss safeguard within the approved programme.
 - **Reversible:** Yes. Revert `b58cc19`; server variants and version history require no migration.
+
+## DEC-037 — Variant entries override profile facts; they do not delete them
+
+- **Date:** 2026-08-09
+- **Decision:** Keep profile-backed entries read-only at the ownership boundary: a CV variant may reorder, hide or override them, but cannot delete the Career Profile item. Provide full add/edit/reorder/confirmed-delete behavior only for variant-owned custom entries using the existing `string[]` model.
+- **Reason/evidence:** the architecture and resolver define variants as lenses over stable Career Profile item keys. Treating Delete in the Builder as profile deletion would violate separation and risk changing every CV. The custom-section model already owns document-specific content and needs no schema change.
+- **Alternatives considered:** delete profile entries from the Builder; clone profile entries into variants; add a second custom-entry table; keep the opaque one-item-per-line textarea. These violate ownership, duplicate data/infrastructure or fail the approved interaction requirement.
+- **Consequences:** original entries use Hide rather than Delete; custom entries receive explicit destructive confirmation. Existing render/public/PDF/version data remains compatible.
+- **User approval required:** No; this preserves the programme's explicit Career Profile separation and existing data.
+- **Reversible:** Yes. Revert `a5b74e0` and `2043349`; settings JSON remains backward-compatible.