J Jarvisexisting agents v0.1.0

Existing-agent compatibility

Existing agents keep native execution.

A compatible host maps native human-agent work into Jarvis records. Jarvis does not replace the agent, rewrite the agent, route models, execute tools, own adapters, own wrappers, or own host integration code.

Open record flow

Mapping contract

Native human participant

Map to HumanWorker and Actor records with protocol authority and contribution scope.

Native agent session

Map to AgentWorker and Actor records. The native agent keeps its own runtime and tools.

Native task scope

Map to WorkSession, Policy, PolicyDecision, Request, Review, Takeover, Contribution, EvidenceManifest, and LearningRecord records.

Native feedback

Map post-session result, reviewer feedback, or external evaluation to OutcomeReport and governed LearningRecord refs.

What the host must emit

  • Worker and Actor refs for the protocol-visible human and agent.
  • WorkSession state with objective, Policy, revision, and last_event_hash.
  • PolicyDecision before every AgentWorker action that affects WorkSession state.
  • Request when policy blocks or human judgment is required.
  • Review or Takeover when human judgment resolves the blocked scope.
  • Contribution and EvidenceManifest refs before portable export.
  • LearningRecord, MemoryProposal, SkillProposal, and OutcomeReport records only through governed review paths.

Rejected implementation claims

  • Jarvis-compatible does not mean Jarvis-certified.
  • Jarvis-compatible does not mean official Jarvis host.
  • Jarvis-compatible does not prove production adoption.
  • Jarvis-compatible does not give the native agent a Jarvis-owned runtime.

Host boundary

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

Jarvis owns protocol records for governed collaboration, portable evidence, and shared learning.