Reference¶

| Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance |

One page per document kind, plus the kernel interface, the closed | [Acceptance profiles](acceptance.md) | `AcceptanceProfileSet`, inline acceptance values, a scenario's pin | [`spec/acceptance`](https://github.com/inference-sim/blis-schemas/tree/main/spec/acceptance) | vocabularies, the rules packs and the two commands. Each document page opens with an | [Acceptance profiles](acceptance.md) | `AcceptanceProfileSet`, inline acceptance values, a scenario's pin | [`spec/acceptance`](https://github.com/inference-sim/blis-schemas/tree/main/spec/acceptance) | example, then lists every key the document may contain, then every check its validator | [Acceptance profiles](acceptance.md) | `AcceptanceProfileSet`, inline acceptance values, a scenario's pin | [`spec/acceptance`](https://github.com/inference-sim/blis-schemas/tree/main/spec/acceptance) | makes.

| Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance |

| Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | The key tables are tested against the Go types: a key the type declares and the table | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | omits, or a key the table lists and the type does not declare, fails the build. The | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | vocabularies and the rules pack listings are generated from the code. For anything finer | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | than these pages, read the source; each page links to it. | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance |

| Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | | Page | Documents | Package | | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | |---|---|---| | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | | Scenario | Scenario | spec/scenario | | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | | Deployment | Deployment | spec/deployment | | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | | Workload | a scenario's workload, a catalog workload shape | spec/workload | | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | | Model graph | ModelGraph, a model's identity manifest | spec/model | | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | | Hardware | chip, fabric, storage classes | spec/hardware | | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | | Coefficient set | CoefficientSet | spec/coefficient | | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | | Evaluation run | EvaluationRun | spec/evaluation | | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | | Kernel interface | the Kernel a cost model implements | kernel | | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | | Vocabularies | units, methods, scope keys, dtypes, and the rest | vocab and spec/ | | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | | Rules packs | the checks for each engine version | rules | | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | | Command line | validate-catalog, validate-registry | cmd | | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance |

| Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | In the key tables, Type is the YAML type. Required means that if the key is absent, | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | the validator reports an error or the loader fails. A key marked no may be omitted, and | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance | the table says what omitting it means. | Acceptance profiles | AcceptanceProfileSet, inline acceptance values, a scenario's pin | spec/acceptance |