J Jarvisimplementer guides v0.1.0

Implementation without runtime drift

Implement Jarvis as protocol records.

Compatible implementations store, emit, validate, reject, export, and preserve Jarvis records. Hosts own runtime behavior, adapters, wrappers, UI, auth, storage, model routing, tool execution, billing, scoring, payment, deployment, monitoring, and host workflow.

Start guide Record examples

Guide contract

Store

Persist protocol records with stable ids, Actor refs, WorkSession refs, revision, and event-hash lineage.

Emit

Emit JarvisEvent-backed state when policy, Request, Review, Takeover, Contribution, Evidence, or Learning changes.

Validate

Validate headers, Actor authority, body/path ids, WorkSession revision, previous event hash, and protocol object shape.

Reject

Reject missing PolicyDecision, unresolved Request, stale Takeover continuation, forbidden export fields, and silent learning mutation.

Guide pages

Implementer guideStorage, emission, validation, rejection, and export duties Existing-agent compatibilityMap native agent work into Jarvis records Request, Review, TakeoverScoped blockers, human judgment, ApprovalScope, and lock epochs Evidence and LearningContribution, EvidenceManifest, LearningRecord, proposals, and OutcomeReport ExtensionsCapability negotiation and extension namespace rules Protocol errorsError envelope, rejection ids, and forbidden fields Protocol examplesMinimal v0.1 record flow examples

Boundary

  • Guides define protocol implementation obligations.
  • Guides do not define runtime behavior.
  • Guides do not define adapters, wrappers, model routing, tool execution, auth provider, storage backend, UI, billing, scoring, payment, deployment, or host workflow.
  • Hosts own UI, auth, storage, runtime behavior, model routing, tool execution, billing, scoring, payment, deployment, monitoring, and host workflow.
  • Hosts own implementation behavior. Jarvis owns the portable collaboration record.