Skip to content

Evidence for AI operations

No English page yet. Showing the Japanese source.

Back to the entrance

Agent Registry/Catalog

用語・参照用語・参照公式仕様のみ公式仕様のみ鮮度未確認鮮度を確定できない

記事状態: 公開 · 最終確認: 未確認

要点

Agent Registry/Catalogは、AI agentやtoolを発見・管理するための資産台帳であり、掲載されていること自体は実行権限、identity、現在の可用性、安全性を保証しない。registry metadataとruntime、IAM、承認状態を別々に観測し、version・owner・identity・endpoint・lifecycleのdriftを継続的に照合する。

現在の判断

Registry/Catalogは少なくともINVENTORY、DISCOVERY、GOVERNANCE/LIFECYCLEを分離する。Registry entry ≠ runtime identity ≠ authorization ≠ deployment health。Microsoftのregistry-only agentが実例であり、掲載だけでidentity存在や認可済みを推定しない。A2A Agent Cardはinteroperable discovery metadataとして有力だが、enterprise registry API自体はA2Aで標準化済みではない。registry recordはagentだけでなくtool/MCP server/skillとの関係をgraphとして持ち、owner、version、environment、identity_ref、endpoint_ref、approval、risk、data scope、lifecycle、last_verified_at、evidence_refを保持する。public/basic cardとrestricted/extended metadataを分離する。

どこまで当てはまるか

Enterprise AI Core / governance / interoperability / implementation / provider mapping / organization overlay.

詳しく理解する

なぜ重要か

agent/tool/skillの増加時、発見可能性だけでなくowner、承認、identity linkage、version、availability、廃止、証拠鮮度を追跡しないとshadow agent、orphan、stale capability、誤認可が生じる。

対象範囲と前提

Enterprise AI Core / governance / interoperability / implementation / provider mapping / organization overlay.

検討ポイント

Registry/Catalogをruntime authorizationと混同せず、discovery・inventory・governance・lifecycleをどう標準化するか。

EVIDENCE TABLE

  • A2A Protocol Specification, Agent Discovery: Agent Card, A2A Protocol Working Group, current dev spec, accessed 2026-09-25, https://a2a-protocol.org/dev/specification/ --- Agent Cardはidentity/capabilities/skills/interaction requirementsを記述し、well-known URI、registry/catalog、direct configurationでdiscover可能。VERIFIED_SPEC / support. 2. A2A Protocol, Agent Discovery, accessed 2026-09-25, https://a2a-protocol.org/dev/topics/agent-discovery/ --- curated registryはAgent Cardを集中管理しskill/tag等で検索可能。ただしcurrent A2A specificationはcurated registryの標準APIを規定しない。VERIFIED_SPEC / support+limit. 3. Microsoft Learn, Manage agents with no agent identities, accessed 2026-09-25, https://learn.microsoft.com/en-us/entra/agent-id/manage-agents-without-identity --- Entra Agent Registry (Preview)にはidentity未関連のregistry-only agentが存在し得る。PRODUCT_VOLATILE+VERIFIED_SPEC / support+counter. 4. Microsoft Learn, View and filter agent identities in your tenant, accessed 2026-09-25, https://learn.microsoft.com/en-us/entra/agent-id/agent-lists --- identity inventoryはowner/sponsor、permissions/roles、audit/sign-in logs等を別途保持。PRODUCT_VOLATILE+VERIFIED_SPEC / context. 5. Microsoft Learn, Agent Registry in Microsoft 365 admin center, accessed 2026-09-25, https://learn.microsoft.com/en-gb/entra/agent-id/registry-agent-to-agent-protocol --- organization内agentのcentralized view、monitor/manage/govern、custom agent upload、owner/risk等の管理surface。PRODUCT_VOLATILE+VERIFIED_SPEC / implementation context. 6. NIST AI RMF 1.0 / Playbook, accessed 2026-09-25 --- AI system inventoryとroles/responsibilities/lifecycle governanceを要求する上位governance context。VERIFIED_SPEC / context.

利用できる条件

provider/platform、tenant、plan/license、region、admin role、registry preview/GA state、A2A version、network reachability、identity provider、organization policyを個別記録。PRODUCT_VOLATILEは公開時再確認。

実装・運用

PROPOSAL AGENT_REGISTRY_ENTRY_V1 = asset_id; asset_type(agent\|tool\|mcp_server\|skill); canonical_name; description; owner; sponsor; provider/platform; version; environment; endpoints; protocol/interfaces; capabilities/skills; input-output modes; identity_ref; auth_scheme_metadata(no secret); tool/dependency_refs; data_scope; approval_state; risk_tier; lifecycle_state; created_at; last_verified_at; deprecation_at; evidence_refs; availability_gates; UNKNOWN. PROPOSAL REGISTRY_RECONCILIATION_V1 = registry_asset_id; discovered_runtime_ref; identity_ref; expected_version; observed_version; owner_state; approval_state; endpoint_health; drift_type; observed_at; evidence_ref; remediation_owner.

