{ "format": "agent-article-v0", "article_id": "EA-113", "canonical_url": "/tools/ea-113-email-agent", "page_type": "reference", "claim_ids": [], "evidence_ids": [ "EVD-EA-113-URL-BD90285E2563", "EVD-EA-113-URL-9C4C1B2FCF9E", "EA-113-R11-RESEARCH", "EA-113-R11-WEB-READBACK" ], "unknown_ids": [ "EA-113-UNKNOWN-01", "EA-113-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-040-EA0113", "SRC-EA-113-URL-BD90285E2563", "SRC-EA-113-URL-9C4C1B2FCF9E", "WEBBODY-EA0113-R8-3BD024C0" ], "article_sources": [ { "id": "EVD-EA-113-URL-BD90285E2563", "evidence_class": "RESEARCH", "title": "source class: official API documentation; exact title: Create and send email messages; author/org: Google for Developers; canonical URL:", "href": "https://developers.google.com/workspace/gmail/api/guides/sending", "supports": [], "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。", "origin_class": "SOURCE_PACKET_REFERENCE", "source_or_experiment_ids": [ "SRC-EA-113-URL-BD90285E2563" ], "supporting_locators": [ "EVIDENCE TABLE", "- source class: official API documentation; exact title: Create and send email messages; author/org: Google for Developers; canonical URL: https://developers.google.com/workspace/gmail/api/guides/sending" ], "scope": "EVIDENCE TABLE", "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED" }, { "id": "EVD-EA-113-URL-9C4C1B2FCF9E", "evidence_class": "RESEARCH", "title": "source class: standards-track protocol; exact title: RFC 2822: Internet Message Format; author/org: P. Resnick, editor / IETF Network Working Group; canonical URL:", "href": "https://www.rfc-editor.org/rfc/rfc2822", "supports": [], "limit": "元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。", "origin_class": "SOURCE_PACKET_REFERENCE", "source_or_experiment_ids": [ "SRC-EA-113-URL-9C4C1B2FCF9E" ], "supporting_locators": [ "EVIDENCE TABLE", "- source class: standards-track protocol; exact title: RFC 2822: Internet Message Format; author/org: P. Resnick, editor / IETF Network Working Group; canonical URL: https://www.rfc-editor.org/rfc/rfc2822" ], "scope": "EVIDENCE TABLE", "provenance_status": "SOURCE_PACKET_REFERENCE_PROJECTED" }, { "id": "EA-113-R11-RESEARCH", "evidence_class": "RESEARCH", "title": "EA-113 監査済みresearch / canonical revision binding", "supports": [ "Gmail APIは直接sendとdraft経由sendを別methodとして公開し、MIME messageとattachmentの作成を要求する。これにより、生成→検査→承認→送信を技術的に別段階へ配置する設計は可能だが、API仕様は「人間が承認した」「宛先が正しい」「添付が安全」「本文が秘密を含まない」ことを保証しない。RFC 2822はInternet Message Formatのsyntaxで、添付等はMIME extension側であり、宛先判断・業務承認・privacy lawは別層である。" ], "limit": "canonical監査・revision bindingの存在を示す。外部ソースcurrentnessが本文またはcontrol-planeで確定していない場合は、currentnessをUNKNOWNのまま保持する。", "origin_class": "AUDITED_CANONICAL_RESEARCH_PACKET", "source_or_experiment_ids": [ "COMM-040-EA0113" ], "supporting_locators": [ "COMM-040-EA0113", "EA-113-R5-LEGACY-MIGRATION-20261008-R1", "content/staging/EA-113.md" ], "scope": "監査済みEA本文・canonical revision・既存Source Graph relationの範囲。欠損currentnessは推測で閉じない。", "provenance_status": "AUDIT_PASS_CANONICAL_BINDING" }, { "id": "EA-113-R11-WEB-READBACK", "evidence_class": "IMPL", "title": "EA-113 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-EA0113-R8-3BD024C0" ], "supporting_locators": [ "WEBBODY-EA0113-R8-3BD024C0", "content/staging/EA-113.md", "EA-113-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": "email agentは誤宛先、reply thread、添付、機密情報、送信の不可逆性が一つのtool callに重なるため、draftとsendを分離した証拠可能な運用が必要。" }, { "heading": "SCOPE_ROUTING", "text": "application / interoperability / organization overlay / security / audit" }, { "heading": "CLAIM_OR_RESEARCH_QUESTION", "text": "Gmail API上でdraft生成と送信が別操作であることは確認できるか。それは人間承認・宛先安全・機密漏えい防止を保証するか。" }, { "heading": "EVIDENCE TABLE", "text": "- source class: official API documentation; exact title: Create and send email messages; author/org: Google for Developers; canonical URL: https://developers.google.com/workspace/gmail/api/guides/sending; publication/update/access: current page accessed 2026-09-13 JST; version/release/tag/commit/API revision/model ID: Gmail API v1 resource/methods messages.send and drafts.send; supporting locator: lines 93-105（direct messages.sendとdrafts.sendの二経路、raw MIME/base64URL）; lines 205-240（draft作成sample）; lines 264-266, 303-369（attachmentを含むdraft例）; evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE; relation: support / limit.\n- source class: standards-track protocol; exact title: RFC 2822: Internet Message Format; author/org: P. Resnick, editor / IETF Network Working Group; canonical URL: https://www.rfc-editor.org/rfc/rfc2822; publication/update/access: 2001-04, now obsolete and superseded by RFC 5322 / accessed 2026-09-13 JST; version/release/tag/commit/API revision/model ID: RFC 2822; supporting locator: info page lines 48-65, 82-89, 185-209（message syntax and scope）; lines 193-201（MIME extensions are outside this RFC）; evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE; relation: context / limit." }, { "heading": "FINDINGS", "text": "Gmail APIは直接sendとdraft経由sendを別methodとして公開し、MIME messageとattachmentの作成を要求する。これにより、生成→検査→承認→送信を技術的に別段階へ配置する設計は可能だが、API仕様は「人間が承認した」「宛先が正しい」「添付が安全」「本文が秘密を含まない」ことを保証しない。RFC 2822はInternet Message Formatのsyntaxで、添付等はMIME extension側であり、宛先判断・業務承認・privacy lawは別層である。" }, { "heading": "LIMITS / COUNTEREVIDENCE / FAILURE ENVELOPE", "text": "RFC 2822はobsoleteであり、現行のRFC 5322へ更新が必要。Gmail APIの公開Docsは特定tenantのadmin policy、DLP、送信後recall、実際のUI警告を証明しない。誤reply、Bcc、alias、thread、添付版違い、外部recipient、代理送信は別failure class。" }, { "heading": "AVAILABILITY_GATES", "text": "OAuth scope、ユーザー/ドメイン管理、Gmail API quota、送信権限、外部recipient制限、DLP/情報分類、providerの契約を確認する必要がある。実アカウントで送信・draft作成は未実施。" }, { "heading": "IMPLEMENTATION_STATE", "text": "proposed two-phase mail agent（draft-only default、recipient/attachment/content lint、explicit approval token、send endpoint分離、post-send audit）。実装・安全性試験未実施。" }, { "heading": "BENCHMARK_OR_EVAL", "text": "synthetic mailbox fixtureでrecipient exactness、reply headers、attachment hash/name, confidential-marker handling, approval bypass, duplicate send/retry idempotencyを測る。実送信はしない。" }, { "heading": "SECURITY / PRIVACY / AUDIT / COST / OPERABILITY", "text": "SECURITY/PRIVACY: secrets/PIIはsyntheticのみ、DLP preflight。AUDIT: draft ID、content hash、recipient、approval actor/time、send result、provider message ID。COST: API quotaとhuman review工数。OPERABILITY: sendをdefault denyにし、失敗時に自動retryせずdraftへ戻す。" }, { "heading": "SAFE_WORDING_FOR_FUTURE_BOOK", "text": "「Gmail APIはmessages.sendとdrafts.sendを別methodとして提供するため、draft→検査→明示承認→sendという制御点を設計できる。ただし、APIの存在は宛先正確性、承認、DLP、法的適合、送信後回収を保証しない。」" }, { "heading": "UPDATE_WORK_HANDOFF", "text": "本文改訂では、agentの自然言語能力よりもsend capability、OAuth scope、admin/DLP、draft-only、approval evidence、idempotencyを表にする。RFC 5322とMIMEの現行一次資料を再採集し、providerごとのalias/thread挙動をTEST_PROFILE化する。" }, { "heading": "OPEN_UNKNOWN", "text": "RFC 5322準拠範囲、Gmailのtenant別DLP/外部送信設定、reply/alias/Bccのagent failure rate、送信取消可能性、他providerとの差。" }, { "heading": "STOP_CONDITION", "text": "draft作成成功を安全な送信成功と扱わない。公開API Docsから特定組織の設定・実挙動を推定しない。\nUNIT_CLOSE_STATUS: INDIVIDUAL_BOUNDED_CLOSE / EVIDENCE_RECORDED / UNKNOWN_PRESERVED\n\n---" } ], "human_url": "/tools/ea-113-email-agent", "markdown_url": "/agent/article.md?path=%2Ftools%2Fea-113-email-agent", "json_url": "/agent/article.json?path=%2Ftools%2Fea-113-email-agent" }