Versioning and extensions

Compatibility requires explicit version and capability checks.

Jarvis v0.1 uses OpenAPI 3.1 as the machine binding and rejects silent downgrade, unsupported required capability, and extension core-field override.

Version rules

Jarvis-Protocol-Version identifies the protocol line.
OpenAPI info.version identifies the OpenAPI artifact version.
Compatible implementations MUST NOT silently downgrade a request.
Unsupported protocol version rejects as unsupported_protocol_version.

Capability negotiation

Jarvis-Required-Capabilities binds a request to capabilities the caller requires. Compatible minor version proceeds only when required capabilities match.

Supported capability

The implementation proceeds only when the capability is supported and the operation allows capability negotiation.

Unsupported capability

The protocol rejects unsupported required capability as unsupported_capability.

Extension rules

Extensions add protocol-visible fields only under valid extension namespaces.
Extensions MUST NOT override core protocol fields.
Extensions MUST NOT define runtime, workflow, UI, auth, storage, model calls, tool execution, billing, scoring, payment, or deployment behavior.
Invalid extension namespace rejects as invalid_extension_namespace.
Extension core field override rejects as extension_core_field_override.

Source: OpenAPI binding Source: protocol lock