{
  "format": "agent-article-v0",
  "article_id": "EA-155",
  "canonical_url": "/tools/ea-155-temporal",
  "page_type": "reference",
  "claim_ids": [],
  "evidence_ids": [
    "EVD-EA-155-URL-23A0B3FA7707",
    "EVD-EA-155-URL-FC516B16713E",
    "EVD-EA-155-URL-6D591402A12C",
    "EA-155-R11-RESEARCH",
    "EA-155-R11-WEB-READBACK"
  ],
  "unknown_ids": [
    "EA-155-UNKNOWN-01",
    "EA-155-UNKNOWN-CURRENTNESS"
  ],
  "operational_object_ids": [],
  "provider": [],
  "models": [],
  "plans": [],
  "surfaces": [],
  "regions": [],
  "current_status": "UNKNOWN",
  "observation_status": "SPEC_ONLY",
  "freshness": "UNKNOWN",
  "last_verified": null,
  "supersedes": [],
  "superseded_by": [],
  "provenance": [
    "COMM-046-EA0155",
    "SRC-EA-155-URL-23A0B3FA7707",
    "SRC-EA-155-URL-FC516B16713E",
    "SRC-EA-155-URL-6D591402A12C",
    "WEBBODY-EA0155-R8-824E15FB"
  ],
  "article_sources": [
    {
      "id": "EVD-EA-155-URL-23A0B3FA7707",
      "evidence_class": "RESEARCH",
      "title": "source_class=official technical documentation; exact_title=Temporal Workflow Execution overview; author/org=Temporal Technologies; canonical_url=",
      "href": "https://docs.temporal.io/workflow-execution",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-155-URL-23A0B3FA7707"
      ],
      "supporting_locators": [
        "EVIDENCE_TABLE",
        "- source_class=official technical documentation; exact_title=Temporal Workflow Execution overview; author/org=Temporal Technologies; canonical_url=https://docs.temporal.io/workflow-execution"
      ],
      "scope": "EVIDENCE_TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-155-URL-FC516B16713E",
      "evidence_class": "RESEARCH",
      "title": "source_class=official product/technical page; exact_title=Durable Execution Solutions; author/org=Temporal; canonical_url=",
      "href": "https://temporal.io/",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-155-URL-FC516B16713E"
      ],
      "supporting_locators": [
        "EVIDENCE_TABLE",
        "- source_class=official product/technical page; exact_title=Durable Execution Solutions; author/org=Temporal; canonical_url=https://temporal.io/"
      ],
      "scope": "EVIDENCE_TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EVD-EA-155-URL-6D591402A12C",
      "evidence_class": "RESEARCH",
      "title": "source_class=author-maintained issue/failure report; exact_title=Skip Re-executing Completed Activities on Workflow Retry; author/org=Temporal GitHub issue tracker; canonical_url=",
      "href": "https://github.com/temporalio/temporal/issues/8901",
      "supports": [],
      "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。",
      "origin_class": "SOURCE_PACKET_REFERENCE",
      "source_or_experiment_ids": [
        "SRC-EA-155-URL-6D591402A12C"
      ],
      "supporting_locators": [
        "EVIDENCE_TABLE",
        "- source_class=author-maintained issue/failure report; exact_title=Skip Re-executing Completed Activities on Workflow Retry; author/org=Temporal GitHub issue tracker; canonical_url=https://github.com/temporalio/temporal/issues/8901"
      ],
      "scope": "EVIDENCE_TABLE",
      "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED"
    },
    {
      "id": "EA-155-R11-RESEARCH",
      "evidence_class": "RESEARCH",
      "title": "EA-155 監査済みresearch / canonical revision binding",
      "supports": [
        "- ESTABLISHED: Temporal DocsはWorkflow Executionをdurable/reliable/scalableなfunction executionとし、Workflow/Run ID、local state、Signals、Activities、Event History、Replay、timeouts/retries/Continue-As-Newを別概念として定義する。失敗時に最後の記録Eventから進行を再開すること、単一Executionにはsize/throughput limitsがあることも記載する。\n- ESTABLISHED: Temporal公式サイトはActivitiesをretry可能なfailure-prone logic、Serviceをstate persistence・task queues・signals・timersの実行部品として示し、self-hosted open-source projectとTemporal Cloudの2経路を記載する。Agents/MCP/AI pipelinesやhuman-in-the-loopは利用例・導線であり、LLMの品質保証ではない。\n- COUNTEREVIDENCE/LIMIT: author-maintained issue #8901は、workflow-level retry時に完了済みActivityも再実行され得るという利用者の具体的問題報告を残している。Issueは全version・全retry pathへの普遍化を許さないが、non-idempotent/non-reversible side effectに対してidempotency・compensation・retry policyを別設計すべき根拠になる。\n- INFERENCE: agentの「何をするか」とTemporalの「記録・再開・side effectをどう実行するか」を分離すると、LLM再試行と業務action再試行を別監査単位にできる。ただしこれは設計推論であり、Temporal Docsが任意のagent architectureを保証するものではない。"
      ],
      "limit": "canonical監査・revision bindingの存在を示す。外部ソースcurrentnessが本文またはcontrol-planeで確定していない場合は、currentnessをUNKNOWNのまま保持する。",
      "origin_class": "AUDITED_CANONICAL_RESEARCH_PACKET",
      "source_or_experiment_ids": [
        "COMM-046-EA0155"
      ],
      "supporting_locators": [
        "COMM-046-EA0155",
        "EA-155-R5-LEGACY-MIGRATION-20261008-R1",
        "content/staging/EA-155.md"
      ],
      "scope": "監査済みEA本文・canonical revision・既存Source Graph relationの範囲。欠損currentnessは推測で閉じない。",
      "provenance_status": "AUDIT_PASS_CANONICAL_BINDING"
    },
    {
      "id": "EA-155-R11-WEB-READBACK",
      "evidence_class": "IMPL",
      "title": "EA-155 Web body identity / canonical readback",
      "supports": [
        "canonical staging bodyのSHA-256一致とR9 canonical ledger readbackをProduction projectionの入力として検証する。"
      ],
      "limit": "body identity/readbackは本文claim自体の真偽や外部ソースの最新性を追加保証しない。",
      "checked_at": null,
      "origin_class": "IMPLEMENTATION_READBACK",
      "source_or_experiment_ids": [
        "WEBBODY-EA0155-R8-824E15FB"
      ],
      "supporting_locators": [
        "WEBBODY-EA0155-R8-824E15FB",
        "content/staging/EA-155.md",
        "EA-155-R5-LEGACY-MIGRATION-20261008-R1"
      ],
      "scope": "R9/R10 canonical readback後のProduction生成時body identity。",
      "provenance_status": "CANONICAL_READBACK_BODY_HASH_MATCH"
    }
  ],
  "research_sections": [
    {
      "heading": "WHY_THIS_MATTERS_TO_UPDATE",
      "text": "Agentの確率的判断と、長時間・再試行・障害復旧を担うdurable workflowを分離するため、Temporalを非LLMの実行基盤として後続更新へ渡す。"
    },
    {
      "heading": "SCOPE_ROUTING",
      "text": "Enterprise AI Core / implementation / non-LLM component / governance / audit / cost / operability / security / benchmark。"
    },
    {
      "heading": "CLAIM_OR_RESEARCH_QUESTION",
      "text": "Temporal公式Docsと公式サイトは、Workflow Execution、Event History、Replay、Activity、Signal、retry/timeout、self-hosted/Cloudを何と確立するか。durability/reliabilityの保証範囲と、side effect・determinism・retry時の再実行限界は何か。"
    },
    {
      "heading": "EVIDENCE_TABLE",
      "text": "- source_class=official technical documentation; exact_title=Temporal Workflow Execution overview; author/org=Temporal Technologies; canonical_url=https://docs.temporal.io/workflow-execution; publication/update/access_date=update date not stated / © 2026 / accessed 2026-09-14 00:00 JST; version/release/tag/commit/API revision=current Temporal Docs; supporting_locator=lines 92-119（durable/reliable/scalable execution、local state、Signals/Activities、size/throughput limits、persistence/resume、Continue-As-New）および lines 120-196（Replay、Event History、Commands、Open/Closed、timeouts/retries/cron、Workflow/Run ID）; evidence_label=VERIFIED_SPEC+PRODUCT_VOLATILE; relation=support+limit。\n- source_class=official product/technical page; exact_title=Durable Execution Solutions; author/org=Temporal; canonical_url=https://temporal.io/; publication/update/access_date=update date not stated / accessed 2026-09-14 00:00 JST; version/release/tag/commit/API revision=current Temporal product page; supporting_locator=lines 38-78（state capture、recovery/replay/pause、Activities retry、state persistence、task queues/signals/timers、self-host/open-source or Temporal Cloud）および lines 81-100（visibility、agents/MCP/AI pipelines、human-in-the-loop、long-running workflows）; evidence_label=VERIFIED_SPEC+PRODUCT_VOLATILE; relation=support+context+limit。\n- source_class=author-maintained issue/failure report; exact_title=Skip Re-executing Completed Activities on Workflow Retry; author/org=Temporal GitHub issue tracker; canonical_url=https://github.com/temporalio/temporal/issues/8901; publication/update/access_date=opened 2025-12-24 / accessed 2026-09-14 00:00 JST; version/release/tag/commit/API revision=issue #8901, repository state current at access; supporting_locator=issue description（workflow-level retryで既成功Activityを含め最初から再実行するとの利用者報告、non-reversible side effectsへの問題提起）; evidence_label=SOURCE_REPORT+OSS_PRACTICE; relation=counter+limit。"
    },
    {
      "heading": "FINDINGS",
      "text": "- ESTABLISHED: Temporal DocsはWorkflow Executionをdurable/reliable/scalableなfunction executionとし、Workflow/Run ID、local state、Signals、Activities、Event History、Replay、timeouts/retries/Continue-As-Newを別概念として定義する。失敗時に最後の記録Eventから進行を再開すること、単一Executionにはsize/throughput limitsがあることも記載する。\n- ESTABLISHED: Temporal公式サイトはActivitiesをretry可能なfailure-prone logic、Serviceをstate persistence・task queues・signals・timersの実行部品として示し、self-hosted open-source projectとTemporal Cloudの2経路を記載する。Agents/MCP/AI pipelinesやhuman-in-the-loopは利用例・導線であり、LLMの品質保証ではない。\n- COUNTEREVIDENCE/LIMIT: author-maintained issue #8901は、workflow-level retry時に完了済みActivityも再実行され得るという利用者の具体的問題報告を残している。Issueは全version・全retry pathへの普遍化を許さないが、non-idempotent/non-reversible side effectに対してidempotency・compensation・retry policyを別設計すべき根拠になる。\n- INFERENCE: agentの「何をするか」とTemporalの「記録・再開・side effectをどう実行するか」を分離すると、LLM再試行と業務action再試行を別監査単位にできる。ただしこれは設計推論であり、Temporal Docsが任意のagent architectureを保証するものではない。"
    },
    {
      "heading": "LIMITS / COUNTEREVIDENCE / FAILURE_ENVELOPE",
      "text": "Workflow codeのdeterminism制約、Event History/size/throughput limits、Activity retryのduplicate side effect、worker/service/network outage、versioning/replay incompatibility、timeout/cancellation、namespace/auth/data residency、Cloudとself-hostの差が失敗包絡になる。Issue #8901は有用な反証候補だが、修正済みか・どのversionに該当するかを再確認する必要がある。独立benchmarkは未採集。"
    },
    {
      "heading": "AVAILABILITY_GATES",
      "text": "Temporal Server/Cloud、SDK language/version、namespace、worker/task queue、service persistence backend、self-host topology、Cloud region/data residency、auth/mTLS/RBAC、Workflow/Run ID、retry/timeout policy、search attributes/retention、pricing/state transitions、AI provider/tool credentials。"
    },
    {
      "heading": "IMPLEMENTATION_STATE",
      "text": "Temporal公式Docs、公式サイト、author-maintained issueの確認のみ。server/worker起動、Workflow実行、Activity外部書込み、Cloud契約、credential投入、負荷・failure replay試験は未実施。"
    },
    {
      "heading": "BENCHMARK_OR_EVAL",
      "text": "公式Docsはdurability/replay/visibilityの仕様と概念例を示すが、独立したfailure recovery SLO、throughput benchmark、duplicate-side-effect率、AI agent success rate、cost per accepted outcomeは本Packetで確立していない。Temporalサイトの“millions/billions”やcustomer statementsは製品主張・文脈として扱う。UNKNOWN。"
    },
    {
      "heading": "SECURITY / PRIVACY / AUDIT / COST / OPERABILITY",
      "text": "Security=namespace/RBAC/auth/mTLS、worker isolation、Activity credential、external side effect、LLM/tool egress。Privacy=Workflow input/Event History/Activity payload、search attributes、logs、Cloud retention。Audit=Workflow/Run ID、Event History、Command/Activity/Signal、retry/timeout、worker/version、human approval、provider call。Cost=Cloud state transitions、storage/retention、workers、model/tool/API、retry/compensation。Operability=determinism/replay tests、worker scaling、queue backpressure、idempotency/Saga、versioning/patching、Continue-As-New、outage recovery、history/visibility completeness。"
    },
    {
      "heading": "SAFE_WORDING_FOR_FUTURE_BOOK",
      "text": "「TemporalはLLMではなく、Workflow Executionの状態・Event History・Replay・Activity・Signal・timeout/retryを用いて長時間処理を耐障害化するdurable execution基盤である。公式Docsはsize/throughput・determinism等の限界を含み、author-maintained issueにはretry時の既成功Activity再実行に関する反証報告があるため、外部副作用はidempotency/補償・版固定・再現試験が必要である。」"
    },
    {
      "heading": "UPDATE_WORK_HANDOFF",
      "text": "non-LLM componentとしてTemporalをagent/tool実行のdurability layerへ置き、LLM plan、Workflow state、Activity side effect、human approval、audit/costを別イベントにする。次回はSDK/versioning、determinism/replay、retry/compensation、Cloud/self-host security/data residency、Nexus/MCP/agent integration、issue resolution、再現可能 failure TEST_PROFILEを補う。"
    },
    {
      "heading": "OPEN_UNKNOWN",
      "text": "current server/SDK release、issue #8901の修正状況、exact retry semantics/version、Cloud pricing/state transition、self-host security/HA、Event History retention、agent/MCP integration、side-effect recovery、公開incident・independent benchmark。"
    },
    {
      "heading": "STOP_CONDITION",
      "text": "durable executionを「業務処理が必ず一度だけ成功する」保証へ言い換えない。Activity retry・Workflow retry・compensationを区別し、issue reportを全version/全deploymentの事実へ一般化しない。\nUNIT_CLOSE_STATUS: INDIVIDUAL_BOUNDED_CLOSE / EVIDENCE_RECORDED / UNKNOWN_PRESERVED\n\n---"
    }
  ],
  "human_url": "/tools/ea-155-temporal",
  "markdown_url": "/agent/article.md?path=%2Ftools%2Fea-155-temporal",
  "json_url": "/agent/article.json?path=%2Ftools%2Fea-155-temporal"
}