Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

EABC/cMCP profile: map order_create to execution_id, authorized-intent, observed-effect and execution scope

Đang mở
  • Có gì không ổn?
#290 1 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
35/100
Loại issue
Tài liệu
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
python
Lĩnh vực
documentation

Hướng nghiên cứu

Start by reviewing Discussion #50 and the existing cMCP/TRACE integration material to identify the profile’s intended location and current field conventions. The issue names no files or tests, and asks maintainers to settle the profile location, correlation and authority fields, and how Execution Scope should be represented. Done means those questions are resolved and the agreed profile contract is ready to document.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

Summary

Following Discussion #50, this issue proposes an EABC interoperability profile for cMCP using fields/mechanisms already present in cMCP/TRACE where possible, and isolates the remaining Execution Scope question.

The intent is not to claim native EABC conformance for cMCP. The profile asks what can be mapped directly, what is adapter-level, and what remains unmapped.

Existing mappings

EABC concern cMCP / TRACE mechanism Status
Effect correlation cMCP execution_id + TRACE references[] with rel: observed-effect MAPPED
Authority binding Cedar decision + TRACE references[] with rel: authorized-intent for an externally held grant MAPPED
Exact execution binding cMCP execution/action binding at the forwarding seam MAPPED at the tested adapter seam
Execution Scope declaration of all paths capable of producing the protected effect OPEN / NEW

Concrete example: order_create

The EABC example uses an authorized intent whose parameters include an item/product and quantity, with the resulting protected operation represented as an order_create effect.

The intended evidence chain is:

authorized intent
      ↓
Cedar decision
      ↓
execution_id
      ↓
execution scope
      ↓
order_create
      ↓
observed effect

The corresponding EABC question is:

For the declared order_create effect domain, are all paths capable of producing that effect inside the mediated execution boundary?

This is the Execution Scope / Complete Mediation part. Merely observing MCP forwarding does not establish that arbitrary alternative paths to the same downstream effect are impossible.

Current EABC evidence boundary

Our existing EABC/cMCP work classifies cMCP mediation as scope-bounded rather than universal. It demonstrates an adapter-level execution seam and exact request binding, but does not claim universal downstream effect mediation or physical-world effect proof.

Therefore the profile should preserve:

  • scoped mediation claims;
  • explicit NOT_CLAIMED / gap status where evidence is absent;
  • separation of authorization, execution correlation, and downstream effect observation.

Requested maintainer feedback

  1. Is this the right location and shape for an EABC/cMCP interoperability profile?
  2. Is execution_id the intended cMCP correlation anchor for the profile?
  3. Is rel: authorized-intent the appropriate authority-binding relation when the grant is held outside cMCP?
  4. What is the canonical cMCP representation for Execution Scope: the set/topology of effect-producing paths, or another existing field/object?
  5. If cMCP does not currently represent that scope, should the gap be tracked as a separate cMCP issue rather than extended in the integration profile?

No PR is attached yet. The goal of this issue is to agree the profile location and field contract before adding repository content.

Ngôn ngữ chính
Python
Star
5
Fork
27
Merge trung bình
1 ngày 13 giờ
Pull request đã merge (30 ngày)
104

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của agentrust-io/integrations

Tất cả issue của agentrust-io/integrations

Issue tương tự

Thêm issue về Python

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.