Source: schemas/library_manifest.schema.json #

View this page as Markdown

On this page

Generated automatically from the published contract sources.

Source path: schemas/library_manifest.schema.json.

The file itself is served at https://turnzero.ai/cloud/reference/sources/schemas/library_manifest.schema.json, the same bytes as the source below, for a validator that loads a schema by address.

Schema fields #

JSON pointer Description and constraints
"" (root) The shape of manifest.json at the root of your project's library folder: the record of the library entries your project has. It is not a copy of the catalog, which lists what a publish offers. The two share name, version, and the closure hash on purpose, so read_library compares your entries with the catalog's like for like. Only the turnzero command writes this file, when it takes an entry: library take, which the served installation and update skills direct, and scaffold, for a template that takes entries. The registrar's validate MCP tool, with the library kind, checks the file's form, each listed entry's hash, and any entry folder the file does not list. This check is local. An edit that changes both an entry's files and its hash passes it, and it does not check a version, source commit, or fetch time against a publication. To compare your entries with the current publication, use read_library. A test in the platform's suite checks this shape.

$schema: https://json-schema.org/draft/2020-12/schema
version: 2026-11-04.1
title: tzCloud — a project's library folder manifest
Type: object
Additional properties: false
Required fields: ["manifest_version","entries"]
/properties/manifest_version The format's revision. A file with an unknown revision is refused as malformed, never read best-effort, by the rule the admission manifest follows. A reader that guesses at a format it does not know drops, without a word, what it did not understand.

Required value: 1
/properties/entries One row per library entry your project has. A project with no entry has the empty array, never an absent member, so a folder that exists and is empty differs from one whose manifest was never written.

Type: array
uniqueItems: true
/properties/entries/items Type: object
Additional properties: false
Required fields: ["name","version","closure_hash","source_commit","fetched_at"]
/properties/entries/items/properties/name The entry's stable name, as the catalog returns it: a package's folder name, ui/<vocabulary>, fonts/<family>, or library/prd for the library's own requirements entry.

Type: string
Minimum length: 1
/properties/entries/items/properties/version The version your project has, spelled as in the entry's front matter. It is null for a font family, which has no specification and so no version, and for the library's own requirements entry, whose two documents declare none. For those two, compare the closure hash.

Type: ["string","null"]
/properties/entries/items/properties/closure_hash The SHA-256 hash of the entry's whole closure, as the catalog computed it, in 64 lowercase hex digits. validate hashes each entry again, compares the result with this value, and lists each entry whose files changed. The check is local: an edit that changes both the files and this hash passes it.

Type: string
Pattern: ^[0-9a-f]{64}$
/properties/entries/items/properties/source_commit The library commit this entry was published from, so you can trace its files to their source without the server's help.

Type: string
Minimum length: 7
/properties/entries/items/properties/fetched_at When this entry was written into your folder, in ISO 8601 form in UTC. The catalog has the publish date; this field has the date your project took the entry, which is later when you take a version some time after its publication. The schema checks the form with a pattern, not JSON Schema's date-time format, because that format needs the optional ajv-formats package, which this schema does not require. Without it, a strict validator refuses the schema and a lenient one ignores the format, a check that passes anything.

Type: string
Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]+)?Z$

Complete source #

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "version": "2026-11-04.1",
  "title": "tzCloud — a project's library folder manifest",
  "description": "The shape of `manifest.json` at the root of your project's library folder: the record of the library entries your project has (LC-07; SPM-L0-50). It is not a copy of the catalog, which lists what a publish offers. The two share `name`, `version`, and the closure hash on purpose, so `read_library` compares your entries with the catalog's like for like. Only the turnzero command writes this file, when it takes an entry: `library take`, which the served installation and update skills direct, and `scaffold`, for a template that takes entries (PLD-L0-100; PLD-L0-103). The registrar's `validate` MCP tool, with the library kind, checks the file's form, each listed entry's hash, and any entry folder the file does not list. This check is local. An edit that changes both an entry's files and its hash passes it, and it does not check a version, source commit, or fetch time against a publication. To compare your entries with the current publication, use `read_library` (LC-06). A test in the platform's suite checks this shape.",
  "type": "object",
  "additionalProperties": false,
  "required": [
    "manifest_version",
    "entries"
  ],
  "properties": {
    "manifest_version": {
      "description": "The format's revision. A file with an unknown revision is refused as malformed, never read best-effort, by the rule the admission manifest follows. A reader that guesses at a format it does not know drops, without a word, what it did not understand (LC-07; MAN-01).",
      "const": 1
    },
    "entries": {
      "description": "One row per library entry your project has. A project with no entry has the empty array, never an absent member, so a folder that exists and is empty differs from one whose manifest was never written.",
      "type": "array",
      "uniqueItems": true,
      "items": {
        "type": "object",
        "additionalProperties": false,
        "required": [
          "name",
          "version",
          "closure_hash",
          "source_commit",
          "fetched_at"
        ],
        "properties": {
          "name": {
            "description": "The entry's stable name, as the catalog returns it: a package's folder name, `ui/<vocabulary>`, `fonts/<family>`, or `library/prd` for the library's own requirements entry.",
            "type": "string",
            "minLength": 1
          },
          "version": {
            "description": "The version your project has, spelled as in the entry's front matter (FTR-L0-62). It is null for a font family, which has no specification and so no version, and for the library's own requirements entry, whose two documents declare none. For those two, compare the closure hash.",
            "type": [
              "string",
              "null"
            ]
          },
          "closure_hash": {
            "description": "The SHA-256 hash of the entry's whole closure, as the catalog computed it, in 64 lowercase hex digits. `validate` hashes each entry again, compares the result with this value, and lists each entry whose files changed (SPM-L0-49). The check is local: an edit that changes both the files and this hash passes it.",
            "type": "string",
            "pattern": "^[0-9a-f]{64}$"
          },
          "source_commit": {
            "description": "The library commit this entry was published from, so you can trace its files to their source without the server's help.",
            "type": "string",
            "minLength": 7
          },
          "fetched_at": {
            "description": "When this entry was written into your folder, in ISO 8601 form in UTC. The catalog has the publish date; this field has the date your project took the entry, which is later when you take a version some time after its publication. The schema checks the form with a pattern, not JSON Schema's `date-time` format, because that format needs the optional `ajv-formats` package, which this schema does not require. Without it, a strict validator refuses the schema and a lenient one ignores the format, a check that passes anything.",
            "type": "string",
            "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(\\.[0-9]+)?Z$"
          }
        }
      }
    }
  }
}