Skip to content

Manifest Navigation

sarr-io edited this page Jun 14, 2026 · 6 revisions

Manifest Navigation ◌

Zinc resolves package refs by walking zinc.pkg.yaml.

Official term

manifest — the package file Zinc reads to find paths inside the package.

◌ Example

openai-responses.software.responses

means:

manifest key: software.responses
manifest node: software/responses.py
resolved file: <package-root>/software/responses.py

◌ Node shapes

A manifest node can be a string path:

software:
  responses: software/responses.py

Or a mapping with path:

software:
  responses:
    path: software/responses.py

✦ URI forms

zinc://packages/<package>/manifest/<path>
zinc://packages/<package>/files/<relative/path>

Examples:

zn read zinc://packages/openai-responses/manifest/software/responses
zn read zinc://packages/openai-responses/files/software/responses.py

▣ What Zinc does not do

Zinc does not interpret the key name.

software, settings, docs, shapes, commands, models, and scripts are all just manifest paths unless a package decides otherwise.

✧ Read next

Clone this wiki locally