確認・評価方法

known deployed assetに対するregistry recall、registry-only率、unregistered runtime率、ownerless率、identity-orphan率、stale-version率、dead-endpoint率、duplicate率、approval mismatch率、mean time to owner/disable/deprecateを測る。catalog search relevanceは別評価し、registry completenessと混同しない。

セキュリティとプライバシー

registry閲覧権限とruntime実行権限を分離。secretをcard/registryへ保存しない。restricted metadataはselective disclosure。create/update/approve/deprecate/delete/identity-link変更をaudit。定期reconciliationとstaleness SLOを持ち、critical agentは短いverification interval。costはregistry基盤だけでなくdiscovery crawl、health check、identity reconciliation、human curationを含める。

要点と前提

RUN_TYPE: MANUAL_HIGH_CONFIDENCE_INVENTORY_UPDATE

対象範囲と前提 2

EA-001..EA-399 only SOURCE_UNION: original ledger + primary research communication + lane1 retreat document + Library packets + current conversation generated packets LEDGER_INTEGRITY: EA-001..EA-399 definitions contiguous; ledger numbering gaps = 0.

RESCUED ORPHAN PACKETS

RESCUED_TO_LANE1_RETREAT: EA-038, EA-039, EA-042 SOURCE: current conversation generated packet files from 2026-09-25. RESEARCH_STATUS: COMPLETE SAVE_STATUS: SYNC_RESCUE_SAVED PRIMARY_CANONICAL_SYNC: PENDING

セキュリティとプライバシー 2

A. NORMAL_RESEARCH_COMPLETE = 147 - EA-001..039 - EA-042 - EA-046..100 - EA-301..352

B. NORMAL_TRUE_GAP = 52 - EA-040..041 - EA-043..045 - EA-353..399

CLAIM_ONLY_NO_PACKET_ARTIFACT: - EA-040: prior chat response claimed completion, but no complete packet artifact was found in primary communication, lane1 retreat, Library, current conversation files, or targeted Drive search. Do not count complete. - EA-041: prior chat response claimed completion, but no complete packet artifact was found in primary communication, lane1 retreat, Library, current conversation files, or targeted Drive search. Do not count complete.

C. LUNA_PRIOR_PACKET_LOCATED_REVIEW_PENDING = 74 - EA-101..174 Use existing LUNA-RESERVE prior packets as PRIOR_WORK. Do not re-research from zero.

D. LUNA_LOCATION_AUDIT_GAP = 38 - EA-175..212 Requires explicit location audit; do not silently classify NOT_LOCATED.

E. LUNA_PRESEARCH_NOT_LOCATED = 87 - EA-213..218 - EA-220..300 Retain NOT_LOCATED unless a uniquely attributable prior artifact is actually found.

F. LUNA_REVIEW_COMPLETE = 1 - EA-219

COUNT_CHECK: 147 + 52 + 74 + 38 + 87 + 1 = 399.

DUPLICATE / SUPERSESSION LEDGER — RETAIN, COUNT ONCE

TRUE_DUPLICATE_OR_RESEARCH_REDO: - EA-001: later 2026-09-25 rerun duplicated existing canonical research. - EA-017: two complete canonical runs. - EA-019: two complete canonical runs. - EA-076: later 2026-09-25 rerun duplicated existing canonical research. - EA-301: later rerun duplicated earlier completed research. - EA-302..305: 2026-09-25 Library runs duplicated earlier retreat packets. - EA-343: two full research runs; count once, later is supplemental/duplicate.

PROVISIONAL_WRONG_TOPIC_SUPERSEDED: - EA-313: provisional wrong-topic Library packet superseded by ledger-verified retreat packet. - EA-314: provisional wrong-topic Library packet superseded by ledger-verified retreat packet. - EA-316: provisional wrong-topic Library packet superseded by ledger-verified retreat packet. - EA-315: earlier Library packet superseded for inventory authority by later ledger-verified retreat packet on same topic.

STATE_EVOLUTION_NOT_DUPLICATE: - EA-219: earlier NOT_LOCATED state superseded by later formal SUPPLEMENTED review.

要点と前提 2

RUN_TYPE: MANUAL_HIGH_CONFIDENCE_SHELF_INVENTORY

対象範囲と前提 3

EA-001..EA-399 SOURCE_UNION: original ledger + primary research communication + lane1 retreat document + Library packet artifacts LEDGER_INTEGRITY: EA-001..EA-399 contiguous; ledger numbering gaps = 0.

セキュリティとプライバシー 3

