JJarvisv0.1 specificationv0.1

WorkSession lifecycle

WorkSession is the source of truth.

A WorkSession records the focused unit of human-agent collaboration, its event chain, revision, policy, requests, reviews, contributions, evidence, and learning.

Lifecycle states

active

The accepted WorkSession starts as active at revision 1 after the genesis mutation records work_session.created.

waiting_on_human

A Request blocks a declared scope while unrelated safe branches remain available inside Policy.

takeover

HumanWorker controls the affected scope through a Takeover record and lock epoch.

reconciling

The WorkSession records reconciliation after Takeover before autonomous continuation resumes.

completed, failed, cancelled

Terminal outcome states allow final EvidenceManifest export when export requirements pass.

closed

closed is the sealed archival state. The protocol rejects mutation after closed.

Event chain rules

  • Every accepted WorkSession-scoped state change records the Actor.
  • Every accepted WorkSession-scoped mutation verifies Actor authority.
  • Every accepted WorkSession-scoped mutation checks the current WorkSession revision.
  • Every accepted WorkSession-scoped mutation links to the previous event hash.
  • Every JarvisEvent carries sequence, previous_hash, event_hash, and canonicalization.
  • The protocol rejects stale revision, previous event hash mismatch, missing Actor, and unauthorized Actor.

Export rules

EvidenceManifest export happens only from valid WorkSession states. Export includes protocol evidence and excludes host-private fields.

Export includes

policy decisions, requests, reviews, takeovers, contributions, artifacts, evidence items, limitations, and event-chain refs.

Export rejects

credentials, secrets, raw runtime state, host-only database ids, deployment details, billing data, private scores, UI state, raw auth tokens, provider secrets, session cookies, and private keys.