JJarvisconformancev0.1.0

Compatible host mapping

Different host shapes produce equivalent Jarvis records.

Compatibility mapping proves that native execution boundaries change no Jarvis object, operation, header, assertion, error id, or export field. Hosts own native execution. Jarvis records portable protocol state.

Open source example

Host shape references

command_line_host_boundarylocal_execution_host_boundaryhosted_execution_host_boundarytool_use_protocol_boundary

host_shape_ref is fixture metadata only. It never enters protocol records, operation bodies, JarvisEvents, EvidenceManifest, or portable export payloads.

Required mapping

Human participant

Maps to Worker, HumanWorker, and Actor records.

Agent participant

Maps to Worker, AgentWorker, and Actor records.

Work objective

Maps to WorkSession objective, Policy, revision, and event hash state.

Agent action

Maps to PolicyDecision before accepted protocol state.

Blocked action

Maps to Request with scope, reason, risk, options, fallback, expiry, and PolicyDecision ref.

Human approval

Maps to Review and bounded ApprovalScope.

Human direct control

Maps to Takeover with lock_epoch and reconciliation refs.

Performed work

Maps to Contribution with human, agent, shared, service, or tool attribution.

Portable proof

Maps to EvidenceManifest evidence refs, event chain root, limitations, and export profile.

Future work change

Maps to LearningRecord, MemoryProposal, SkillProposal, and OutcomeReport when feedback changes future behavior.

Mapping order

  1. Register Worker records.
  2. Register Actor records.
  3. Create HumanWorker and AgentWorker records.
  4. Start WorkSession with objective, Policy, revision, and event hash state.
  5. Record PolicyDecision before AgentWorker action affects protocol state.
  6. Append JarvisEvent for accepted protocol state.
  7. Create Request for denied, review-required, or blocked scope.
  8. Record Review or Takeover for human resolution.
  9. Record Contribution for performed work.
  10. Capture evidence refs from source events and portable artifacts.
  11. Record LearningRecord for confirmed human, agent, or pair learning.
  12. Record MemoryProposal or SkillProposal when learning changes future work.
  13. Submit OutcomeReport only as post-session feedback ingress.