A. NORMAL_RESEARCH_COMPLETE = 152 - EA-001..039 - EA-042 - EA-046..100 - EA-301..357 Notes: - EA-037 is Library rescue completion. - EA-038, EA-039, EA-042 are rescued into lane1 retreat and remain primary-canonical sync pending. - EA-301..352 are complete by retreat/Library union even where primary canonical synchronization is pending. - EA-353..357 are verified Library rescue packets with all required Evidence Packet fields; SAVE_STATUS=SYNC_PENDING.

B. NORMAL_TRUE_GAP = 47 - EA-040..041 - EA-043..045 - EA-358..399 Claim-only/no-packet correction: - EA-040 and EA-041 were previously claimed complete in chat, but no complete packet artifact is present in the primary communication, lane1 retreat, Library, or targeted Drive search. They remain TRUE_GAP. Lowest normal true gap: EA-040. Forward cursor: EA-358. Backfill queue is separate from forward cursor and must never cause silent rewind.

C. LUNA_PRIOR_PACKET_LOCATED_REVIEW_PENDING = 74 - EA-101..174 Canonical LUNA-RESERVE prior packets exist and must be used as PRIOR_WORK. Do not re-research from zero. The later EA-101..106 LUNA_PRESEARCH_NOT_LOCATED record is superseded by the earlier canonical prior artifacts.

D. LUNA_LOCATION_AUDIT_GAP = 38 - EA-175..212 No formal location-audit result is established. Do not silently classify as NOT_LOCATED.

E. LUNA_PRESEARCH_NOT_LOCATED = 87 - EA-213..218 - EA-220..300 These have explicit location-audit records. Search failure is not proof of nonexistence; retain NOT_LOCATED until a uniquely attributable Luna artifact is found.

F. LUNA_REVIEW_COMPLETE = 1 - EA-219 Formal review supersedes its earlier NOT_LOCATED state.

COUNT_CHECK: 152 + 47 + 74 + 38 + 87 + 1 = 399.

DUPLICATE / SUPERSESSION LEDGER — COUNT ONCE

TRUE_DUPLICATE_OR_RESEARCH_REDO: - EA-001: later 2026-09-25 rerun duplicated existing canonical research. - EA-017: two complete canonical runs. - EA-019: two complete canonical runs. - EA-076: later 2026-09-25 rerun duplicated existing canonical research. - EA-301: later rerun duplicated earlier completed research. - EA-302..305: later Library reruns duplicated earlier retreat packets. - EA-343: two full research runs; count once. - EA-353: two complete Library rescue packets (2026-09-26 01:18 and 02:21 JST); count once. The second run is duplicate/supplemental and MUST NOT advance completion twice.

PROVISIONAL_WRONG_TOPIC_SUPERSEDED: - EA-313: provisional wrong-topic Library packet superseded by ledger-verified retreat packet. - EA-314: provisional wrong-topic Library packet superseded by ledger-verified retreat packet. - EA-316: provisional wrong-topic Library packet superseded by ledger-verified retreat packet. - EA-315: earlier Library packet superseded for inventory authority by later ledger-verified retreat packet on the same topic.

STATE_EVOLUTION_NOT_DUPLICATE: - EA-219: earlier NOT_LOCATED -> later formal SUPPLEMENTED review.

AUDITED BOUNDARY

Agent Registry/Catalog is inventory/discovery/governance/lifecycle, not runtime identity, authorization, deployment health, entitlement, or measured capability. Preserve A2A Agent Card scope; do not claim A2A standardizes a curated enterprise registry API. Preserve provider volatility and every OPEN_UNKNOWN. Currentness recheck recorded by Web audit for A2A Agent Card, Google Cloud Agent Registry, and Microsoft Agent 365 registry.

確認できていること

  • Registry/Catalogは少なくともINVENTORY、DISCOVERY、GOVERNANCE/LIFECYCLEを分離する。Registry entry ≠ runtime identity ≠ authorization ≠ deployment health。Microsoftのregistry-only agentが実例であり、掲載だけでidentity存在や認可済みを推定しない。A2A Agent Cardはinteroperable discovery metadataとして有力だが、enterprise registry API自体はA2Aで標準化済みではない。registry recordはagentだけでなくtool/MCP server/skillとの関係をgraphとして持ち、owner、version、environment、identity_ref、endpoint_ref、approval、risk、data scope、lifecycle、last_verified_at、evidence_refを保持する。public/basic cardとrestricted/extended metadataを分離する。

よくある失敗・反証

  • registry掲載≠実行可能、approved≠entitled、identity_ref存在≠credential有効、Agent Card capability≠実測性能。stale metadata、duplicate agent、orphan identity、unregistered deployment、version drift、endpoint drift、ownerless asset、deleted-but-cached card、registry/API outage、cross-tenant mismatchをfailure classとする。Microsoft preview/current product behaviorをprovider-neutral保証へ外挿しない。

