cesnimda
14 lines
2.3 KiB
Markdown
14 lines
2.3 KiB
Markdown
# CV-IMPORT-01 handoff — implementation not started
|
|
|
|
This document supplies compatibility requirements from CV-UX-01. It does not authorise or start Docling, model qualification, legacy-parser replacement or Phase10 cleanup.
|
|
|
|
Career Profile remains the canonical career-data owner. An eventual import must preview and explicitly reconcile facts through the established profile service; it must preserve CV-specific overrides, hidden/order choices, null-as-inherit design settings and existing revisions. CV settings history resolves the current Career Profile; it is not a historical full-profile snapshot.
|
|
|
|
Cover letters use the parent JobApplication.Version for optimistic concurrency. Every intended writer stages current text, normalized document settings and history through ApplicationAssetsService before the parent transaction commits. Preserve generic null-clear versus draft null-unchanged semantics, no-op acknowledgements, recovery of previously uncovered legacy text, restore-as-new and owner filtering. Do not introduce an independent revision counter or write CoverLetterText directly from import code.
|
|
|
|
Contact/design copies are explicit reviewed snapshots. Imported facts or later CV edits must not silently rewrite saved letters. Historical text-only letters and submitted packages remain readable. New submitted packages freeze letter HTML/settings and CV output; future source changes must not rewrite their bytes. Account/backup portability includes letter design/history.
|
|
|
|
CV AI proposals are bound to owned source/revision capabilities and reviewed acceptance. Letter AI requires an owned linked CV with actual visible career evidence. Advert requirements, identity/header text and a previous letter do not establish experience. Import text is untrusted data, never model instructions. Reuse the existing approved self-hosted infrastructure; do not infer semantic, GPU or production readiness from CPU compatibility or mocked UI tests.
|
|
|
|
Before CV-IMPORT entry: read CV-UX final acceptance and its open gates, verify the accepted branch/commit and current architecture, re-establish supported-provider migration/rollback evidence and preserve frozen fixtures. Keep the legacy parser until the separately authorised replacement is qualified. Production, hosted isolation and security/recovery decisions remain separate.
|