J Jarvisextensions v0.1.0

Extensions

Extensions add namespaced protocol data without overriding core fields.

Jarvis v0.1 preserves compatibility through protocol version negotiation, capability negotiation, and namespaced extension records. Extensions do not add host runtime behavior to Jarvis and do not override core protocol fields.

Open spec page

Extension rules

  • Extensions MUST use a namespace owned by the extension author.
  • Extensions MUST NOT override core Jarvis fields.
  • Extensions MUST NOT weaken required headers, Actor authority, WorkSession revision, previous event hash, Request resolution, Takeover lock epochs, export redaction, or governed learning.
  • Unsupported required capabilities reject as unsupported_capability.
  • Invalid extension namespace rejects as invalid_extension_namespace.
  • Core field override rejects as extension_core_field_override.

Implementation duties

Must store

Store declared protocol version, declared capabilities, extension namespace, and extension refs when accepted.

Must validate

Validate protocol version, capability support, namespace ownership, and closed-schema core field protection.

Must reject

Reject silent downgrade, unsupported required capability, invalid namespace, and extension core field override.

Host boundary

Hosts own UI, auth, storage, runtime behavior, model routing, tool execution, billing, scoring, payment, deployment, monitoring, and host workflow.