実務での使い方

  • provider/platform、tenant、plan/license、region、admin role、registry preview/GA state、A2A version、network reachability、identity provider、organization policyを個別記録。PRODUCT_VOLATILEは公開時再確認。

  • PROPOSAL AGENT_REGISTRY_ENTRY_V1 = asset_id; asset_type(agent\|tool\|mcp_server\|skill); canonical_name; description; owner; sponsor; provider/platform; version; environment; endpoints; protocol/interfaces; capabilities/skills; input-output modes; identity_ref; auth_scheme_metadata(no secret); tool/dependency_refs; data_scope; approval_state; risk_tier; lifecycle_state; created_at; last_verified_at; deprecation_at; evidence_refs; availability_gates; UNKNOWN. PROPOSAL REGISTRY_RECONCILIATION_V1 = registry_asset_id; discovered_runtime_ref; identity_ref; expected_version; observed_version; owner_state; approval_state; endpoint_health; drift_type; observed_at; evidence_ref; remediation_owner.

  • known deployed assetに対するregistry recall、registry-only率、unregistered runtime率、ownerless率、identity-orphan率、stale-version率、dead-endpoint率、duplicate率、approval mismatch率、mean time to owner/disable/deprecateを測る。catalog search relevanceは別評価し、registry completenessと混同しない。

  • registry閲覧権限とruntime実行権限を分離。secretをcard/registryへ保存しない。restricted metadataはselective disclosure。create/update/approve/deprecate/delete/identity-link変更をaudit。定期reconciliationとstaleness SLOを持ち、critical agentは短いverification interval。costはregistry基盤だけでなくdiscovery crawl、health check、identity reconciliation、human curationを含める。

  • EA-041 Control Planeへregistry reconciliation signalを接続。EA-043 Agent Identityではregistry_asset_idとprincipal/blueprint/service-principalの関係、orphan/driftを深掘り。EA-005 MCP、EA-006 A2A、EA-029 template packともcross-reference。

  • Agent Registry/Catalog is inventory/discovery/governance/lifecycle, not runtime identity, authorization, deployment health, entitlement, or measured capability. Preserve A2A Agent Card scope; do not claim A2A standardizes a curated enterprise registry API. Preserve provider volatility and every OPEN_UNKNOWN. Currentness recheck recorded by Web audit for A2A Agent Card, Google Cloud Agent Registry, and Microsoft Agent 365 registry.

まだ確認できていないこと

  • EA-042-UNKNOWN-01

    / STOP_CONDITION provider横断registry API標準、tool/MCP serverまで含む共通schema、cross-tenant federation、runtime discoveryの完全性保証はUNKNOWN。registry/catalogの責務境界、identity/authorization非同一性、schema、failure envelope、reconciliation evaluationまで確立したためEA-042をbounded close。 NEXT_START: EA-043

  • EA-042-UNKNOWN-CURRENTNESS

    外部根拠の再確認日がcanonical body/control-planeで確定していないため、currentnessはUNKNOWNとして保持する。日付を推測補完しない。

根拠資料

出典ID・検証情報・機械可読データ

根拠の種類と情報の鮮度は、ラベルとアイコンで確認できます。

記事ID
EA-042
最終確認日
—
提供元・モデル・プラン・利用環境
Microsoft
対象地域
—
元資料の全文と収録照合記録
WHY_THIS_MATTERS_TO_UPDATE

agent/tool/skillの増加時、発見可能性だけでなくowner、承認、identity linkage、version、availability、廃止、証拠鮮度を追跡しないとshadow agent、orphan、stale capability、誤認可が生じる。

SCOPE_ROUTING

Enterprise AI Core / governance / interoperability / implementation / provider mapping / organization overlay.

CLAIM_OR_RESEARCH_QUESTION

Registry/Catalogをruntime authorizationと混同せず、discovery・inventory・governance・lifecycleをどう標準化するか。

