Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#290 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
documentation

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
5
Fork
27
Merge medio
1g 13h
PR unite (30g)
104

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di agentrust-io/integrations

Tutte le issue di agentrust-io/integrations

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.