{
  "repository": "TakashiSasaki/templates",
  "schema_version": 1,
  "terms": [
    {
      "aliases": [],
      "authority": {
        "kind": "upstream",
        "sources": [
          {
            "title": "Git glossary",
            "url": "https://git-scm.com/docs/gitglossary"
          }
        ]
      },
      "id": "external-git-branch",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "ブランチ"
        }
      },
      "origin": "external",
      "provider": "integration",
      "repository_usage": "The repository uses separate primary branches for site, composition, and policy responsibilities.",
      "source_path": "docs/glossary.yml",
      "source_revision": "12590dcf711e83ce4853409fdd8e40eb9023427f",
      "summary": "A named line of development represented through Git references.",
      "term": "Branch"
    },
    {
      "aliases": [
        "MCP"
      ],
      "authority": {
        "kind": "normative",
        "sources": [
          {
            "title": "Model Context Protocol Specification",
            "url": "https://modelcontextprotocol.io/specification/2026-07-28",
            "version": "2026-07-28"
          }
        ]
      },
      "id": "external-mcp-model-context-protocol",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "モデルコンテキストプロトコル"
        }
      },
      "origin": "external",
      "provider": "composition",
      "related_terms": [
        "templates-composition-capability-component"
      ],
      "repository_usage": "capability.mcp uses MCP 2026-07-28 as the initial core protocol baseline, while optional extensions such as MCP Apps remain separately selected composition capabilities.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "summary": "An open protocol that standardizes how LLM applications connect to external context sources, tools, and capabilities through host, client, and server roles.",
      "term": "Model Context Protocol"
    },
    {
      "aliases": [],
      "definition": "A requirement whose meaning depends on a particular agent, platform, protocol, command surface, renderer, or output format. It adapts or presents semantics instead of defining application-independent shared policy.",
      "id": "templates-adapter-renderer-requirement",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "アダプター／レンダラー要件"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-renderer",
        "templates-artifact-contract"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Adapter/renderer requirement"
    },
    {
      "aliases": [],
      "definition": "A requirement class that defines what a produced Skill, Web application, CLI, library, service, or other artifact must contain or do. Artifact contracts belong to the produced artifact rather than to shared coding-agent operating policy.",
      "id": "templates-artifact-contract",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "アーティファクト契約"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-adapter-renderer-requirement",
        "templates-explanatory-material"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Artifact contract"
    },
    {
      "aliases": [],
      "definition": "A composition component that defines the identity-specific semantics of the produced artifact, such as an Agent Skill, Website, or Web application, while reusable capabilities and lifecycle concerns remain separate authorities.",
      "id": "templates-composition-artifact-component",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "アーティファクトコンポーネント"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-component",
        "templates-artifact-contract"
      ],
      "repository_usage": "Website and Web application are sibling artifact identities in the current production catalog. Both may require the shared foundation.web baseline, but content/document orientation versus interactive application tasks determines artifact identity rather than static/dynamic rendering, runtime, or PWA selection.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Artifact component"
    },
    {
      "aliases": [],
      "definition": "An artifact-neutral composition component that adds an optional product capability such as an implementation runtime, packaged CLI, MCP interface, MCP Apps extension, standalone browser interface, or headless service.",
      "id": "templates-composition-capability-component",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "ケイパビリティコンポーネント"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-component",
        "templates-implementation-runtime",
        "templates-runtime-decision-record",
        "external-mcp-model-context-protocol"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Capability component"
    },
    {
      "aliases": [],
      "definition": "A closed reusable source authority with a component role: foundation, artifact, capability, lifecycle, topology, or workspace. Its descriptor declares dependencies, conflicts, materialized files, ownership modes, and any contract registrations used by deterministic composition.",
      "id": "templates-composition-component",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "コンポジションコンポーネント"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-component-role",
        "templates-composition-foundation-component",
        "templates-composition-artifact-component",
        "templates-composition-capability-component",
        "templates-composition-lifecycle-component",
        "templates-composition-topology-component",
        "templates-composition-workspace-component",
        "templates-composition-recipe"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Composition component"
    },
    {
      "aliases": [],
      "definition": "The single resolved Composition component recorded as the owner of a materialized destination. It identifies which component claims that destination and is independent of the destination's ownership mode; owner transitions are never inferred automatically.",
      "id": "templates-composition-component-owner",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "コンポーネント所有者"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-component",
        "templates-composition-material-ownership",
        "templates-composition-ownership-mode",
        "templates-composition-lock"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Component owner"
    },
    {
      "aliases": [],
      "definition": "The machine-readable role assigned to every Composition component. It explains whether the component supplies a shared required base (foundation), defines what is being built (artifact), adds an optional observable behavior (capability), manages the artifact over time (lifecycle), establishes repository authority, history, and projection structure (topology), or defines local checkout materialization (workspace).",
      "id": "templates-composition-component-role",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "コンポーネントロール"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-component",
        "templates-composition-foundation-component",
        "templates-composition-artifact-component",
        "templates-composition-capability-component",
        "templates-composition-lifecycle-component",
        "templates-composition-topology-component",
        "templates-composition-workspace-component"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Component role"
    },
    {
      "aliases": [],
      "definition": "The positive integer compatibility boundary declared by a Composition component descriptor. A managed update cannot cross a version change, while an explicit upgrade may; same-version descriptor drift is rejected as an invariant violation.",
      "id": "templates-composition-component-version",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "コンポジションコンポーネントバージョン"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-component",
        "templates-composition-update-operation",
        "templates-composition-upgrade-operation"
      ],
      "repository_usage": "A Composition component version is not Semantic Versioning and does not encode major/minor/patch significance.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Composition component version"
    },
    {
      "aliases": [],
      "definition": "A product or artifact repository that consumes Composition recipes/components and may carry Composition-managed state, materialized contracts, or consumer-owned seed content. It is the target of Composer operations rather than the Composition source-authority repository itself.",
      "id": "templates-composition-consumer-repository",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "コンポジション利用リポジトリ"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-recipe",
        "templates-composition-lock",
        "templates-composition-initial-operation",
        "templates-composition-update-operation",
        "templates-composition-upgrade-operation"
      ],
      "repository_usage": "Consumer refers to the repository or its maintainer consuming Composition, not to an application end user or customer.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Composition consumer repository"
    },
    {
      "aliases": [],
      "definition": "A shared mandatory baseline introduced through an artifact component dependency. Foundations are not consumer-selectable product capabilities and cannot be directly included by a recipe.",
      "id": "templates-composition-foundation-component",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "基盤コンポーネント"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-component-role",
        "templates-composition-artifact-component",
        "templates-composition-recipe"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Foundation component"
    },
    {
      "aliases": [],
      "definition": "Materialized content produced deterministically by an allowlisted declarative generator from resolved composition authorities rather than copied from one source file. Its bytes remain composition-managed and digest-bound in the lock.",
      "id": "templates-composition-generated-material",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "生成マテリアル"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-lock",
        "templates-composition-material-ownership",
        "templates-composition-ownership-mode",
        "templates-composition-managed-material",
        "templates-composition-seed-material",
        "templates-contract-manifest"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Generated material"
    },
    {
      "aliases": [],
      "definition": "The first Composer materialization of a not-yet-managed consumer repository from explicit consumer configuration. It requires no existing Composition lock, refuses unsafe destination replacement, and writes the lock last to establish managed Composition state.",
      "id": "templates-composition-initial-operation",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "初回コンポジション"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-consumer-repository",
        "templates-composition-lock",
        "templates-composition-update-operation",
        "templates-composition-upgrade-operation"
      ],
      "repository_usage": "Initial composition is one explicit Composer operation mode; it is not a generic project initialization step.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Initial composition"
    },
    {
      "aliases": [],
      "definition": "A content-addressed Composition lifecycle record that preserves validated planning or product contract state, parent/sequence linkage, and selected validation snapshots so later transitions can be checked against the recorded baseline.",
      "id": "templates-composition-lifecycle-checkpoint",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "ライフサイクルチェックポイント"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-planning-mode",
        "templates-webapp-product-mode",
        "templates-composition-lifecycle-component"
      ],
      "repository_usage": "The local checkpoint hash chain is not a trusted timestamp or external attestation and cannot by itself prove real-world chronology against wholesale history replacement.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Lifecycle checkpoint"
    },
    {
      "aliases": [],
      "definition": "An artifact-neutral composition component that adds product lifecycle machinery such as resolved-state validation, contract evolution, implementation evidence, release evidence, or release handoff.",
      "id": "templates-composition-lifecycle-component",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "ライフサイクルコンポーネント"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-component",
        "templates-contract-manifest",
        "templates-implementation-evidence",
        "templates-release-evidence",
        "templates-release-bundle"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Lifecycle component"
    },
    {
      "aliases": [],
      "definition": "The deterministic .template-composition/lock.json resolved-state record written last by the composer. It binds the exact composition source revision, configuration bytes, resolved components, descriptor digests, material destinations, owners, ownership modes, and materialized-byte digests.",
      "id": "templates-composition-lock",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "コンポジションロック"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-recipe",
        "templates-composition-material-ownership",
        "templates-composition-component-owner",
        "templates-composition-ownership-mode",
        "templates-composition-managed-material",
        "templates-composition-seed-material",
        "templates-composition-generated-material"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Composition lock"
    },
    {
      "aliases": [],
      "definition": "Materialized content whose composition source remains authoritative after initial application. Consumer-time validation requires its current bytes to continue matching the composition lock digest.",
      "id": "templates-composition-managed-material",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "管理対象マテリアル"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-lock",
        "templates-composition-material-ownership",
        "templates-composition-ownership-mode",
        "templates-composition-seed-material",
        "templates-composition-generated-material"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Managed material"
    },
    {
      "aliases": [],
      "definition": "The Composition rule that assigns every materialized destination exactly one component owner and one ownership mode. The owner identifies which resolved component claims the destination, while the mode determines whether Composition retains authority over its bytes or transfers content ownership to the consumer.",
      "id": "templates-composition-material-ownership",
      "localized_labels": {
        "ja": {
          "aliases": [
            "マテリアルオーナーシップ"
          ],
          "term": "マテリアル所有権"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-component-owner",
        "templates-composition-ownership-mode",
        "templates-composition-lock"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Material ownership"
    },
    {
      "aliases": [
        "ownership modes"
      ],
      "definition": "The per-destination lifecycle classification recorded as managed, generated, or seed in the Composition lock. It determines byte authority after materialization: managed and generated content remain Composition-controlled, while seed content transfers to the consumer.",
      "id": "templates-composition-ownership-mode",
      "localized_labels": {
        "ja": {
          "aliases": [
            "所有モード"
          ],
          "term": "オーナーシップモード"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-material-ownership",
        "templates-composition-managed-material",
        "templates-composition-seed-material",
        "templates-composition-generated-material",
        "templates-composition-lock"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Ownership mode"
    },
    {
      "aliases": [],
      "definition": "The narrow Composition lifecycle state used after explicit product requirements and their intended machine-contract targets are known but before concrete implementation-evidence records exist. Planning mode keeps implementation records and release execution claims incomplete while preserving stable requirement identity and required proof kinds.",
      "id": "templates-composition-planning-mode",
      "localized_labels": {
        "ja": {
          "aliases": [
            "計画モード"
          ],
          "term": "プランニングモード"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-webapp-template-mode",
        "templates-webapp-product-mode",
        "templates-implementation-evidence",
        "templates-composition-release-readiness"
      ],
      "repository_usage": "Planning mode is a contract state, not a synonym for the whole project-planning phase.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Planning mode"
    },
    {
      "aliases": [],
      "definition": "A consumer-facing artifact recipe that selects exactly one artifact component and defines which reusable capability or lifecycle components are required, defaulted, or available for explicit selection.",
      "id": "templates-composition-recipe",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "コンポジションレシピ"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-component",
        "templates-composition-lock"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Composition recipe"
    },
    {
      "aliases": [],
      "definition": "The implementation-evidence lifecycle decision that a product-mode evidence graph is ready for release production: required targets and requirements are covered and every proof required by the selected release gates is verified rather than deferred or missing.",
      "id": "templates-composition-release-readiness",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "コンポジション・リリース準備完了性"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-implementation-evidence",
        "templates-webapp-product-mode",
        "templates-webapp-candidate-revision",
        "templates-release-evidence"
      ],
      "repository_usage": "Passing Composition release readiness permits the Composition release producer to proceed; it does not by itself prove packaging, signing, deployment, external artifact identity, or post-deployment success.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Composition release readiness"
    },
    {
      "aliases": [],
      "definition": "Materialized initial content whose ownership transfers to the consumer repository after composition. The file must remain present, but consumer edits are allowed to diverge from the initial lock digest.",
      "id": "templates-composition-seed-material",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "シードマテリアル"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-lock",
        "templates-composition-material-ownership",
        "templates-composition-ownership-mode",
        "templates-composition-managed-material",
        "templates-composition-generated-material"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Seed material"
    },
    {
      "aliases": [
        "Topology component"
      ],
      "definition": "An artifact-neutral composition component that declares and materializes repository authority, history, and projection structure (such as Hub-and-Orphan) rather than artifact identity, capability, or lifecycle behavior.",
      "id": "templates-composition-topology-component",
      "localized_labels": {
        "ja": {
          "aliases": [
            "トポロジコンポーネント"
          ],
          "term": "リポジトリトポロジコンポーネント"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-component",
        "templates-composition-component-role",
        "templates-composition-recipe"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Repository topology component"
    },
    {
      "aliases": [],
      "definition": "A managed Composer reconciliation that preserves the normalized consumer intent already recorded in lock schema version 2 while reconciling that intent against the current descendant Composition source revision.",
      "id": "templates-composition-update-operation",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "コンポジション更新"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-consumer-repository",
        "templates-composition-lock",
        "templates-composition-upgrade-operation",
        "templates-composition-component-version"
      ],
      "repository_usage": "Update does not accept replacement configuration and cannot cross a Composition component-version compatibility boundary; the size of the source change does not determine whether an operation is an update.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Composition update"
    },
    {
      "aliases": [],
      "definition": "A managed Composer reconciliation that consumes explicit replacement consumer configuration and may change recipe selection, includes/excludes, component parameters, or cross a declared Composition component-version compatibility boundary.",
      "id": "templates-composition-upgrade-operation",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "コンポジションアップグレード"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-consumer-repository",
        "templates-composition-lock",
        "templates-composition-update-operation",
        "templates-composition-component-version"
      ],
      "repository_usage": "Upgrade means explicit replacement intent or a compatibility-boundary crossing in Composer semantics; it is not defined merely by a source change being large or major.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Composition upgrade"
    },
    {
      "aliases": [],
      "definition": "An artifact-neutral Composition component that declares local-checkout and workspace materialization semantics independently from repository authority, history, and projection topology.",
      "id": "templates-composition-workspace-component",
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-component",
        "templates-composition-topology-component"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Workspace component"
    },
    {
      "aliases": [],
      "definition": "Artifact- and engine-independent policy content selected only for a particular operational context, such as pull-request review or external artifact intake. It is policy content, not the Policy context selector: a Policy context is the named semantic authority boundary that selects profiles, repository-local policy, and overrides; each output separately references both a context and a renderer.",
      "id": "templates-context-policy",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "コンテキストポリシー"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-context",
        "templates-shared-policy"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Context policy"
    },
    {
      "aliases": [],
      "definition": "The deterministic generated contracts/manifest.json registry built from contract registrations in the resolved component closure. It identifies active contract documents, schemas, purposes, version histories, and migrations without being a handwritten source file.",
      "id": "templates-contract-manifest",
      "localized_labels": {
        "ja": {
          "aliases": [
            "契約マニフェスト"
          ],
          "term": "コントラクトマニフェスト"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-generated-material",
        "templates-composition-lifecycle-component",
        "templates-release-bundle"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Contract manifest"
    },
    {
      "aliases": [],
      "definition": "Rationale, examples, history, proposals, and other non-normative text that explains policy or artifact decisions without itself establishing a normative policy rule or artifact contract.",
      "id": "templates-explanatory-material",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "説明資料"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-artifact-contract"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Explanatory material"
    },
    {
      "aliases": [],
      "definition": "An artifact-neutral lifecycle contract that maps artifact-defined contract targets to repository-local implementation boundaries, positive and negative proofs, authoritative command definitions, and release gates. It defines what must be proved and run but does not record candidate execution itself.",
      "id": "templates-implementation-evidence",
      "localized_labels": {
        "ja": {
          "aliases": [
            "実装証跡"
          ],
          "term": "実装エビデンス"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-release-evidence",
        "templates-artifact-contract",
        "templates-composition-lifecycle-component"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Implementation evidence"
    },
    {
      "aliases": [],
      "definition": "The implementation ecosystem and operational choices used to build and run a composed artifact, including its language/runtime, runtime version, dependency and package workflow, exact commands, environment, distribution, and deployment.",
      "id": "templates-implementation-runtime",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "実装ランタイム"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-capability-component",
        "templates-runtime-decision-record"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Implementation runtime"
    },
    {
      "aliases": [],
      "definition": "The bounded Integration-generated guided-navigation graph v2 of Provider-branch-owned index.md navigation metadata from exact reviewed Provider branch revisions. Its provider discovery root is the authority root index.md; each reachable index retains its source blob identity. It preserves Provider branch grouping, order, labels, and descriptions without turning provider indexes into a publication catalog or replacing Integration-owned reader navigation. Site may render this schema-versioned machine-readable graph at /guided/.",
      "id": "templates-index-guided-navigation",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "インデックス誘導ナビゲーション"
        }
      },
      "origin": "repository",
      "provider": "integration",
      "related_terms": [
        "templates-integrated-publication",
        "templates-provider-branch",
        "templates-publication-catalog",
        "templates-publication-source-lock"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "12590dcf711e83ce4853409fdd8e40eb9023427f",
      "term": "Index-guided navigation"
    },
    {
      "aliases": [],
      "definition": "The Integration-owned publication model assembled from reviewed exact revisions of independently owned Provider branch histories without merging those histories or transferring ownership of their canonical content.",
      "id": "templates-integrated-publication",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "統合公開"
        }
      },
      "origin": "repository",
      "provider": "integration",
      "related_terms": [
        "templates-provider-branch",
        "templates-publication-catalog",
        "templates-publication-source-lock"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "12590dcf711e83ce4853409fdd8e40eb9023427f",
      "term": "Integrated publication"
    },
    {
      "aliases": [],
      "definition": "The user-facing first-time onboarding operation that inspects an unmanaged repository and derives either fresh adoption or migration adoption from repository state before any supported mutation. Installing the agent-policy skill provides the entry point but does not itself adopt the target repository.",
      "id": "templates-policy-adoption",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "Policy 導入"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-bootstrap-trust-seed",
        "templates-policy-fresh-adoption",
        "templates-policy-migration-adoption",
        "templates-policy-managed-repository"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Policy adoption"
    },
    {
      "aliases": [],
      "definition": "The trust-seed role of the installable skills/agent-policy package when it is used to onboard an unmanaged repository. Its runtime manifest selects one reviewed immutable Policy toolchain revision, binds that revision's runtime dependency lock by SHA-256, and exposes a closed bootstrap route set with no migration-finalization route. After adoption, the same skill follows the managed repository's .agent-policy.lock instead of switching to a separate bootstrap package.",
      "id": "templates-policy-bootstrap-trust-seed",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "ブートストラップ信頼シード"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-stable-release-descriptor",
        "templates-policy-promoted-toolchain-revision",
        "templates-policy-managed-repository",
        "templates-policy-adoption"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Bootstrap trust seed"
    },
    {
      "aliases": [],
      "definition": "The read-only managed-repository operation that verifies the current configuration, semantic inputs, .agent-policy.lock, and generated outputs agree. It detects missed regeneration and manual changes to generated outputs but does not regenerate them.",
      "id": "templates-policy-check-operation",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "Policy 整合性チェック"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-managed-repository",
        "templates-policy-render-operation",
        "templates-policy-validate-operation"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Policy check"
    },
    {
      "aliases": [],
      "definition": "A named semantic authority boundary in agent-policy configuration that selects shared policy profiles, repository-local policy files, and any explicit overrides. Outputs reference a context rather than selecting policy semantics independently.",
      "id": "templates-policy-context",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "ポリシーコンテキスト"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-profile",
        "templates-policy-renderer",
        "templates-context-policy",
        "templates-repository-local-policy",
        "templates-policy-override"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Policy context"
    },
    {
      "aliases": [],
      "definition": "The Policy adoption strategy selected for an unmanaged-empty repository, where no handwritten primary agent instructions require migration. When explicitly applied it may use the hidden init primitive internally and can create normal managed state directly without a staged adoption-state transaction.",
      "id": "templates-policy-fresh-adoption",
      "localized_labels": {
        "ja": {
          "aliases": [
            "フレッシュ導入"
          ],
          "term": "新規導入"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-adoption",
        "templates-policy-migration-adoption",
        "templates-policy-managed-repository"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Fresh adoption"
    },
    {
      "aliases": [],
      "definition": "A product repository that Policy onboarding inspection classifies as managed because the canonical .agent-policy.yml path resolves to an existing regular file. Managed repositories use normal validate, render, and check operations through the same installed agent-policy skill, whose runtime selection follows .agent-policy.lock. The classification itself does not assert that configuration semantics have already passed those validations, and partial or conflicting generated state is classified separately as inconsistent.",
      "id": "templates-policy-managed-repository",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "管理対象リポジトリ"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-profile",
        "templates-policy-context",
        "templates-repository-local-policy",
        "templates-policy-bootstrap-trust-seed",
        "templates-policy-adoption",
        "templates-policy-render-operation",
        "templates-policy-validate-operation",
        "templates-policy-check-operation"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Managed repository"
    },
    {
      "aliases": [],
      "definition": "The Policy adoption strategy selected for an unmanaged-existing repository. Existing instructions remain authoritative while preparation records protected sources and generates a non-conflicting preview; a later explicit finalize --apply transaction performs cutover only after semantic review.",
      "id": "templates-policy-migration-adoption",
      "localized_labels": {
        "ja": {
          "aliases": [
            "マイグレーション導入"
          ],
          "term": "移行導入"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-adoption",
        "templates-policy-fresh-adoption",
        "templates-policy-managed-repository"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Migration adoption"
    },
    {
      "aliases": [],
      "definition": "A shared-policy source file that owns one independently applicable normative rule and one stable rule ID, with metadata such as severity, override permission, and deterministic order plus optional rationale and examples.",
      "id": "templates-policy-module",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "ポリシーモジュール"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Policy module"
    },
    {
      "aliases": [],
      "definition": "The mechanism by which a repository-local rule intentionally replaces an overridable shared rule with the same stable rule ID. The containing policy context must record that exception in an explicit override declaration with a non-empty reason, while the repository-local policy file remains the source of the replacement rule body.",
      "id": "templates-policy-override",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "ポリシーオーバーライド"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-context",
        "templates-shared-policy",
        "templates-repository-local-policy"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Policy override"
    },
    {
      "aliases": [],
      "definition": "A named ordered selection of shared policy modules that can be selected by a managed repository or policy context as part of its semantic policy input.",
      "id": "templates-policy-profile",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "ポリシープロファイル"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-module",
        "templates-skill-profile"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Policy profile"
    },
    {
      "aliases": [],
      "definition": "The reviewed candidate full commit SHA selected by Policy promotion and written into both the stable release descriptor and the single-skill runtime manifest. It is a strict ancestor of the later promotion state, avoiding recursive self-reference.",
      "id": "templates-policy-promoted-toolchain-revision",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "昇格済みツールチェーンリビジョン"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-stable-release",
        "templates-policy-stable-release-descriptor",
        "templates-policy-bootstrap-trust-seed"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Promoted toolchain revision"
    },
    {
      "aliases": [],
      "definition": "The mutating managed-repository operation that composes the current accepted shared and repository-local Policy inputs and regenerates the configured outputs together with .agent-policy.lock. Generated outputs are changed through render rather than edited directly.",
      "id": "templates-policy-render-operation",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "Policy レンダー"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-managed-repository",
        "templates-policy-validate-operation",
        "templates-policy-check-operation"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Policy render"
    },
    {
      "aliases": [],
      "definition": "A presentation adapter that renders the semantic rules selected by a policy context into a caller-facing output format without selecting, adding, removing, or overriding policy rules.",
      "id": "templates-policy-renderer",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "ポリシーレンダラー"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-context",
        "templates-adapter-renderer-requirement"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Policy renderer"
    },
    {
      "aliases": [],
      "definition": "The executable Policy toolchain release currently selected by the stable release descriptor. It may intentionally lag the advancing policy branch and is identified by the promoted toolchain revision rather than by the later promotion-state commit.",
      "id": "templates-policy-stable-release",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "安定版リリース"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-stable-release-descriptor",
        "templates-policy-promoted-toolchain-revision"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Stable release"
    },
    {
      "aliases": [],
      "definition": "The committed release/toolchain.json record for the stable channel that binds the Policy toolchain repository and exact promoted revision together with synchronized contract versions and verifier requirements.",
      "id": "templates-policy-stable-release-descriptor",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "安定版リリース記述子"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-stable-release",
        "templates-policy-promoted-toolchain-revision",
        "templates-policy-bootstrap-trust-seed"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Stable release descriptor"
    },
    {
      "aliases": [],
      "definition": "The read-only Policy operation that validates .agent-policy.yml and its referenced semantic inputs, including schema shape, known profiles, policy files, rule identities, overrides, and repository path safety. A successful validation does not assert that generated outputs match the current lock and inputs.",
      "id": "templates-policy-validate-operation",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "Policy 検証"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-managed-repository",
        "templates-policy-render-operation",
        "templates-policy-check-operation"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Policy validate"
    },
    {
      "aliases": [],
      "definition": "A repository-internal primary Git branch, currently composition or policy, that owns canonical content supplied as an independently versioned input to the Integration publication model.",
      "id": "templates-provider-branch",
      "localized_labels": {
        "ja": {
          "aliases": [
            "提供ブランチ"
          ],
          "term": "プロバイダーブランチ"
        }
      },
      "origin": "repository",
      "provider": "integration",
      "related_terms": [
        "templates-publication-catalog"
      ],
      "repository_usage": "In Integration publication terminology, Provider branch refers only to these internal Git content-source branches. It does not mean a cloud provider, LLM or API provider, identity provider, or other external service provider. Integration assembles provider sources and Site renders the result; neither is a Provider branch. Policy documentation also uses Provider / toolchain layer in its own Policy-specific architecture, which is a separate use of provider terminology.",
      "source_path": "docs/glossary.yml",
      "source_revision": "12590dcf711e83ce4853409fdd8e40eb9023427f",
      "summary": "One of the repository's composition or policy content-source branches used as an input to Integration publication.",
      "term": "Provider branch"
    },
    {
      "aliases": [],
      "definition": "A declaration owned by a Provider branch that lists the canonical publication inputs Integration is permitted to integrate.",
      "id": "templates-publication-catalog",
      "localized_labels": {
        "ja": {
          "aliases": [
            "パブリケーションカタログ"
          ],
          "term": "公開カタログ"
        }
      },
      "origin": "repository",
      "provider": "integration",
      "related_terms": [
        "templates-provider-branch"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "12590dcf711e83ce4853409fdd8e40eb9023427f",
      "term": "Publication catalog"
    },
    {
      "aliases": [],
      "definition": "An Integration-owned binding in publication-sources.json from a Provider branch publication to a reviewed full 40-character commit SHA used as an immutable build input. Mutable branch names, tags, and abbreviated SHAs are not valid publication source locks.",
      "id": "templates-publication-source-lock",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "公開ソースロック"
        }
      },
      "origin": "repository",
      "provider": "integration",
      "related_terms": [
        "templates-provider-branch",
        "templates-integrated-publication"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "12590dcf711e83ce4853409fdd8e40eb9023427f",
      "term": "Publication source lock"
    },
    {
      "aliases": [],
      "definition": "An artifact-neutral deterministic handoff contract that binds an approved candidate revision to the exact current bytes of the active registered contract set transferred to the next system.",
      "id": "templates-release-bundle",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "リリースバンドル"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-contract-manifest",
        "templates-release-evidence",
        "templates-composition-lifecycle-component"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Release bundle"
    },
    {
      "aliases": [],
      "definition": "An artifact-neutral revision-specific record that binds one exact candidate revision to completed authoritative command and release-gate results, execution provenance, and the resulting release decision.",
      "id": "templates-release-evidence",
      "localized_labels": {
        "ja": {
          "aliases": [
            "リリース証跡"
          ],
          "term": "リリースエビデンス"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-implementation-evidence",
        "templates-release-bundle",
        "templates-composition-lifecycle-component"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Release evidence"
    },
    {
      "aliases": [],
      "definition": "Policy owned by a managed repository for local facts, invariants, justified extensions, or explicit permitted overrides. It supplements shared semantics instead of restating shared rules merely for convenience.",
      "id": "templates-repository-local-policy",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "リポジトリローカルポリシー"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-context",
        "templates-shared-policy",
        "templates-policy-override"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Repository-local policy"
    },
    {
      "aliases": [
        "Runtime decision record"
      ],
      "definition": "The consumer-owned RUNTIME.md decision record materialized by capability.runtime. It records the selected implementation runtime, dependency workflow, exact commands, protocol selections, environment, distribution, and deployment lifecycle without belonging specifically to Skill, Website, or Webapp semantics.",
      "id": "templates-runtime-decision-record",
      "localized_labels": {
        "ja": {
          "aliases": [
            "ランタイム決定記録"
          ],
          "term": "実装ランタイム決定記録"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-implementation-runtime",
        "templates-composition-capability-component"
      ],
      "repository_usage": "Runtime is an optional artifact-neutral capability. A Website may have a maintained server runtime and a Webapp may be statically hosted; runtime selection therefore must not be used to classify Website versus Web application product identity.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Implementation runtime decision record"
    },
    {
      "aliases": [],
      "definition": "Artifact- and engine-independent operating behavior that is generally applicable and is authored in the policy branch as canonical shared semantics rather than copied into consumer repositories as an independent handwritten authority.",
      "id": "templates-shared-policy",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "共有ポリシー"
        }
      },
      "origin": "repository",
      "provider": "policy",
      "related_terms": [
        "templates-policy-module",
        "templates-policy-profile",
        "templates-context-policy",
        "templates-repository-local-policy"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "19ae6a5c460a2bdf7a23c24dce8e7f0ec195d2f4",
      "term": "Shared policy"
    },
    {
      "aliases": [],
      "definition": "A Skill-specific resource pattern describing whether a concrete Agent Skill is instruction-only, knowledge-augmented, asset-driven, or script-assisted. Application runtime and public interfaces are composition capabilities rather than Skill profiles.",
      "id": "templates-skill-profile",
      "localized_labels": {
        "ja": {
          "aliases": [
            "Skill プロファイル"
          ],
          "term": "スキルプロファイル"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-policy-profile",
        "templates-skill-template-scaffold",
        "templates-composition-capability-component"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Skill profile"
    },
    {
      "aliases": [],
      "definition": "The uncustomized Agent Skill seed identified by the reserved template-scaffold sentinel. The sentinel is not a fifth concrete Skill profile and must be replaced before the repository is treated as an operational Skill.",
      "id": "templates-skill-template-scaffold",
      "localized_labels": {
        "ja": {
          "aliases": [
            "スキルテンプレート雛形"
          ],
          "term": "スキルテンプレート・スキャフォールド"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-skill-profile",
        "templates-composition-artifact-component"
      ],
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Skill template scaffold"
    },
    {
      "aliases": [],
      "definition": "The exact immutable product source revision named for release production, against which authoritative proofs run and to which approved release evidence and the resulting release bundle are bound.",
      "id": "templates-webapp-candidate-revision",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "候補リビジョン"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-release-evidence",
        "templates-release-bundle",
        "templates-composition-release-readiness"
      ],
      "repository_usage": "This is the product release-candidate revision in the Composition release lifecycle, not a generic pull-request candidate or Policy toolchain promotion candidate. The stable term ID predates the Composition authority migration and is retained for the surviving concept.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Candidate revision"
    },
    {
      "aliases": [],
      "definition": "A stable versioned identity for one registered contract concern, with its active or retired state, current schema version, contiguous version history, migration path, document/schema locations, and evidence relationship maintained through contract evolution.",
      "id": "templates-webapp-contract-family",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "コントラクトファミリー"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-contract-manifest",
        "templates-composition-lifecycle-component"
      ],
      "repository_usage": "The concept originated in the former Webapp authority but now applies through the artifact-neutral Composition contract-evolution lifecycle; the historical stable ID is retained because the concept itself survives.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Contract family"
    },
    {
      "aliases": [],
      "definition": "The Composition lifecycle state in which the concrete implementation and evidence graph is active: product requirements link to implementation boundaries, proofs, authoritative commands, and release gates according to the selected contracts.",
      "id": "templates-webapp-product-mode",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "プロダクトモード"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-webapp-template-mode",
        "templates-composition-planning-mode",
        "templates-implementation-evidence",
        "templates-composition-release-readiness"
      ],
      "repository_usage": "Product mode does not mean implementation complete, release ready, released, or deployed. Product-mode proofs may still be deferred or otherwise incomplete until the separate release-readiness contract passes. This stable term ID predates the Composition authority migration and is retained for the surviving concept.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Product mode"
    },
    {
      "aliases": [],
      "definition": "The Composition lifecycle state in which a selected contract carries no active product requirement or concrete implementation claim. Template mode provides scaffold/default contract structure only; it is not a claim that a repository is merely a template or that a concrete product has been validated.",
      "id": "templates-webapp-template-mode",
      "localized_labels": {
        "ja": {
          "aliases": [],
          "term": "テンプレートモード"
        }
      },
      "origin": "repository",
      "provider": "composition",
      "related_terms": [
        "templates-composition-planning-mode",
        "templates-webapp-product-mode",
        "templates-implementation-evidence"
      ],
      "repository_usage": "This stable term ID predates the Composition authority migration and is retained because the same lifecycle concept survives under the current artifact-neutral Composition model.",
      "source_path": "docs/glossary.yml",
      "source_revision": "e55d340740c21c374d2c4d29c410015c475089ec",
      "term": "Template mode"
    }
  ]
}