EVIDENCE TABLE
  • A2A Protocol Specification, Agent Discovery: Agent Card, A2A Protocol Working Group, current dev spec, accessed 2026-09-25, https://a2a-protocol.org/dev/specification/ --- Agent Cardはidentity/capabilities/skills/interaction requirementsを記述し、well-known URI、registry/catalog、direct configurationでdiscover可能。VERIFIED_SPEC / support. 2. A2A Protocol, Agent Discovery, accessed 2026-09-25, https://a2a-protocol.org/dev/topics/agent-discovery/ --- curated registryはAgent Cardを集中管理しskill/tag等で検索可能。ただしcurrent A2A specificationはcurated registryの標準APIを規定しない。VERIFIED_SPEC / support+limit. 3. Microsoft Learn, Manage agents with no agent identities, accessed 2026-09-25, https://learn.microsoft.com/en-us/entra/agent-id/manage-agents-without-identity --- Entra Agent Registry (Preview)にはidentity未関連のregistry-only agentが存在し得る。PRODUCT_VOLATILE+VERIFIED_SPEC / support+counter. 4. Microsoft Learn, View and filter agent identities in your tenant, accessed 2026-09-25, https://learn.microsoft.com/en-us/entra/agent-id/agent-lists --- identity inventoryはowner/sponsor、permissions/roles、audit/sign-in logs等を別途保持。PRODUCT_VOLATILE+VERIFIED_SPEC / context. 5. Microsoft Learn, Agent Registry in Microsoft 365 admin center, accessed 2026-09-25, https://learn.microsoft.com/en-gb/entra/agent-id/registry-agent-to-agent-protocol --- organization内agentのcentralized view、monitor/manage/govern、custom agent upload、owner/risk等の管理surface。PRODUCT_VOLATILE+VERIFIED_SPEC / implementation context. 6. NIST AI RMF 1.0 / Playbook, accessed 2026-09-25 --- AI system inventoryとroles/responsibilities/lifecycle governanceを要求する上位governance context。VERIFIED_SPEC / context.
FINDINGS

Registry/Catalogは少なくともINVENTORY、DISCOVERY、GOVERNANCE/LIFECYCLEを分離する。Registry entry ≠ runtime identity ≠ authorization ≠ deployment health。Microsoftのregistry-only agentが実例であり、掲載だけでidentity存在や認可済みを推定しない。A2A Agent Cardはinteroperable discovery metadataとして有力だが、enterprise registry API自体はA2Aで標準化済みではない。registry recordはagentだけでなくtool/MCP server/skillとの関係をgraphとして持ち、owner、version、environment、identity_ref、endpoint_ref、approval、risk、data scope、lifecycle、last_verified_at、evidence_refを保持する。public/basic cardとrestricted/extended metadataを分離する。

LIMITS / COUNTEREVIDENCE / FAILURE ENVELOPE

registry掲載≠実行可能、approved≠entitled、identity_ref存在≠credential有効、Agent Card capability≠実測性能。stale metadata、duplicate agent、orphan identity、unregistered deployment、version drift、endpoint drift、ownerless asset、deleted-but-cached card、registry/API outage、cross-tenant mismatchをfailure classとする。Microsoft preview/current product behaviorをprovider-neutral保証へ外挿しない。

AVAILABILITY_GATES

provider/platform、tenant、plan/license、region、admin role、registry preview/GA state、A2A version、network reachability、identity provider、organization policyを個別記録。PRODUCT_VOLATILEは公開時再確認。

IMPLEMENTATION_STATE

PROPOSAL AGENT_REGISTRY_ENTRY_V1 = asset_id; asset_type(agent\|tool\|mcp_server\|skill); canonical_name; description; owner; sponsor; provider/platform; version; environment; endpoints; protocol/interfaces; capabilities/skills; input-output modes; identity_ref; auth_scheme_metadata(no secret); tool/dependency_refs; data_scope; approval_state; risk_tier; lifecycle_state; created_at; last_verified_at; deprecation_at; evidence_refs; availability_gates; UNKNOWN. PROPOSAL REGISTRY_RECONCILIATION_V1 = registry_asset_id; discovered_runtime_ref; identity_ref; expected_version; observed_version; owner_state; approval_state; endpoint_health; drift_type; observed_at; evidence_ref; remediation_owner.

BENCHMARK_OR_EVAL REGISTRY_COMPLETENESS_AND_DRIFT_SUITE

known deployed assetに対するregistry recall、registry-only率、unregistered runtime率、ownerless率、identity-orphan率、stale-version率、dead-endpoint率、duplicate率、approval mismatch率、mean time to owner/disable/deprecateを測る。catalog search relevanceは別評価し、registry completenessと混同しない。

SECURITY / PRIVACY / AUDIT / COST / OPERABILITY

registry閲覧権限とruntime実行権限を分離。secretをcard/registryへ保存しない。restricted metadataはselective disclosure。create/update/approve/deprecate/delete/identity-link変更をaudit。定期reconciliationとstaleness SLOを持ち、critical agentは短いverification interval。costはregistry基盤だけでなくdiscovery crawl、health check、identity reconciliation、human curationを含める。

SAFE_WORDING_FOR_FUTURE_BOOK

Agent Registry/Catalogは、AI agentやtoolを発見・管理するための資産台帳であり、掲載されていること自体は実行権限、identity、現在の可用性、安全性を保証しない。registry metadataとruntime、IAM、承認状態を別々に観測し、version・owner・identity・endpoint・lifecycleのdriftを継続的に照合する。

UPDATE_WORK_HANDOFF

