litertlm_manifest.json

Deployment manifest for Hugging Face model repos that ship .litertlm bundles for the LiteRT-LM runtime: per-device file selection, verified backends, requirements, and measured performance

litertlm_manifest.json

Validate

Check your file against this schema

Opens the validator with this schema already loaded. Paste your litertlm_manifest.json and it validates in your browser — nothing is uploaded.

Validate a litertlm_manifest.json → View raw schema

Reference

Fields

Generated directly from the schema, following local $refs, to two levels of nesting.

Field	Type	Description
`manifest_schema`required	`string`	Version of the manifest format. The 0.1 line is the compatibility line: a 0.1.x release only adds optional fields, so a 0.2 manifest is rejected rather than half-parsed.
`repo`required	`string`	Hugging Face repo id (owner/name) the manifest lives in. Together with a variant's file name this is the download address.
`generated`required	`string`	Date the manifest was generated (YYYY-MM-DD).
`generator`	`string`	Tool that produced the manifest.
`model`required	`object`	Model-level facts. Fields marked Derived are read out of the bundle header by the generator; the rest are curated.
`model.display_name`required	`string`	Human-readable model name.
`model.base_model`	`string`	Hugging Face id of the source model.
`model.architecture`	`string`	Free-text architecture label, e.g. "lfm2-hybrid" or "qwen3-dense".
`model.parameters_b`	`number`	Parameter count in billions.
`model.license`	`string`	SPDX identifier, or a pointer to the license file.
`model.context_length`	`integer`	Derived: the bundle's max_num_tokens.
`model.capabilities`	`object`	Capability flags derived from the bundle header, so they are readable before download.
`model.capabilities.vision`	`boolean`	Derived: the bundle declares image input.
`model.capabilities.audio`	`boolean`	Derived: the bundle declares audio input.
`model.capabilities.thinking`	`object`	Derived: whether the bundle declares a thinking channel, and its markers. Mirrors the first declared channel.
`model.capabilities.channels`	`array`	Derived (manifest 0.1.1 and later): the bundle's full declared channel set, whether thinking, tool-call, or anything else the model declares.
`model.session_defaults`	`object`	Curated session knobs a wrapper should set that the engine cannot infer. An open object: readers take keys by name and ignore what they do not consume.
`model.session_defaults.max_output_tokens_min`	`integer`	A floor on the output-token budget (e.g. 2048 for reasoning models), never a cap.
`model.session_defaults.notes`	`string`	Curated guidance worth surfacing to the app developer.
`model.session_defaults.temperature`	`number`	Sampler hint.
`model.session_defaults.top_k`	`integer`	Sampler hint.
`model.session_defaults.top_p`	`number`	Sampler hint.
`variants`required	`array`	One entry per .litertlm file in the repo.

Audit

What we found in this schema

Declared draft: draft-07
Validates cleanly against its own meta-schema.
70 properties, 91% carrying a description, max nesting depth 7.

Standards

Specification sections for the keywords in this schema

Keyword	Document	Section
`$comment`	JSON Schema Core, draft 2020-12	§8.3 — Comments With "$comment"
`$id`	JSON Schema Core, draft 2020-12	§8.2.1 — The "$id" Keyword
`$ref`	JSON Schema Core, draft 2020-12	§8.2.3.1 — Direct References with "$ref"
`$schema`	JSON Schema Core, draft 2020-12	§8.1.1 — "$schema"
`additionalProperties`	JSON Schema Core, draft 2020-12	§10.3.2.3 — "additionalProperties"
`anyOf`	JSON Schema Core, draft 2020-12	§10.2.1.2 — "anyOf"
`description`	JSON Schema Validation, draft 2020-12	§9.1 — "title" and "description"
`enum`	JSON Schema Validation, draft 2020-12	§6.1.2 — "enum"
`examples`	JSON Schema Validation, draft 2020-12	§9.5 — "examples"
`format`	JSON Schema Validation, draft 2020-12	§7 — Vocabularies for Semantic Content With "format"
`items`	JSON Schema Core, draft 2020-12	§10.3.1.2 — "items"
`minItems`	JSON Schema Validation, draft 2020-12	§6.4.2 — "minItems"
`minimum`	JSON Schema Validation, draft 2020-12	§6.2.4 — "minimum"
`pattern`	JSON Schema Validation, draft 2020-12	§6.3.3 — "pattern"
`properties`	JSON Schema Core, draft 2020-12	§10.3.2.1 — "properties"
`required`	JSON Schema Validation, draft 2020-12	§6.5.3 — "required"
`type`	JSON Schema Validation, draft 2020-12	§6.1.1 — "type"
`format: "date"`	RFC 3339	§5.6 — Internet Date/Time Format

Documents

JSON Schema Core, draft 2020-12 — JSON Schema: A Media Type for Describing JSON Documents, A. Wright, H. Andrews, B. Hutton, G. Dennis, Eds., 2022. draft-bhutton-json-schema-01. An expired Internet-Draft with no formal standing in the IETF standards process; it is nonetheless the specification of record for JSON Schema 2020-12, published by json-schema.org.
JSON Schema Validation, draft 2020-12 — JSON Schema Validation: A Vocabulary for Structural Validation of JSON, A. Wright, H. Andrews, B. Hutton, Eds., 2022.
RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The format a schema describes.
RFC 6901 — JavaScript Object Notation (JSON) Pointer. Defines the pointer syntax used by $ref fragments and the ~0 / ~1 escapes.

Source

Attribution

This schema comes from SchemaStore, distributed under the Apache License 2.0. Copyright 2015–present Mads Kristensen and contributors. View the original file. The field table and audit on this page are generated by JSONTools.tools; the schema itself is unmodified.

← All schemas