Fit matrix — why the verdict is pilot
Hardware appears comfortable and the integrated proposal is relevant. Risk lies in operational breadth and runtime gaps. Pilot therefore preserves the opportunity and demands proof; adopt would exceed the evidence.
Complete Simple + Technical
Hardware appears comfortable and the integrated proposal is relevant. Risk lies in operational breadth and runtime gaps. Pilot therefore preserves the opportunity and demands proof; adopt would exceed the evidence.
Bounded analogy: It is an audition, not a permanent contract. The candidate passed initial tests but still must perform a real reversible task.
Under the hood
The matrix favors local Metal, chat/dashboard, and CLI in the first pass. Cloud/hybrid, agents, workflows, RAG, voice, search, and observability stay outside the core; ComfyUI has no fit on the documented macOS path.
Boundary: installation, runtime, and Docker/Compose were not executed.
14 semantic microdiagrams
Each figure teaches one relationship; the sequence is a decision map, not a health dashboard.
Command and proof boundary
rg -n '^VEREDICTO:|^## Matriz de fit|^## Plano de piloto' outputs/ods-adoption-dossier.md
Allows claiming
| check | reading |
|---|---|
| local | exercised contract |
| upstream | declared capability |
Remains open
| runtime | gate |
|---|---|
| health/chat/UI | live pilot |
| lifecycle | backup/restore/uninstall |
Local sources
outputs/ods-adoption-dossier.md:151-178outputs/ods-adoption-dossier.md:272-276outputs/ods-adoption-dossier.md:5-16outputs/ods-check-receipt.md:230-232
Includes dossier, receipt, and official source by path:line.
Practice with feedback
1 · Prediction
2 · Stepper
1. classify the need
2. locate the proof
3. decide without overclaiming
3 · Scenarios
4 · Checklist
6 · Quiz
Why not adopt?