EA-041 Control Planeへregistry reconciliation signalを接続。EA-043 Agent Identityではregistry_asset_idとprincipal/blueprint/service-principalの関係、orphan/driftを深掘り。EA-005 MCP、EA-006 A2A、EA-029 template packともcross-reference。

OPEN_UNKNOWN

/ STOP_CONDITION provider横断registry API標準、tool/MCP serverまで含む共通schema、cross-tenant federation、runtime discoveryの完全性保証はUNKNOWN。registry/catalogの責務境界、identity/authorization非同一性、schema、failure envelope、reconciliation evaluationまで確立したためEA-042をbounded close。 NEXT_START: EA-043

要点と前提

RUN_TYPE: MANUAL_HIGH_CONFIDENCE_INVENTORY_UPDATE

SCOPE

EA-001..EA-399 only SOURCE_UNION: original ledger + primary research communication + lane1 retreat document + Library packets + current conversation generated packets LEDGER_INTEGRITY: EA-001..EA-399 definitions contiguous; ledger numbering gaps = 0.

RESCUED_ORPHAN_PACKETS

RESCUED_TO_LANE1_RETREAT: EA-038, EA-039, EA-042 SOURCE: current conversation generated packet files from 2026-09-25. RESEARCH_STATUS: COMPLETE SAVE_STATUS: SYNC_RESCUE_SAVED PRIMARY_CANONICAL_SYNC: PENDING

UPDATED AUTHORITATIVE PARTITION — 399/399 ACCOUNTED

A. NORMAL_RESEARCH_COMPLETE = 147 - EA-001..039 - EA-042 - EA-046..100 - EA-301..352

B. NORMAL_TRUE_GAP = 52 - EA-040..041 - EA-043..045 - EA-353..399

CLAIM_ONLY_NO_PACKET_ARTIFACT: - EA-040: prior chat response claimed completion, but no complete packet artifact was found in primary communication, lane1 retreat, Library, current conversation files, or targeted Drive search. Do not count complete. - EA-041: prior chat response claimed completion, but no complete packet artifact was found in primary communication, lane1 retreat, Library, current conversation files, or targeted Drive search. Do not count complete.

C. LUNA_PRIOR_PACKET_LOCATED_REVIEW_PENDING = 74 - EA-101..174 Use existing LUNA-RESERVE prior packets as PRIOR_WORK. Do not re-research from zero.

D. LUNA_LOCATION_AUDIT_GAP = 38 - EA-175..212 Requires explicit location audit; do not silently classify NOT_LOCATED.

E. LUNA_PRESEARCH_NOT_LOCATED = 87 - EA-213..218 - EA-220..300 Retain NOT_LOCATED unless a uniquely attributable prior artifact is actually found.

F. LUNA_REVIEW_COMPLETE = 1 - EA-219

COUNT_CHECK: 147 + 52 + 74 + 38 + 87 + 1 = 399.

DUPLICATE / SUPERSESSION LEDGER — RETAIN, COUNT ONCE

TRUE_DUPLICATE_OR_RESEARCH_REDO: - EA-001: later 2026-09-25 rerun duplicated existing canonical research. - EA-017: two complete canonical runs. - EA-019: two complete canonical runs. - EA-076: later 2026-09-25 rerun duplicated existing canonical research. - EA-301: later rerun duplicated earlier completed research. - EA-302..305: 2026-09-25 Library runs duplicated earlier retreat packets. - EA-343: two full research runs; count once, later is supplemental/duplicate.

PROVISIONAL_WRONG_TOPIC_SUPERSEDED: - EA-313: provisional wrong-topic Library packet superseded by ledger-verified retreat packet. - EA-314: provisional wrong-topic Library packet superseded by ledger-verified retreat packet. - EA-316: provisional wrong-topic Library packet superseded by ledger-verified retreat packet. - EA-315: earlier Library packet superseded for inventory authority by later ledger-verified retreat packet on same topic.

STATE_EVOLUTION_NOT_DUPLICATE: - EA-219: earlier NOT_LOCATED state superseded by later formal SUPPLEMENTED review.

要点と前提

RUN_TYPE: MANUAL_HIGH_CONFIDENCE_SHELF_INVENTORY

SCOPE

EA-001..EA-399 SOURCE_UNION: original ledger + primary research communication + lane1 retreat document + Library packet artifacts LEDGER_INTEGRITY: EA-001..EA-399 contiguous; ledger numbering gaps = 0.

AUTHORITATIVE PARTITION — 399/399 ACCOUNTED

A. NORMAL_RESEARCH_COMPLETE = 152 - EA-001..039 - EA-042 - EA-046..100 - EA-301..357 Notes: - EA-037 is Library rescue completion. - EA-038, EA-039, EA-042 are rescued into lane1 retreat and remain primary-canonical sync pending. - EA-301..352 are complete by retreat/Library union even where primary canonical synchronization is pending. - EA-353..357 are verified Library rescue packets with all required Evidence Packet fields; SAVE_STATUS=SYNC_PENDING.

