JJarvisconformancev0.1.0

Existing-agent compatibility

Existing agents keep native execution and emit Jarvis-compatible records.

An existing native agent participates in Jarvis by recording the human-agent collaboration contract around native work. Jarvis does not replace the agent, route the model, execute tools, own memory, own UI, own auth, own storage, or become the host adapter.

Open source example

Native surface to Jarvis records

Native agent session

Maps to AgentWorker and Actor records.

Human operator identity

Maps to HumanWorker and Actor records. Hosts own identity provider and auth backend.

Task instruction

Maps to WorkSession objective. Hosts own prompt transport.

Native policy settings

Map to Policy record. Hosts own policy UI and storage.

Allowed native step

Maps to PolicyDecision result allow before accepted state.

Blocked native step

Maps to PolicyDecision review_required or deny plus scoped Request.

Human narrowed authority

Maps to Review decision narrow plus ApprovalScope.

Human direct control

Maps to Takeover with lock_epoch and reconciliation_refs.

Native output

Maps to Contribution and EvidenceManifest refs.

Reviewed lesson

Maps to LearningRecord, MemoryProposal, and SkillProposal.

External result

Maps to OutcomeReport referencing LearningRecord.

Compatibility proof branches

Review resolution

Agent reaches external-source action, records PolicyDecision, creates Request, receives human Review with bounded ApprovalScope, and resumes only inside approved scope.

Takeover resolution

Agent reaches high-risk branch, records PolicyDecision, creates Request, human assumes direct control through Takeover, stale continuation rejects, and resume requires reconciliation refs.

Boundary

Hosts own native agent runtime, model calls, tool calls, memory, skills, tracing, session handling, execution flow, UI, storage, auth, billing, scoring, payment, deployment, adapters, wrappers, and host-specific SDK integration.