{
  "schema_version": "core-reviewed-term-ai-handoff-v2",
  "version": "core-reviewed-term-ai-handoff-v2",
  "compat": {
    "backward_compatible_schema_versions": [
      "core-reviewed-term-ai-handoff-v1"
    ],
    "v1_fields_preserved": true
  },
  "contract_status": "preview",
  "distribution": "per_term_read_only_ai_handoff",
  "no_write_operations": true,
  "content_tier": "db_backed",
  "canonical": {
    "url": "https://core.yogoq.com/ko-KR/core/task",
    "slug": "task",
    "locale": "ko-KR"
  },
  "summary": {
    "schema_version": "core-reviewed-term-summary-v1",
    "term_id": "36dcbf28-cc2d-5b74-ab63-2d940ca8da3e",
    "canonical_slug": "task",
    "canonical_url": "https://core.yogoq.com/ko-KR/core/task",
    "locale": "ko-KR",
    "display_name": "タスク",
    "english_name": "Task",
    "abbreviation": null,
    "short_definition": "Task clarifies an individual unit of work, aligning purpose, order, and time allocation so people can execute with a shared standard and fewer delays.",
    "content_tier": "db_backed",
    "quality": "reviewed",
    "publication_status": "published_reviewed",
    "version": "core-reviewed-term-summary-v1",
    "last_reviewed_at": "2026-05-10T00:00:00.000Z",
    "sources_count": 3,
    "limitations_key": "core-trust-policy-v1-2026-06-22"
  },
  "aliases": [
    {
      "text": "タスク",
      "type": "display_name",
      "locale": "ko-KR"
    },
    {
      "text": "Task",
      "type": "english_name",
      "locale": "en-US"
    },
    {
      "text": "タスク",
      "type": "localized_title",
      "locale": "ja-JP"
    }
  ],
  "content": {
    "definition": {
      "key": "definition",
      "title": "一言でいうと",
      "text": "Task clarifies an individual unit of work, aligning purpose, order, and time allocation so people can execute with a shared standard and fewer delays.",
      "items": []
    },
    "formula": null,
    "boundary": null,
    "usage": [
      {
        "key": "meaning",
        "title": "意味",
        "text": "Task is the concept of organizing an individual unit of work in daily work by defining purpose, scope, ownership, timing, and quality expectations. When it is clear, teams share assumptions, track progress consistently, and make faster decisions with fewer rework cycles. In practice it is maintained alongside tools and documents and updated by agreement when priorities or constraints change. It becomes a shared reference point for coordinating work across roles.",
        "items": []
      },
      {
        "key": "usage",
        "title": "役立つ場面",
        "text": "When Task is explicit, teams align on what comes first and can decide faster without backtracking. Shared criteria make it easier to detect delays early and adjust resources before impacts escalate. Clear structure reduces duplication and gaps, improving decision quality and accountability across owners.",
        "items": [
          "When Task is explicit, teams align on what comes first and can decide faster without backtracking.",
          "Shared criteria make it easier to detect delays early and adjust resources before impacts escalate.",
          "Clear structure reduces duplication and gaps, improving decision quality and accountability across owners."
        ]
      },
      {
        "key": "usage",
        "title": "使い方のポイント",
        "text": null,
        "items": [
          "State the goal and scope first, including what is intentionally excluded.",
          "List dependencies and due dates so sequencing decisions are visible.",
          "Use rough effort estimates to set realistic capacity expectations.",
          "Record the last update and the next review date to prevent drift.",
          "Assign owners so responsibility is explicit rather than implied."
        ]
      }
    ],
    "misunderstandings": [
      {
        "key": "misunderstandings",
        "title": "よくある誤解 / 落とし穴",
        "text": null,
        "items": [
          "Having a plan does not guarantee results; continuous review is still required.",
          "More detail is not always better; the right granularity depends on the context.",
          "It can be revised with agreement when conditions or priorities change."
        ]
      }
    ],
    "examples": [
      {
        "key": "examples",
        "title": "最小例",
        "text": "Example: A team preparing a product launch uses Task to organize work over four weeks. They define the scope (landing page, ad assets, FAQ), assign owners, and set deadlines. Weekly check-ins track progress and surface blockers early. If a dependency slips, they adjust priority and reallocate effort to protect the launch date, documenting changes for shared visibility.",
        "items": []
      }
    ],
    "comparisons": [
      {
        "key": "comparisons",
        "title": "似ている言葉との違い",
        "text": "Compare Task with adjacent concepts before deciding. Task | Current concept | Use when the team needs the primary decision lens Adjacent metric or framework | Supporting lens | Use when the team needs evidence or process detail General vocabulary | Broad explanation | Use only for orientation, not final decision-making",
        "items": [
          "Task | Current concept | Use when the team needs the primary decision lens",
          "Adjacent metric or framework | Supporting lens | Use when the team needs evidence or process detail",
          "General vocabulary | Broad explanation | Use only for orientation, not final decision-making"
        ]
      }
    ],
    "faq": [
      {
        "question": "When should I use Task?",
        "answer": "Use it when the team needs to decide scope, priority, owner, or trade-off, not when it only needs a short definition."
      },
      {
        "question": "What makes Task useful in practice?",
        "answer": "It becomes useful when it is tied to evidence, a decision owner, and a concrete next operating choice."
      },
      {
        "question": "What should I avoid?",
        "answer": "Avoid using the term as a label without clarifying assumptions, boundaries, and how success will be judged."
      }
    ]
  },
  "source_refs": [
    "concept:task:en-US",
    "concept:task:ja-JP",
    "core-term-page-500:concept:task"
  ],
  "sources": {
    "source_refs": [
      "concept:task:en-US",
      "concept:task:ja-JP",
      "core-term-page-500:concept:task"
    ],
    "visible_sources": [
      {
        "label": "Business Communication for Success (Open Textbook Library)",
        "url": "https://open.umn.edu/opentextbooks/textbooks/business-communication-for-success",
        "kind": null
      },
      {
        "label": "Principles of Marketing (Open Textbook Library)",
        "url": "https://open.umn.edu/opentextbooks/textbooks/principles-of-marketing",
        "kind": "tier_s"
      },
      {
        "label": "Principles of Management (OpenStax)",
        "url": "https://openstax.org/details/books/principles-management",
        "kind": "tier_s"
      }
    ]
  },
  "related_terms": [
    {
      "topic_id": "ab5bbd61-929c-5ad3-81f0-bb52b97cf120",
      "canonical_slug": "tcp-ip",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/tcp-ip",
      "title": "TCP/IP",
      "relation_type": "next"
    },
    {
      "topic_id": "90bcd3eb-e718-5ea9-a6d6-04a984db9a28",
      "canonical_slug": "target-customer",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/target-customer",
      "title": "ターゲット顧客",
      "relation_type": "used_together"
    },
    {
      "topic_id": "1427f25e-426c-5a6e-b1e8-bcf8ebfb28c2",
      "canonical_slug": "product-portfolio-management",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/product-portfolio-management",
      "title": "プロダクトポートフォリオ管理",
      "relation_type": "used_together"
    },
    {
      "topic_id": "3d77d4a4-995f-504b-8fc5-c33b5d53378d",
      "canonical_slug": "promotion",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/promotion",
      "title": "プロモーション(4P)",
      "relation_type": "used_together"
    }
  ],
  "relations": [
    {
      "term_id": "ab5bbd61-929c-5ad3-81f0-bb52b97cf120",
      "canonical_slug": "tcp-ip",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/tcp-ip",
      "display_name": "TCP/IP",
      "relation_type": "related",
      "source_relation_type": "next"
    },
    {
      "term_id": "90bcd3eb-e718-5ea9-a6d6-04a984db9a28",
      "canonical_slug": "target-customer",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/target-customer",
      "display_name": "ターゲット顧客",
      "relation_type": "related",
      "source_relation_type": "used_together"
    },
    {
      "term_id": "1427f25e-426c-5a6e-b1e8-bcf8ebfb28c2",
      "canonical_slug": "product-portfolio-management",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/product-portfolio-management",
      "display_name": "プロダクトポートフォリオ管理",
      "relation_type": "related",
      "source_relation_type": "used_together"
    },
    {
      "term_id": "3d77d4a4-995f-504b-8fc5-c33b5d53378d",
      "canonical_slug": "promotion",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/promotion",
      "display_name": "プロモーション(4P)",
      "relation_type": "related",
      "source_relation_type": "used_together"
    }
  ],
  "chunk_ids": [
    "core:chunk:task:ko-KR:definition:6e30e9df8edb2d91",
    "core:chunk:task:ko-KR:meaning:6301e57aa13d06a6",
    "core:chunk:task:ko-KR:usage:5dff152027a81d12",
    "core:chunk:task:ko-KR:usage:c66f5a406d472254",
    "core:chunk:task:ko-KR:misunderstandings:6025770ec8aa36da",
    "core:chunk:task:ko-KR:examples:4eb36e1b10abc9db",
    "core:chunk:task:ko-KR:comparisons:c8082429bf6b4c17",
    "core:chunk:task:ko-KR:faq:86bdda6b724fa9aa",
    "core:chunk:task:ko-KR:faq:9f00e368094418b9",
    "core:chunk:task:ko-KR:faq:79bb496164ef487a"
  ],
  "chunks": [
    {
      "chunk_id": "core:chunk:task:ko-KR:definition:6e30e9df8edb2d91",
      "section_key": "definition",
      "heading": "一言でいうと",
      "text": "Task clarifies an individual unit of work, aligning purpose, order, and time allocation so people can execute with a shared standard and fewer delays.",
      "source_refs": [
        "concept:task:en-US",
        "concept:task:ja-JP",
        "core-term-page-500:concept:task"
      ],
      "content_hash": "6e30e9df8edb2d91b3d3bfb917624013e641b95778c65885869492be252714c7"
    },
    {
      "chunk_id": "core:chunk:task:ko-KR:meaning:6301e57aa13d06a6",
      "section_key": "meaning",
      "heading": "意味",
      "text": "Task is the concept of organizing an individual unit of work in daily work by defining purpose, scope, ownership, timing, and quality expectations. When it is clear, teams share assumptions, track progress consistently, and make faster decisions with fewer rework cycles. In practice it is maintained alongside tools and documents and updated by agreement when priorities or constraints change. It becomes a shared reference point for coordinating work across roles.",
      "source_refs": [
        "concept:task:en-US",
        "concept:task:ja-JP",
        "core-term-page-500:concept:task"
      ],
      "content_hash": "6301e57aa13d06a6e0f79c61caa43d97580fd255606ceca9d039793ddc9a4648"
    },
    {
      "chunk_id": "core:chunk:task:ko-KR:usage:5dff152027a81d12",
      "section_key": "usage",
      "heading": "役立つ場面",
      "text": "When Task is explicit, teams align on what comes first and can decide faster without backtracking. Shared criteria make it easier to detect delays early and adjust resources before impacts escalate. Clear structure reduces duplication and gaps, improving decision quality and accountability across owners. When Task is explicit, teams align on what comes first and can decide faster without backtracking. Shared criteria make it easier to detect delays early and adjust resources before impacts escalate. Clear structure reduces duplication and gaps, improving decision quality and accountability across owners.",
      "source_refs": [
        "concept:task:en-US",
        "concept:task:ja-JP",
        "core-term-page-500:concept:task"
      ],
      "content_hash": "5dff152027a81d126b828886389f211ed57b659a156fa2d4405f53c6d83a774b"
    },
    {
      "chunk_id": "core:chunk:task:ko-KR:usage:c66f5a406d472254",
      "section_key": "usage",
      "heading": "使い方のポイント",
      "text": "State the goal and scope first, including what is intentionally excluded. List dependencies and due dates so sequencing decisions are visible. Use rough effort estimates to set realistic capacity expectations. Record the last update and the next review date to prevent drift. Assign owners so responsibility is explicit rather than implied.",
      "source_refs": [
        "concept:task:en-US",
        "concept:task:ja-JP",
        "core-term-page-500:concept:task"
      ],
      "content_hash": "c66f5a406d472254800dac8a1a452780f05ca6478486e079a22753de4f614984"
    },
    {
      "chunk_id": "core:chunk:task:ko-KR:misunderstandings:6025770ec8aa36da",
      "section_key": "misunderstandings",
      "heading": "よくある誤解 / 落とし穴",
      "text": "Having a plan does not guarantee results; continuous review is still required. More detail is not always better; the right granularity depends on the context. It can be revised with agreement when conditions or priorities change.",
      "source_refs": [
        "concept:task:en-US",
        "concept:task:ja-JP",
        "core-term-page-500:concept:task"
      ],
      "content_hash": "6025770ec8aa36da36df4028ed753f9f4f728876115995f33cd2e4b5a925c906"
    },
    {
      "chunk_id": "core:chunk:task:ko-KR:examples:4eb36e1b10abc9db",
      "section_key": "examples",
      "heading": "最小例",
      "text": "Example: A team preparing a product launch uses Task to organize work over four weeks. They define the scope (landing page, ad assets, FAQ), assign owners, and set deadlines. Weekly check-ins track progress and surface blockers early. If a dependency slips, they adjust priority and reallocate effort to protect the launch date, documenting changes for shared visibility.",
      "source_refs": [
        "concept:task:en-US",
        "concept:task:ja-JP",
        "core-term-page-500:concept:task"
      ],
      "content_hash": "4eb36e1b10abc9db1793150a536dea972b8601915f0d95dab06dfcd4d35dfb02"
    },
    {
      "chunk_id": "core:chunk:task:ko-KR:comparisons:c8082429bf6b4c17",
      "section_key": "comparisons",
      "heading": "似ている言葉との違い",
      "text": "Compare Task with adjacent concepts before deciding. Task | Current concept | Use when the team needs the primary decision lens Adjacent metric or framework | Supporting lens | Use when the team needs evidence or process detail General vocabulary | Broad explanation | Use only for orientation, not final decision-making Task | Current concept | Use when the team needs the primary decision lens Adjacent metric or framework | Supporting lens | Use when the team needs evidence or process detail General vocabulary | Broad explanation | Use only for orientation, not final decision-making",
      "source_refs": [
        "concept:task:en-US",
        "concept:task:ja-JP",
        "core-term-page-500:concept:task"
      ],
      "content_hash": "c8082429bf6b4c173ae683f3435698c9ae9e4df5806a7ca1f8d406cdd6c5a780"
    },
    {
      "chunk_id": "core:chunk:task:ko-KR:faq:86bdda6b724fa9aa",
      "section_key": "faq",
      "heading": "When should I use Task?",
      "text": "When should I use Task? Use it when the team needs to decide scope, priority, owner, or trade-off, not when it only needs a short definition.",
      "source_refs": [
        "concept:task:en-US",
        "concept:task:ja-JP",
        "core-term-page-500:concept:task"
      ],
      "content_hash": "86bdda6b724fa9aa9132f818f486e12b03532cae727e691f80b1a5ec20d49242"
    },
    {
      "chunk_id": "core:chunk:task:ko-KR:faq:9f00e368094418b9",
      "section_key": "faq",
      "heading": "What makes Task useful in practice?",
      "text": "What makes Task useful in practice? It becomes useful when it is tied to evidence, a decision owner, and a concrete next operating choice.",
      "source_refs": [
        "concept:task:en-US",
        "concept:task:ja-JP",
        "core-term-page-500:concept:task"
      ],
      "content_hash": "9f00e368094418b9e752e3f1a0fab764ea43862ef18ce90aec6d701756328d76"
    },
    {
      "chunk_id": "core:chunk:task:ko-KR:faq:79bb496164ef487a",
      "section_key": "faq",
      "heading": "What should I avoid?",
      "text": "What should I avoid? Avoid using the term as a label without clarifying assumptions, boundaries, and how success will be judged.",
      "source_refs": [
        "concept:task:en-US",
        "concept:task:ja-JP",
        "core-term-page-500:concept:task"
      ],
      "content_hash": "79bb496164ef487a44975af31482e2e5a825ba773600d29b037f06fafdd28eff"
    }
  ],
  "content_hash": "11e4119b7a728f3eeeefbc31de55b1d4ecf7141f8b4b31f9efd44a72fc9ea867",
  "hash_algorithm": "sha256",
  "rag": {
    "chunk_id_policy": "core:chunk:{canonical_slug}:{locale}:{section_key}:{sha256_16}",
    "content_hash_policy": "sha256_stable_json",
    "source_refs_precision": "source_object_ref_or_source_key_current_snapshot"
  },
  "quality": {
    "content_tier": "db_backed",
    "quality": "reviewed",
    "publication_status": "published_reviewed",
    "source_count": 3,
    "last_reviewed_at": "2026-05-10T00:00:00.000Z",
    "trust_policy_version": "core-trust-policy-v1-2026-06-22"
  },
  "limitations": {
    "policy_version": "core-trust-policy-v1-2026-06-22",
    "professional_advice_boundary": "reference_only_not_professional_advice",
    "text": "이 페이지는 조사와 학습을 위한 참조 정보입니다. 회계, 법무, 금융, 의료, 보안 등 개별 판단은 1차 출처나 전문가 확인을 우선하세요.",
    "items": [
      "공개 페이지는 일반 이해와 실무 맥락을 돕는 자료이며, 개별 사안의 전문 조언이 아닙니다.",
      "제도, 가격, 규제, 회계 기준, 제품 사양처럼 빠르게 변하는 정보는 최종 판단 전에 1차 출처를 확인해야 합니다.",
      "AI 지원 제작·감사 흐름을 사용하더라도 공개 여부는 품질 게이트와 사람이 읽을 수 있는 증거에 기반해 다룹니다."
    ]
  }
}