← SES-021 — Lifecycle and Security State Machines · Standard Index · SES-023 — Versioning, Negotiation, and Compatibility →
Status: Draft 1.0 — Normative target.
Different transports MUST converge on one semantic execution contract. MCP, GraphQL, REST, RPC, SDKs, and agent protocols MAY expose different syntax but MUST NOT define independent authorization semantics.
A future normative envelope MUST contain:
Transport-provided claims MUST be classified as untrusted until validated by the host trust domain. Tool descriptions, schema descriptions, labels, natural-language metadata, and agent-generated arguments MUST NOT directly grant capability.
The protocol MUST distinguish at least:
InvalidInput, UnknownSemantic, AmbiguousSemantic, Unauthorized, StaleAuthorization, InvalidProvenance, UnsupportedProvider, ResourceExceeded, Conflict, Cancelled, and ExecutionFailure.
An implementation MUST NOT collapse security rejection into a successful transport response.
Equivalent semantic requests sent over two conformant transports MUST resolve to equivalent SOGs and authorization decisions, subject only to explicitly documented transport context differences.
Peers MUST negotiate protocol, semantic-contract, operation-graph, provenance, IR, and capability versions before execution when compatibility is not implicit.
Specify canonical JSON/CBOR encodings, capability discovery, signed envelopes, replay protection, delegation tokens, streaming semantics, pagination, and backward/forward compatibility rules.
A transport-conformance suite MUST replay the same semantic vector through at least two transport adapters and compare canonical semantic, authorization, provenance, and error outcomes.
← SES-021 — Lifecycle and Security State Machines · Standard Index · SES-023 — Versioning, Negotiation, and Compatibility →