Question 1

Are the offline demo decisions showing real model quality?

Accepted Answer

No. Offline runs use a rule table with every answer flagged degraded. They demonstrate trace, accounting and UI shape; real quality and cost need Laya sidecar or Jev API runs plus bench and compare.

Question 2

How is DECISION.md different from prose prompt files?

Accepted Answer

DECISION.md declares upcoming decisions and compiles to model questions plus policy, with explicit state frames. Prose companions stay as prompts while conformance checks catch undeclared or excluded state.

Question 3

What happens with no Jev key and no local Laya running?

Accepted Answer

It resolves hosted Jev when a key is set, otherwise local Laya, otherwise it names the missing backend and escalates every step instead of guessing.

Question 4

Should I install from npm or from git, and what do I measure?

Accepted Answer

Install this tree from git or clone it rather than trusting the registry tarball. Bench scores decisions against trajectories while compare pits loop shapes on calls and outcomes.

Question 5

What does one offline demo run actually show?

Accepted Answer

In the offline demo, 12 decisions took 53 ms total, about 4.4 ms each, while the single scripted model call took 600 ms, giving a decision-to-model ratio of 12:1 and putting decisions at 8.2% of wall clock. Every answer from the bundled judge is marked degraded with a tilde, because it is a rule table rather than a model, so the run shows the shape of the loop and not decision quality.

Question 6

What is the frame block, and what does the conformance check enforce?

Accepted Answer

Each decision declares a frame naming which few fields of agent state reach the model, how far each is clipped, and which fields are withheld and why, with mandatory per-field bounds so a frame cannot quietly become send-everything. scripts/conformance.ts proves every cell of agent state is either read by a decision or explicitly excluded with a reason; delete an exclusion line and it fails by naming the cell.

Question 7

Can a host that is not JevLoop consume the contract?

Accepted Answer

Yes. npm run external-host is a minimal host that parses, decides and acts with its own state and graph, and offline commands keep it honest: adapter-test runs negative fixtures, adapter-report checks the capability report matches the host's code, replay verifies a real session's decision records still add up, trace renders each as its own markdown and can re-derive digests from those files alone, metrics exports Prometheus text, and claim-audit asks whether the run claimed work the trajectory does not show.

JevLoop — zjunlp

About this project

Highlights

Questions about this entry

Other listings of this project

More Jev resources like this

From the Jev community