[2026-10-04] eagle: personal/career/profile.md personal/career/zoom-evidence/my-note_LKv7PP5oRNWI9GIMVfUIQg_27399f2c5d5f.md personal/plans/personal-os-operating-plan-2026-10-03.md personal/projects/personal-os/personal-os-purpose.md personal/projects/personal-os/personal-os-status-2026-10.md personal/projects/personal-os/project-truth-analyzer.md work/tech-design/coredata-code-defined-models.md work/zoom-evidence/my-note_LKv7PP5oRNWI9GIMVfUIQg_27399f2c5d5f.md

work/tech-design/coredata-code-defined-models.md

@@ -8,9 +8,13 @@ tags:
   - persistence
   - spm
   - build
-status: draft
-chosen-approach: 'Schemas defined in Swift with full version history; explicit lightweight migration'
+status: cancelled
+chosen-approach: >-
+  Schemas defined in Swift with full version history; explicit lightweight
+  migration
 asana: TODO
+updated: '2026-10-04'
+superseded_by: Xcode 27 / Swift 6.4 SPM Core Data model support
 ---
 **Author:** Alexey Martemyanov
 **Reviewer:** Sam Symons
@@ -19,6 +23,8 @@ asana: TODO
 
 ---
 
+> **Historical proposal — cancelled 2026-10-01.** Xcode 27 / Swift 6.4 swiftbuild compiles existing Core Data models as SPM resources, so the code-defined conversion was not implemented. The Asana subtask was completed to close the obsolete approach, not to mark its implementation. See [[work/projects/vscode-migration/vscode-migration]] and [Asana task 1218854852229979](https://app.asana.com/0/0/1218854852229979). The design below records the superseded reasoning.
+
 ## Background & Requirements
 
 We're moving development and CI to VS Code and SwiftPM builds that don't go through Xcode.