跳到主要内容

Conformance

C2AI2X conformance requires all three layers below, not just a JSON schema match.

1. Standard conformance​

Integration payloads should stay aligned with the neutral artifacts in zhen-protocol-c2ai2x:

  • Demand
  • Envelope
  • AuthorizationGrant
  • ProtocolError
  • ProtocolEvent

2. Platform ingress conformance​

The current public executable subset requires:

  • domain
  • required_scopes
  • execution_mode
  • text or structured_input
  • key_id only on the admin bearer path

And:

  • authentication must pass platform admission
  • if required_scopes is declared, the platform credential must actually satisfy it
  • sync integrations must handle output, usage_applications, and optional exact_bridge
  • async flows must consume the returned workflow URLs from zhen-platform-core

3. Ecosystem boundary conformance​

The following behaviors are not conformant with the current ecosystem model:

  • business frontends calling zhen-brain-core directly
  • treating a vertical site repository as the protocol source of truth
  • treating local caller state as the source of truth for entitlement or quota
  • bypassing platform admission and trying to force brain execution directly
  • request includes stable request_id, trace_id, and idempotency_key handling
  • integration can send either text or structured_input
  • if neutral protocol objects are embedded inside structured_input, any Demand.input_context.raw_input or structured_summary fields stay inside that protocol-layer payload rather than replacing the live top-level HTTP contract
  • integration propagates request_id, trace_id, and idempotency_key
  • caller handles both 200 and 202
  • caller persists returned output metadata, usage_applications, and async workflow references into local logs or events