What mattered
Apple's system model is a free and private routing floor, but its context and action-grounding limits make it unsuitable as the core capability dependency for a realistic tool catalog.
What changed locally
PostTrainLLM measured the framework, retained a bridge for comparison, ruled out adapter dependency, and kept owned weights plus owned evaluation as the differentiation.
Evidence limits
Core ML remains a possible deployment target for owned weights. The rejection applies to depending on Apple's closed model for capability, not to every Apple runtime technology.
Retained disposition
Use the system model only where a fresh task-specific gate proves it sufficient.
The action is retained as study context rather than an active backlog item. Any implementation, download, training run, or benchmark requires a fresh scoped question under the repository's experiment gate.
How to read this dossier
This canonical page separates the retained repository decision from the material that informed it. A source may describe an external claim, historical measurement, local observation, or planned procedure; those evidence classes are not interchangeable. Follow the provenance links before reusing a number or method.
Status and disposition describe what PostTrainLLM retained when this record was indexed. They are not a live product promise, a newly run benchmark, or permission to restart historical work. Unknown or unmeasured fields remain unknown rather than being treated as zero.
To reuse the record, first name the exact claim you need and trace it to the linked source. Then check whether the original environment, model revision, data split, evaluator, hardware, and budget match the proposed use. If they do not, treat the record as a hypothesis or design reference and run the smallest fresh comparison that can falsify it. Preserve negative outcomes and regressions beside any improvement; a local win on one slice does not silently become a general capability claim.
Source provenance
The normalized record comes from docs/studies/registry.json. The links below are the tracked evidence and explanatory sources preserved with the record.