B. NORMAL_TRUE_GAP = 47 - EA-040..041 - EA-043..045 - EA-358..399 Claim-only/no-packet correction: - EA-040 and EA-041 were previously claimed complete in chat, but no complete packet artifact is present in the primary communication, lane1 retreat, Library, or targeted Drive search. They remain TRUE_GAP. Lowest normal true gap: EA-040. Forward cursor: EA-358. Backfill queue is separate from forward cursor and must never cause silent rewind.

C. LUNA_PRIOR_PACKET_LOCATED_REVIEW_PENDING = 74 - EA-101..174 Canonical LUNA-RESERVE prior packets exist and must be used as PRIOR_WORK. Do not re-research from zero. The later EA-101..106 LUNA_PRESEARCH_NOT_LOCATED record is superseded by the earlier canonical prior artifacts.

D. LUNA_LOCATION_AUDIT_GAP = 38 - EA-175..212 No formal location-audit result is established. Do not silently classify as NOT_LOCATED.

E. LUNA_PRESEARCH_NOT_LOCATED = 87 - EA-213..218 - EA-220..300 These have explicit location-audit records. Search failure is not proof of nonexistence; retain NOT_LOCATED until a uniquely attributable Luna artifact is found.

F. LUNA_REVIEW_COMPLETE = 1 - EA-219 Formal review supersedes its earlier NOT_LOCATED state.

COUNT_CHECK: 152 + 47 + 74 + 38 + 87 + 1 = 399.

DUPLICATE / SUPERSESSION LEDGER — COUNT ONCE

TRUE_DUPLICATE_OR_RESEARCH_REDO: - EA-001: later 2026-09-25 rerun duplicated existing canonical research. - EA-017: two complete canonical runs. - EA-019: two complete canonical runs. - EA-076: later 2026-09-25 rerun duplicated existing canonical research. - EA-301: later rerun duplicated earlier completed research. - EA-302..305: later Library reruns duplicated earlier retreat packets. - EA-343: two full research runs; count once. - EA-353: two complete Library rescue packets (2026-09-26 01:18 and 02:21 JST); count once. The second run is duplicate/supplemental and MUST NOT advance completion twice.

PROVISIONAL_WRONG_TOPIC_SUPERSEDED: - EA-313: provisional wrong-topic Library packet superseded by ledger-verified retreat packet. - EA-314: provisional wrong-topic Library packet superseded by ledger-verified retreat packet. - EA-316: provisional wrong-topic Library packet superseded by ledger-verified retreat packet. - EA-315: earlier Library packet superseded for inventory authority by later ledger-verified retreat packet on the same topic.

STATE_EVOLUTION_NOT_DUPLICATE: - EA-219: earlier NOT_LOCATED -> later formal SUPPLEMENTED review.

AUDITED_BOUNDARY

