JJarvisconformancev0.1.0

Failure modes

Compatible implementations reject unsafe protocol records.

Failure-mode conformance protects the human-agent collaboration and learning loop from fake compatibility, silent learning changes, missing authority, incomplete evidence, stale continuation, and sealed-record mutation.

Required rejections

Headers and authority

Reject missing protocol version, missing Actor header, invalid Actor authority, missing idempotency key, missing request timestamp, stale request timestamp, missing expected WorkSession revision, and missing previous event hash.

Policy and control

Reject missing Policy, missing PolicyDecision before AgentWorker state change, Request resolved without Review or Takeover, terminal state with unresolved Request, and approval without bounded ApprovalScope.

Revision and takeover

Reject stale WorkSession revision, previous event hash mismatch, and stale Takeover continuation.

Evidence and learning

Reject invalid EvidenceManifest export state, sealed WorkSession mutation, sealed EvidenceManifest mutation, host-private export fields, silent memory mutation, silent skill activation, OutcomeReport without LearningRecord, and OutcomeReport with non-terminal source WorkSession.

Fixture-backed rejection ids

missing_protocol_versionmissing_actorunauthorized_actormissing_idempotency_keymissing_request_timestampstale_request_timestampmissing_expected_work_session_revisionmissing_previous_event_hashmissing_policymissing_policy_decisionmissing_review_resolutionmissing_takeover_resolutionrequest_unresolvedinvalid_approval_scopestale_work_session_revisioninvalid_previous_event_hashstale_takeover_epochinvalid_evidence_export_statesealed_work_session_mutationsealed_evidence_mutationforbidden_host_private_fieldsilent_memory_mutationsilent_skill_activationoutcome_report_without_learning_recordoutcome_report_requires_terminal_source

Checklist-only protocol error ids

These ids exist in the OpenAPI contract without dedicated invalid fixtures in the current v0.1 fixture set. Compatible implementations MUST still reject them when the relevant condition appears. Public conformance reports MUST NOT claim fixture coverage for these ids unless fixtures are added.

invalid_transitionunknown_stateunsupported_protocol_versionpath_body_id_mismatchactor_body_id_mismatchmissing_objectivepolicy_deniedreview_requiredinvalid_request_transitionmissing_superseding_requestapproval_scope_expiredapproval_scope_mismatchinvalid_event_hashduplicate_idempotency_key_mismatchrequest_livelockduplicate_request_mismatchmissing_jarvis_eventmissing_blocked_scope_resolution_refsmissing_reconciliation_refsmutation_after_closedinvalid_exportinvalid_export_statemissing_contribution_actorinvalid_contributor_refsshared_contribution_without_individual_refsduplicate_contributor_refevidence_after_the_factmissing_evidence_event_refsduplicate_evidence_item_refforbidden_export_fieldmodel_self_confirmed_memorytool_self_confirmed_memoryskill_expands_tool_access_without_policy_reviewunsupported_capabilityinvalid_extension_namespaceextension_core_field_override

Required error envelope

error_id
protocol_version
object_type
field
reason
remediation
trace_id

Protocol error responses MUST exclude host-private fields.