Interior · Filenames expose the artifact choices
Model Filename Lab
The first interior page focuses on the anatomy hidden inside concrete model filenames.
Broken intuition
A long filename helps a human guess what is inside, but the repo still needs the pinned repo, revision, exact file-or-snapshot shape, and later integrity data before it can trust anything. src/coding_agent/fetch.clj:73-90 src/coding_agent/lock.clj:41-64
Experiment
Filename reading is a naming signal, not proof. Exact repo, revision, file, checksum, and manifest are the proof this repo can automate.
This lab is deliberately lossy: it helps read hints, then pushes back toward the stronger artifact fields from the previous page.
Revealed constraint
One filename can hint at family, quant, tuning, or packaging, but it cannot prove that the repo tree still contains the expected file, that the revision is pinned, or that the chosen quant selector is specific enough. resolve-quant-file enforces that last boundary by accepting exactly one match. src/coding_agent/fetch.clj:27-35 src/coding_agent/fetch.clj:73-90
Named concept
The useful habit is lossy filename reading: take the name as a clue, then verify it against repo, revision, exact file, checksum, and manifest data. That is why a GGUF file path, an MLX repo snapshot, and companion files like mmproj-BF16.gguf or MTP/gemma-4-26B-A4B-it-Q8_0-MTP.gguf are treated as separate facts. profiles/m3-max-128gb.edn:12-39 profiles/m1-16gb.edn:10-27 src/coding_agent/lock.clj:41-64
Repo implementation
The fetch layer lists the pinned revision tree, resolves a quant token to one filename, then fetches the main model and any companions at that same revision. The lock layer records either exact GGUF sha256 values or an MLX snapshot manifest, so the later serve path does not rely on guesses from the filename alone. src/coding_agent/fetch.clj:50-63 src/coding_agent/fetch.clj:73-90 src/coding_agent/fetch.clj:109-119 src/coding_agent/lock.clj:41-64
Recognition
Choose the reading that needs the most extra proof.
Select a filename claim to see whether the name alone proves it.
Sources
src/coding_agent/fetch.clj:27-35 src/coding_agent/fetch.clj:50-63 src/coding_agent/fetch.clj:73-90 src/coding_agent/fetch.clj:109-119 src/coding_agent/lock.clj:41-64 profiles/m1-16gb.edn:10-27 profiles/m3-max-128gb.edn:12-39