Agent Registry/Catalog is inventory/discovery/governance/lifecycle, not runtime identity, authorization, deployment health, entitlement, or measured capability. Preserve A2A Agent Card scope; do not claim A2A standardizes a curated enterprise registry API. Preserve provider volatility and every OPEN_UNKNOWN. Currentness recheck recorded by Web audit for A2A Agent Card, Google Cloud Agent Registry, and Microsoft Agent 365 registry.

  • EVD-EA-042-URL-81C64C3E8BC6研究資料研究資料根拠の出所: SOURCE_PACKET_REFERENCE

    https://a2a-protocol.org/dev/specification/

    裏付ける内容
    —
    確認日
    —
    出典・実験ID
    SRC-EA-042-URL-81C64C3E8BC6
    検証箇所
    EVIDENCE TABLE · https://a2a-protocol.org/dev/specification/
    適用範囲
    EVIDENCE TABLE
    出典・来歴
    SOURCE_PACKET_REFERENCE_PROJECTED
    限界
    元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
  • EVD-EA-042-URL-B121D7CCDB29研究資料研究資料根拠の出所: SOURCE_PACKET_REFERENCE

    https://a2a-protocol.org/dev/topics/agent-discovery/

    裏付ける内容
    —
    確認日
    —
    出典・実験ID
    SRC-EA-042-URL-B121D7CCDB29
    検証箇所
    EVIDENCE TABLE · https://a2a-protocol.org/dev/topics/agent-discovery/
    適用範囲
    EVIDENCE TABLE
    出典・来歴
    SOURCE_PACKET_REFERENCE_PROJECTED
    限界
    元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
  • EVD-EA-042-URL-37179491A973研究資料研究資料根拠の出所: SOURCE_PACKET_REFERENCE

    https://learn.microsoft.com/en-us/entra/agent-id/manage-agents-without-identity

    裏付ける内容
    —
    確認日
    —
    出典・実験ID
    SRC-EA-042-URL-37179491A973
    検証箇所
    EVIDENCE TABLE · https://learn.microsoft.com/en-us/entra/agent-id/manage-agents-without-identity
    適用範囲
    EVIDENCE TABLE
    出典・来歴
    SOURCE_PACKET_REFERENCE_PROJECTED
    限界
    元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
  • EVD-EA-042-URL-6BD665FABFBB研究資料研究資料根拠の出所: SOURCE_PACKET_REFERENCE

    https://learn.microsoft.com/en-us/entra/agent-id/agent-lists

    裏付ける内容
    —
    確認日
    —
    出典・実験ID
    SRC-EA-042-URL-6BD665FABFBB
    検証箇所
    EVIDENCE TABLE · https://learn.microsoft.com/en-us/entra/agent-id/agent-lists
    適用範囲
    EVIDENCE TABLE
    出典・来歴
    SOURCE_PACKET_REFERENCE_PROJECTED
    限界
    元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
  • EVD-EA-042-URL-1BAF2A011AD6研究資料研究資料根拠の出所: SOURCE_PACKET_REFERENCE

    https://learn.microsoft.com/en-gb/entra/agent-id/registry-agent-to-agent-protocol

    裏付ける内容
    —
    確認日
    —
    出典・実験ID
    SRC-EA-042-URL-1BAF2A011AD6
    検証箇所
    EVIDENCE TABLE · https://learn.microsoft.com/en-gb/entra/agent-id/registry-agent-to-agent-protocol
    適用範囲
    EVIDENCE TABLE
    出典・来歴
    SOURCE_PACKET_REFERENCE_PROJECTED
    限界
    元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
  • EA-042-R11-RESEARCH研究資料研究資料根拠の出所: AUDITED_CANONICAL_RESEARCH_PACKET

    EA-042 監査済みresearch / canonical revision binding

    裏付ける内容
    Registry/Catalogは少なくともINVENTORY、DISCOVERY、GOVERNANCE/LIFECYCLEを分離する。Registry entry ≠ runtime identity ≠ authorization ≠ deployment health。Microsoftのregistry-only agentが実例であり、掲載だけでidentity存在や認可済みを推定しない。A2A Agent Cardはinteroperable discovery metadataとして有力だが、enterprise registry API自体はA2Aで標準化済みではない。registry recordはagentだけでなくtool/MCP server/skillとの関係をgraphとして持ち、owner、version、environment、identity_ref、endpoint_ref、approval、risk、data scope、lifecycle、last_verified_at、evidence_refを保持する。public/basic cardとrestricted/extended metadataを分離する。
    確認日
    —
    出典・実験ID
    R1R-062-EA0042
    検証箇所
    R1R-062-EA0042 · EA-042-R5-LEGACY-MIGRATION-20261008-R1 · content/staging/EA-042.md
    適用範囲
    監査済みEA本文・canonical revision・既存Source Graph relationの範囲。欠損currentnessは推測で閉じない。
    出典・来歴
    AUDIT_PASS_CANONICAL_BINDING
    限界
    canonical監査・revision bindingの存在を示す。外部ソースcurrentnessが本文またはcontrol-planeで確定していない場合は、currentnessをUNKNOWNのまま保持する。
  • EA-042-R11-WEB-READBACK実装資料実装資料根拠の出所: IMPLEMENTATION_READBACK

    EA-042 Web body identity / canonical readback

    裏付ける内容
    canonical staging bodyのSHA-256一致とR9 canonical ledger readbackをProduction projectionの入力として検証する。
    確認日
    —
    出典・実験ID
    WEBBODY-EA0042-R8-46301F22
    検証箇所
    WEBBODY-EA0042-R8-46301F22 · content/staging/EA-042.md · EA-042-R5-LEGACY-MIGRATION-20261008-R1
    適用範囲
    R9/R10 canonical readback後のProduction生成時body identity。
    出典・来歴
    CANONICAL_READBACK_BODY_HASH_MATCH
    限界
    body identity/readbackは本文claim自体の真偽や外部ソースの最新性を追加保証しない。
出典ID
R1R-062-EA0042, SRC-EA-042-URL-81C64C3E8BC6, SRC-EA-042-URL-B121D7CCDB29, SRC-EA-042-URL-37179491A973, SRC-EA-042-URL-6BD665FABFBB, SRC-EA-042-URL-1BAF2A011AD6, WEBBODY-EA0042-R8-46301F22
追跡中のUNKNOWN ID
EA-042-UNKNOWN-01, EA-042-UNKNOWN-CURRENTNESS
再確認のきっかけ
canonical revision/publication state change · body artifact hash change · source currentness change · new contradiction or implementation readback

機械検査: 通過 — Automated validation does not guarantee accuracy or authorize execution.

    同じ記事IDの機械可読データです。