Why a blank on a model card means something else
This register records documentation rather than behaviour, so every entry is read the same way. A published licence changes what the blanks are worth, because anybody can resolve them by running the thing. As of 2026-09-12.
| Question | On a hosted API | On published weights |
|---|---|---|
| Can it be resolved | Only by the vendor | By anyone with the weights |
| How long it stays open | Until a page changes | Until somebody measures it |
| What the blank means | No commitment offered | Not written down yet |
| Who bears the risk | The customer | Whoever deploys it |
Inclusion rule. Differences in how an undocumented behaviour behaves as a risk, by release type. Order. Alphabetical by question.
1The register still reads every entry the same way
A comparison only works if the same rule was applied everywhere. Reading code for one entry and pages for the rest would produce a table where one row was generated by a different method, which is worse than a table with a blank in it.
So the licence is logged as a fact of its own instead. A reader can then discount that silences on that row deliberately, which is a judgement the register supports rather than makes on their behalf.
2A permissive licence is also a support obligation
Resolving a blank by running the model means somebody has to run it, keep it running, and notice when a new version behaves differently. That is a real cost, and it is the cost that hosted products exist to remove.
For a small production the hosted blank is often the cheaper one to live with. For a team already operating its own inference, the open blank is barely a gap at all.
3Measurement produces a finding, not a specification
Testing how a model handles overlapping speech gives a result for that build, on that material, on that day. It is genuinely useful and it is not a commitment, so it belongs in the notes a production keeps, with a date, rather than in a comparison table.
That is the same rule this register applies to itself. Nothing here comes from generating a clip and listening to it, because a sample describes the sampling.
4Where the published detail is logged
What is described above is how the techniques work in general. Which models document which of them, in whose words, is kept in the speech controls table with a date on every field.
- What kind of page — four kinds of document, four silences
- How a field gets filled in — and why nothing comes from output
A mechanism note rather than a documented field. Nothing here is attributed to a model, and nothing here is a claim about one. The sourced material is on the speech controls table. Related: Two kinds of fix, Framing and the mouth.