{
  "title": "The VAO learning lab: explore, decide, reuse — Virtual Acoustic Objects",
  "text": "MODAVIS (2026). The VAO learning lab: explore, decide, reuse — Virtual Acoustic Objects. Research notebooks, October 2026 · Interactive reuse and evidence edition. https://modavis.org/editions/2026-10-workbench/vao/package-lab/",
  "bibtex": "@misc{modavis_vao_package_lab_2026_10_workbench,\n  author = {{MODAVIS}},\n  title = {The VAO learning lab: explore, decide, reuse — Virtual Acoustic Objects},\n  year = {2026},\n  month = {10},\n  version = {2026-10-workbench},\n  url = {https://modavis.org/editions/2026-10-workbench/vao/package-lab/},\n  note = {Content SHA-256: 14d91fdfc09157c1f3f2925d886c14947d7989f1bd534915690b9f08f4d1ba96}\n}",
  "url": "https://modavis.org/editions/2026-10-workbench/vao/package-lab/",
  "sha256": "14d91fdfc09157c1f3f2925d886c14947d7989f1bd534915690b9f08f4d1ba96",
  "edition": "2026-10-workbench",
  "date": "2026-10-09",
  "canonicalPayload": "{\"book\":{\"number\":\"01\",\"slug\":\"vao\",\"title\":\"Virtual Acoustic Objects\"},\"chapter\":{\"blocks\":[{\"items\":[{\"detail\":\"Edit, run real validation, repair and download.\",\"href\":\"/notebooks/vao/workbench/\",\"label\":\"Continue with the interactive workbench\"}],\"type\":\"links\"},{\"id\":\"vao-learning-lab\",\"intro\":\"Work at your own pace. Each short lesson links back to the full notebook explanation. You can revisit any answer, save your learning notes and continue later on this device.\",\"lessons\":[{\"id\":\"versions\",\"label\":\"Identity\",\"next\":{\"detail\":\"\",\"href\":\"/notebooks/vao/structure/#carrier-roles\",\"label\":\"Read about release and format identity\"},\"options\":[{\"correct\":true,\"feedback\":\"Yes. Retain 0.5.0-rc.2 separately as the object content version.\",\"id\":\"format\",\"label\":\"0.5.0 — the exchange contract\"},{\"correct\":false,\"feedback\":\"That names the dataset content release, not its declared formatVersion.\",\"id\":\"content\",\"label\":\"0.5.0-rc.2 — copied from the dataset label\"},{\"correct\":false,\"feedback\":\"A client version cannot silently change the format contract of an existing release.\",\"id\":\"latest\",\"label\":\"Whatever version the viewing software uses\"}],\"question\":\"Which formatVersion should describe this released Cuntz object?\",\"text\":\"VAO formatVersion names the exchange contract. The instrument’s content version names one published object release. Cuntz uses formatVersion 0.5.0 while its released content is labelled 0.5.0-rc.2. Keep both: a similar-looking string is not a reason to rewrite the format version.\",\"title\":\"Two versions, two different jobs\",\"visual\":{\"caption\":\"The dataset release label does not make the finalized exchange contract a release candidate.\",\"layout\":\"compare\",\"nodes\":[{\"detail\":\"The rules for reading and checking the object.\",\"icon\":\"book\",\"label\":\"Standard\",\"value\":\"VAO 0.5.0\"},{\"detail\":\"The particular dataset release used here.\",\"icon\":\"cube\",\"label\":\"Cuntz content\",\"value\":\"0.5.0-rc.2\"}],\"title\":\"Read each version in its proper place\"}},{\"id\":\"realizations\",\"label\":\"Exact files\",\"next\":{\"detail\":\"\",\"href\":\"/notebooks/vao/model-study/#cuntz-provenance\",\"label\":\"Follow the actual Cuntz model derivation\"},\"options\":[{\"correct\":true,\"feedback\":\"Correct. Keep the derivation relationship and applicable attribution; a new byte sequence has a new realization identity.\",\"id\":\"new\",\"label\":\"Describe the derivative with its own size and SHA-256\"},{\"correct\":false,\"feedback\":\"The subject can stay the same while the bytes change. The original digest would fail an integrity check.\",\"id\":\"reuse\",\"label\":\"Keep the original digest because the subject is the same\"},{\"correct\":false,\"feedback\":\"A new filename does not establish the new file’s exact identity or record how it was derived.\",\"id\":\"rename\",\"label\":\"Only change its filename\"}],\"question\":\"You simplify a GLB. What should happen to its exact-byte identity?\",\"text\":\"The website’s light Cuntz GLB is derived from its more detailed display model. Its size and digest differ. It can serve the same visual research subject without being the exact file the detailed realization identifies. Preserve the source relationship and distinguish the files.\",\"title\":\"A light preview is a new realization\",\"visual\":{\"caption\":\"Changing an encoding changes realization identity even when it serves the same logical asset.\",\"layout\":\"flow\",\"nodes\":[{\"detail\":\"Its intellectual role and subject are identified.\",\"icon\":\"cube\",\"label\":\"Logical asset\",\"value\":\"The model as a resource\"},{\"detail\":\"A particular byte sequence and digest.\",\"icon\":\"database\",\"label\":\"Realization\",\"value\":\"One exact GLB\"},{\"detail\":\"A location must resolve to the promised bytes.\",\"icon\":\"external\",\"label\":\"Distribution\",\"value\":\"A way to acquire it\"}],\"relations\":[\"has an exact encoding\",\"is available through\"],\"title\":\"One role can have more than one encoding\"}},{\"id\":\"closure\",\"label\":\"Delivery\",\"next\":{\"detail\":\"\",\"href\":\"/notebooks/vao/delivery/\",\"label\":\"Read the carrier and receipt workflow\"},\"options\":[{\"correct\":true,\"feedback\":\"Exactly. Full preservation closure and other capabilities still need their own checks.\",\"id\":\"task\",\"label\":\"This available representation can be inspected\"},{\"correct\":false,\"feedback\":\"A working entry point does not show that every realization and dependency is present.\",\"id\":\"whole\",\"label\":\"The complete release has been preserved locally\"},{\"correct\":false,\"feedback\":\"Visual geometry does not establish the data or runtime support required for playback.\",\"id\":\"audio\",\"label\":\"The instrument is ready for acoustic playback\"}],\"question\":\"A bootstrap opens and its model displays. What have you established?\",\"text\":\"A bootstrap carrier gives you an entry point. A preservation-closure carrier contains every realization and completes every group. A custom carrier can hold a local selection. For a task, select declared groups and recursively include their dependencies; do not infer completeness from a successful preview.\",\"title\":\"Choose what a task needs, then follow the dependencies\",\"visual\":{\"caption\":\"This is a general closure illustration. It does not invent missing groups in the Cuntz manifest.\",\"layout\":\"flow\",\"nodes\":[{\"detail\":\"Choose a declared group, not a guessed filename.\",\"icon\":\"compass\",\"label\":\"Requested group\",\"value\":\"Your intended task\"},{\"detail\":\"Follow dependsOnGroupIds recursively.\",\"icon\":\"network\",\"label\":\"Dependencies\",\"value\":\"Required supporting groups\"},{\"detail\":\"All required exact members are available.\",\"icon\":\"check\",\"label\":\"Complete selection\",\"value\":\"Verified realizations\"}],\"relations\":[\"follow the dependency links\",\"verify the resulting set\"],\"title\":\"A usable selection includes its dependencies\"}},{\"id\":\"validation\",\"label\":\"Review\",\"next\":{\"detail\":\"\",\"href\":\"/notebooks/standards/reuse-checklist/\",\"label\":\"Use the release-readiness checklist\"},\"options\":[{\"correct\":true,\"feedback\":\"Yes. Conformance does not erase the released qualification or invent a session date.\",\"id\":\"scope\",\"label\":\"Only if the source evidence supports that interpretation\"},{\"correct\":false,\"feedback\":\"A valid date value does not establish what event it dates.\",\"id\":\"valid\",\"label\":\"Yes, because its date field is structurally valid\"},{\"correct\":false,\"feedback\":\"Keep it. The qualification is part of what makes the observation reusable and interpretable.\",\"id\":\"drop\",\"label\":\"Remove the qualification to make the record simpler\"}],\"question\":\"A file validates. Can you treat its timestamp as a verified measurement-session date?\",\"text\":\"Validation checks the declared contract: structure, relationships, profiles and exact-byte integrity, with further layers when claimed. Research review asks whether the evidence supports a historical or acoustic conclusion. The released Cuntz timestamp qualification is a useful reminder: a valid date can still be a workbook modification time.\",\"title\":\"A passed validator tells you what it checked\",\"visual\":{\"caption\":\"Technical validation and scientific review answer different questions.\",\"layout\":\"flow\",\"nodes\":[{\"detail\":\"Identify which requirements were checked.\",\"icon\":\"book\",\"label\":\"Contract\",\"value\":\"Version + profiles\"},{\"detail\":\"Parsing, relationships, fixity and other claimed layers.\",\"icon\":\"check\",\"label\":\"Technical checks\",\"value\":\"Recorded outcomes\"},{\"detail\":\"Review what the result can support.\",\"icon\":\"quote\",\"label\":\"Research judgment\",\"value\":\"Evidence & interpretation\"}],\"relations\":[\"run the relevant checks\",\"interpret their limits\"],\"title\":\"A useful result states its scope\"}}],\"mode\":\"package\",\"title\":\"From a file to a reusable research object\",\"type\":\"lab\"},{\"id\":\"apply-package-learning\",\"text\":\"Turn the practice into your own next step\",\"type\":\"heading\"},{\"type\":\"visual\",\"visual\":{\"caption\":\"A successful practice carrier gives you a working method. Your actual publication still needs its own sources, rights, identifiers and review.\",\"layout\":\"flow\",\"nodes\":[{\"detail\":\"Use the versioned release and an isolated working copy.\",\"icon\":\"book\",\"label\":\"Start small\",\"value\":\"A known-good fixture\"},{\"detail\":\"Trace a resource to the bytes and check its contract.\",\"icon\":\"search\",\"label\":\"Inspect & validate\",\"value\":\"Understand the report\"},{\"detail\":\"Replace identities, sources and capabilities as a coherent new release.\",\"icon\":\"compass\",\"label\":\"Adapt deliberately\",\"value\":\"Your research object\"}],\"relations\":[\"learn what the fields do\",\"carry the method forward\"],\"title\":\"Your first successful reuse loop\"}},{\"text\":\"Choose one resource from your own project. Write down its subject, whether it was captured or derived, the source it depends on, the exact file you will use, and the rights that travel with it. Then identify the smallest capability your initial carrier must support. This gives you a focused first release instead of an unnecessarily large application.\",\"type\":\"p\"},{\"boundary\":\"A downloaded bootstrap does not prove that every external resource has been fetched or verified.\",\"concept\":\"A manifest describes the research object and its resource relationships. A carrier is a package that delivers some or all of those exact resources.\",\"expanded\":false,\"id\":\"cuntz-carriers\",\"scenario\":\"The published Cuntz record offers a bootstrap carrier and a preservation carrier. The release states that both carry the same manifest; the preservation carrier includes every declared realization.\",\"sources\":[{\"detail\":\"Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release.\",\"href\":\"https://doi.org/10.5281/zenodo.22151203\",\"label\":\"Cuntz Positiv · VAO 0.5.0-rc.2\"},{\"detail\":\"The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2.\",\"href\":\"https://doi.org/10.5281/zenodo.22214248\",\"label\":\"VAO Standard 0.5.0\"}],\"steps\":[{\"text\":\"The bootstrap supplies the semantic inventory and core evidence. It lets a reader discover what exists without first downloading all the media.\",\"title\":\"Begin with the inventory\"},{\"text\":\"A geometry inspection needs the selected model and its dependencies. A playable experience may need audio, control mappings and other groups. Reading metadata does not make those resources locally available.\",\"title\":\"Request the required material\"},{\"text\":\"The complete preservation carrier supports the full declared realization inventory. Cite the exact release and record which carrier or selected closure you actually acquired.\",\"title\":\"Choose preservation deliberately\"}],\"takeaway\":\"One research release can have several delivery packages without becoming several historical interpretations.\",\"title\":\"Why does the Cuntz release offer two VAO downloads?\",\"type\":\"example\",\"visual\":{\"caption\":\"These delivery roles can carry the same semantic release. Small does not mean complete.\",\"layout\":\"compare\",\"nodes\":[{\"detail\":\"Carries entry-point resources and pinned references.\",\"icon\":\"book\",\"label\":\"Bootstrap\",\"value\":\"Discover & select\"},{\"detail\":\"Completes the release’s groups and dependencies.\",\"icon\":\"database\",\"label\":\"Preservation closure\",\"value\":\"Keep every realization\"}],\"title\":\"A small entry point and a full preservation copy\"}},{\"items\":[{\"detail\":\"Run the validated starter-fixture workflow.\",\"href\":\"/notebooks/vao/reuse/\",\"label\":\"Make a real practice carrier\"},{\"detail\":\"A separate, attributed Cuntz model viewer with its source and limitations.\",\"href\":\"/notebooks/vao/model-study/\",\"label\":\"Inspect the actual instrument model\"},{\"detail\":\"Practice identity, evidence, context and structural validation.\",\"href\":\"/notebooks/ontologies/graph-lab/\",\"label\":\"Learn the ontology relationships\"}],\"type\":\"links\"}],\"intro\":\"Make four decisions about one research object. See the connections, check your reasoning, and pull a conceptual package apart in an optional 3D view.\",\"overview\":{\"example\":{\"detail\":\"\",\"href\":\"#cuntz-carriers\",\"label\":\"See the worked example\"},\"summary\":\"A manifest describes the research object and its resource relationships. A carrier is a package that delivers some or all of those exact resources.\",\"takeaway\":\"One research release can have several delivery packages without becoming several historical interpretations.\"},\"slug\":\"package-lab\",\"sources\":[{\"detail\":\"Specification, schemas, reference tools and fixtures. Use this exact standard version for the exercises.\",\"href\":\"https://doi.org/10.5281/zenodo.22214248\",\"label\":\"VAO Standard 0.5.0 · immutable release\"},{\"detail\":\"Terms, governed vocabularies, versioned shapes and interpretation guide.\",\"href\":\"https://doi.org/10.5281/zenodo.22126086\",\"label\":\"MODAVIS Ontology Network 0.1.0 · immutable release\"},{\"detail\":\"The real observation and model used for the Cuntz examples. Its content version differs from VAO formatVersion 0.5.0.\",\"href\":\"https://doi.org/10.5281/zenodo.22151203\",\"label\":\"Cuntz Positiv · content release 0.5.0-rc.2\"}],\"title\":\"The VAO learning lab: explore, decide, reuse\"},\"date\":\"2026-10-09\",\"edition\":\"2026-10-workbench\",\"figures\":{},\"glossary\":[{\"definition\":\"A package or workspace that contains a manifest, carrier mapping and selected realizations. Bootstrap, preservation-closure and custom carriers serve different delivery purposes.\",\"example\":{\"detail\":\"\",\"href\":\"/notebooks/standards/cuntz/#cuntz-carriers\",\"label\":\"Work through the Cuntz example\"},\"term\":\"Carrier\"}]}",
  "payload": {
    "edition": "2026-10-workbench",
    "date": "2026-10-09",
    "book": {
      "slug": "vao",
      "title": "Virtual Acoustic Objects",
      "number": "01"
    },
    "chapter": {
      "slug": "package-lab",
      "title": "The VAO learning lab: explore, decide, reuse",
      "intro": "Make four decisions about one research object. See the connections, check your reasoning, and pull a conceptual package apart in an optional 3D view.",
      "sources": [
        {
          "label": "VAO Standard 0.5.0 · immutable release",
          "href": "https://doi.org/10.5281/zenodo.22214248",
          "detail": "Specification, schemas, reference tools and fixtures. Use this exact standard version for the exercises."
        },
        {
          "label": "MODAVIS Ontology Network 0.1.0 · immutable release",
          "href": "https://doi.org/10.5281/zenodo.22126086",
          "detail": "Terms, governed vocabularies, versioned shapes and interpretation guide."
        },
        {
          "label": "Cuntz Positiv · content release 0.5.0-rc.2",
          "href": "https://doi.org/10.5281/zenodo.22151203",
          "detail": "The real observation and model used for the Cuntz examples. Its content version differs from VAO formatVersion 0.5.0."
        }
      ],
      "blocks": [
        {
          "type": "links",
          "items": [
            {
              "label": "Continue with the interactive workbench",
              "href": "/notebooks/vao/workbench/",
              "detail": "Edit, run real validation, repair and download."
            }
          ]
        },
        {
          "type": "lab",
          "id": "vao-learning-lab",
          "title": "From a file to a reusable research object",
          "intro": "Work at your own pace. Each short lesson links back to the full notebook explanation. You can revisit any answer, save your learning notes and continue later on this device.",
          "mode": "package",
          "lessons": [
            {
              "id": "versions",
              "label": "Identity",
              "title": "Two versions, two different jobs",
              "text": "VAO formatVersion names the exchange contract. The instrument’s content version names one published object release. Cuntz uses formatVersion 0.5.0 while its released content is labelled 0.5.0-rc.2. Keep both: a similar-looking string is not a reason to rewrite the format version.",
              "visual": {
                "layout": "compare",
                "title": "Read each version in its proper place",
                "nodes": [
                  {
                    "label": "Standard",
                    "value": "VAO 0.5.0",
                    "detail": "The rules for reading and checking the object.",
                    "icon": "book"
                  },
                  {
                    "label": "Cuntz content",
                    "value": "0.5.0-rc.2",
                    "detail": "The particular dataset release used here.",
                    "icon": "cube"
                  }
                ],
                "caption": "The dataset release label does not make the finalized exchange contract a release candidate."
              },
              "question": "Which formatVersion should describe this released Cuntz object?",
              "options": [
                {
                  "id": "format",
                  "label": "0.5.0 — the exchange contract",
                  "feedback": "Yes. Retain 0.5.0-rc.2 separately as the object content version.",
                  "correct": true
                },
                {
                  "id": "content",
                  "label": "0.5.0-rc.2 — copied from the dataset label",
                  "feedback": "That names the dataset content release, not its declared formatVersion.",
                  "correct": false
                },
                {
                  "id": "latest",
                  "label": "Whatever version the viewing software uses",
                  "feedback": "A client version cannot silently change the format contract of an existing release.",
                  "correct": false
                }
              ],
              "next": {
                "label": "Read about release and format identity",
                "href": "/notebooks/vao/structure/#carrier-roles",
                "detail": ""
              }
            },
            {
              "id": "realizations",
              "label": "Exact files",
              "title": "A light preview is a new realization",
              "text": "The website’s light Cuntz GLB is derived from its more detailed display model. Its size and digest differ. It can serve the same visual research subject without being the exact file the detailed realization identifies. Preserve the source relationship and distinguish the files.",
              "visual": {
                "layout": "flow",
                "title": "One role can have more than one encoding",
                "nodes": [
                  {
                    "label": "Logical asset",
                    "value": "The model as a resource",
                    "detail": "Its intellectual role and subject are identified.",
                    "icon": "cube"
                  },
                  {
                    "label": "Realization",
                    "value": "One exact GLB",
                    "detail": "A particular byte sequence and digest.",
                    "icon": "database"
                  },
                  {
                    "label": "Distribution",
                    "value": "A way to acquire it",
                    "detail": "A location must resolve to the promised bytes.",
                    "icon": "external"
                  }
                ],
                "caption": "Changing an encoding changes realization identity even when it serves the same logical asset.",
                "relations": [
                  "has an exact encoding",
                  "is available through"
                ]
              },
              "question": "You simplify a GLB. What should happen to its exact-byte identity?",
              "options": [
                {
                  "id": "new",
                  "label": "Describe the derivative with its own size and SHA-256",
                  "feedback": "Correct. Keep the derivation relationship and applicable attribution; a new byte sequence has a new realization identity.",
                  "correct": true
                },
                {
                  "id": "reuse",
                  "label": "Keep the original digest because the subject is the same",
                  "feedback": "The subject can stay the same while the bytes change. The original digest would fail an integrity check.",
                  "correct": false
                },
                {
                  "id": "rename",
                  "label": "Only change its filename",
                  "feedback": "A new filename does not establish the new file’s exact identity or record how it was derived.",
                  "correct": false
                }
              ],
              "next": {
                "label": "Follow the actual Cuntz model derivation",
                "href": "/notebooks/vao/model-study/#cuntz-provenance",
                "detail": ""
              }
            },
            {
              "id": "closure",
              "label": "Delivery",
              "title": "Choose what a task needs, then follow the dependencies",
              "text": "A bootstrap carrier gives you an entry point. A preservation-closure carrier contains every realization and completes every group. A custom carrier can hold a local selection. For a task, select declared groups and recursively include their dependencies; do not infer completeness from a successful preview.",
              "visual": {
                "layout": "flow",
                "title": "A usable selection includes its dependencies",
                "nodes": [
                  {
                    "label": "Requested group",
                    "value": "Your intended task",
                    "detail": "Choose a declared group, not a guessed filename.",
                    "icon": "compass"
                  },
                  {
                    "label": "Dependencies",
                    "value": "Required supporting groups",
                    "detail": "Follow dependsOnGroupIds recursively.",
                    "icon": "network"
                  },
                  {
                    "label": "Complete selection",
                    "value": "Verified realizations",
                    "detail": "All required exact members are available.",
                    "icon": "check"
                  }
                ],
                "caption": "This is a general closure illustration. It does not invent missing groups in the Cuntz manifest.",
                "relations": [
                  "follow the dependency links",
                  "verify the resulting set"
                ]
              },
              "question": "A bootstrap opens and its model displays. What have you established?",
              "options": [
                {
                  "id": "task",
                  "label": "This available representation can be inspected",
                  "feedback": "Exactly. Full preservation closure and other capabilities still need their own checks.",
                  "correct": true
                },
                {
                  "id": "whole",
                  "label": "The complete release has been preserved locally",
                  "feedback": "A working entry point does not show that every realization and dependency is present.",
                  "correct": false
                },
                {
                  "id": "audio",
                  "label": "The instrument is ready for acoustic playback",
                  "feedback": "Visual geometry does not establish the data or runtime support required for playback.",
                  "correct": false
                }
              ],
              "next": {
                "label": "Read the carrier and receipt workflow",
                "href": "/notebooks/vao/delivery/",
                "detail": ""
              }
            },
            {
              "id": "validation",
              "label": "Review",
              "title": "A passed validator tells you what it checked",
              "text": "Validation checks the declared contract: structure, relationships, profiles and exact-byte integrity, with further layers when claimed. Research review asks whether the evidence supports a historical or acoustic conclusion. The released Cuntz timestamp qualification is a useful reminder: a valid date can still be a workbook modification time.",
              "visual": {
                "layout": "flow",
                "title": "A useful result states its scope",
                "nodes": [
                  {
                    "label": "Contract",
                    "value": "Version + profiles",
                    "detail": "Identify which requirements were checked.",
                    "icon": "book"
                  },
                  {
                    "label": "Technical checks",
                    "value": "Recorded outcomes",
                    "detail": "Parsing, relationships, fixity and other claimed layers.",
                    "icon": "check"
                  },
                  {
                    "label": "Research judgment",
                    "value": "Evidence & interpretation",
                    "detail": "Review what the result can support.",
                    "icon": "quote"
                  }
                ],
                "caption": "Technical validation and scientific review answer different questions.",
                "relations": [
                  "run the relevant checks",
                  "interpret their limits"
                ]
              },
              "question": "A file validates. Can you treat its timestamp as a verified measurement-session date?",
              "options": [
                {
                  "id": "scope",
                  "label": "Only if the source evidence supports that interpretation",
                  "feedback": "Yes. Conformance does not erase the released qualification or invent a session date.",
                  "correct": true
                },
                {
                  "id": "valid",
                  "label": "Yes, because its date field is structurally valid",
                  "feedback": "A valid date value does not establish what event it dates.",
                  "correct": false
                },
                {
                  "id": "drop",
                  "label": "Remove the qualification to make the record simpler",
                  "feedback": "Keep it. The qualification is part of what makes the observation reusable and interpretable.",
                  "correct": false
                }
              ],
              "next": {
                "label": "Use the release-readiness checklist",
                "href": "/notebooks/standards/reuse-checklist/",
                "detail": ""
              }
            }
          ]
        },
        {
          "type": "heading",
          "id": "apply-package-learning",
          "text": "Turn the practice into your own next step"
        },
        {
          "type": "visual",
          "visual": {
            "layout": "flow",
            "title": "Your first successful reuse loop",
            "nodes": [
              {
                "label": "Start small",
                "value": "A known-good fixture",
                "detail": "Use the versioned release and an isolated working copy.",
                "icon": "book"
              },
              {
                "label": "Inspect & validate",
                "value": "Understand the report",
                "detail": "Trace a resource to the bytes and check its contract.",
                "icon": "search"
              },
              {
                "label": "Adapt deliberately",
                "value": "Your research object",
                "detail": "Replace identities, sources and capabilities as a coherent new release.",
                "icon": "compass"
              }
            ],
            "caption": "A successful practice carrier gives you a working method. Your actual publication still needs its own sources, rights, identifiers and review.",
            "relations": [
              "learn what the fields do",
              "carry the method forward"
            ]
          }
        },
        {
          "type": "p",
          "text": "Choose one resource from your own project. Write down its subject, whether it was captured or derived, the source it depends on, the exact file you will use, and the rights that travel with it. Then identify the smallest capability your initial carrier must support. This gives you a focused first release instead of an unnecessarily large application."
        },
        {
          "type": "example",
          "id": "cuntz-carriers",
          "title": "Why does the Cuntz release offer two VAO downloads?",
          "concept": "A manifest describes the research object and its resource relationships. A carrier is a package that delivers some or all of those exact resources.",
          "scenario": "The published Cuntz record offers a bootstrap carrier and a preservation carrier. The release states that both carry the same manifest; the preservation carrier includes every declared realization.",
          "steps": [
            {
              "title": "Begin with the inventory",
              "text": "The bootstrap supplies the semantic inventory and core evidence. It lets a reader discover what exists without first downloading all the media."
            },
            {
              "title": "Request the required material",
              "text": "A geometry inspection needs the selected model and its dependencies. A playable experience may need audio, control mappings and other groups. Reading metadata does not make those resources locally available."
            },
            {
              "title": "Choose preservation deliberately",
              "text": "The complete preservation carrier supports the full declared realization inventory. Cite the exact release and record which carrier or selected closure you actually acquired."
            }
          ],
          "takeaway": "One research release can have several delivery packages without becoming several historical interpretations.",
          "boundary": "A downloaded bootstrap does not prove that every external resource has been fetched or verified.",
          "sources": [
            {
              "label": "Cuntz Positiv · VAO 0.5.0-rc.2",
              "href": "https://doi.org/10.5281/zenodo.22151203",
              "detail": "Published manifest: identities, measurement observations, realization digests, profiles and rights. Exact examples checked against this release."
            },
            {
              "label": "VAO Standard 0.5.0",
              "href": "https://doi.org/10.5281/zenodo.22214248",
              "detail": "The standard contract is separate from the Cuntz dataset content version 0.5.0-rc.2."
            }
          ],
          "visual": {
            "layout": "compare",
            "title": "A small entry point and a full preservation copy",
            "nodes": [
              {
                "label": "Bootstrap",
                "value": "Discover & select",
                "detail": "Carries entry-point resources and pinned references.",
                "icon": "book"
              },
              {
                "label": "Preservation closure",
                "value": "Keep every realization",
                "detail": "Completes the release’s groups and dependencies.",
                "icon": "database"
              }
            ],
            "caption": "These delivery roles can carry the same semantic release. Small does not mean complete."
          },
          "expanded": false
        },
        {
          "type": "links",
          "items": [
            {
              "label": "Make a real practice carrier",
              "href": "/notebooks/vao/reuse/",
              "detail": "Run the validated starter-fixture workflow."
            },
            {
              "label": "Inspect the actual instrument model",
              "href": "/notebooks/vao/model-study/",
              "detail": "A separate, attributed Cuntz model viewer with its source and limitations."
            },
            {
              "label": "Learn the ontology relationships",
              "href": "/notebooks/ontologies/graph-lab/",
              "detail": "Practice identity, evidence, context and structural validation."
            }
          ]
        }
      ],
      "overview": {
        "summary": "A manifest describes the research object and its resource relationships. A carrier is a package that delivers some or all of those exact resources.",
        "takeaway": "One research release can have several delivery packages without becoming several historical interpretations.",
        "example": {
          "label": "See the worked example",
          "href": "#cuntz-carriers",
          "detail": ""
        }
      }
    },
    "glossary": [
      {
        "term": "Carrier",
        "definition": "A package or workspace that contains a manifest, carrier mapping and selected realizations. Bootstrap, preservation-closure and custom carriers serve different delivery purposes.",
        "example": {
          "label": "Work through the Cuntz example",
          "href": "/notebooks/standards/cuntz/#cuntz-carriers",
          "detail": ""
        }
      }
    ],
    "figures": {}
  }
}