Skip to the article

Jevstice

What is Jevstice?

Jevstice is an oh-my-pi addon that checks whether the agent understood your request and built what you asked for.

Jev compares the agent's decisions with the request, plan, and evidence from the session. Its findings appear in the terminal without stopping the work.

Why use it?

A booking test can tell you whether South accepts a reservation. It won't tell you whether the help page promises a waitlist that South doesn't offer. Jev can check those words against the studio policy.

Examples

When I give a cheap model a coding task in YOLO mode, it can start calling tools and writing code before it has worked out what I asked for or made a plan.

Jev checks the requirements against my request and the plan against those requirements. At acceptance, it checks what the code and test results actually prove.

Triage

1 / 4
The booking brief
Choose a version of the triage submission
Invalid input

A date slipped into the brief.

The agent sent the terminal's date and working directory along with the booking request. Triage rejected the extra text before Jev read the brief.

Registered

The booking API and the help page.

The agent removed the terminal reminder. Jev registered two topics: moving the bookings to two studios and checking what the help page promised.

Requirements

2 / 4
The requirements checklist
Choose a version of the requirements checklist
Passed

Six items about the API.

The checklist covered seat limits, duplicate emails and old bookings. It said nothing about South's waitlist.

Findings

A seventh item for the help page.

The agent added the seat and waitlist policy. Jev supported that item but couldn't confirm the checklist covered the whole brief.

Passed

No new waitlist route.

The agent saved the distinction in the checklist: “Keep the policy-accurate help copy in this draft, not an API route.”

Plan review

3 / 4
The route plan
Choose a version of the plan outline
Findings

Server setup in the route step.

The agent put studio selection, seat limits and email checks there too. Jev sent that step back and accepted the other six.

Findings

Which booking methods?

The agent specified a 400 for missing or unknown studios on “requests to /bookings.” That step still didn't name GET and POST.

Outline passed

Check the studio before GET or POST.

The agent moved studio validation ahead of both methods. The review stopped at the outline; Jev didn't review the detailed steps.

Fact-check

4 / 4
The booking desk notice
Compare the agent's full draft with the booking desk checks
Inconclusive

The agent's full help text.

Jev supported the policy claims but couldn't tell whether the draft covered the whole request. Neither of the two fact-checks passed overall.

Incomplete

“Both studios have two seats.”

That was the old notice. In a separate check, Jev supported North's count and left South's count unresolved. The signed policy gives South just one seat.

Both claims supported

North offers two seats. South offers one seat.

Jev checked each count against the signed policy and found that the corrected notice answered the booking desk's question.

Read the policy and Jev's result
“North offers two seats and South offers one. The public waitlist is available when North fills up. South has no waitlist for this pilot.”

Jev marked both counts relevant. It left open whether the claim list was exhaustive.

Read the recorded fact-check

The old and corrected notices were checked separately from the development run, against the same signed policy.

What else Jev can do

What did we agree to build?
Context
Reopen the brief to see which studio gets the old bookings.
Consult
Weigh two ways to keep those bookings: copy the rows or add a studio column in place.
Re-aim
Record a new brief if you decide to build the waitlist after all.
Does the code do what we asked?
Course check
See whether the current change still leaves the waitlist out of the API.
Developer review
Ask whether the database change could drop a booking.
Acceptance
Check the test result: did an old North booking survive a restart?
What belongs in the help text?
Search relevance
Compare the signed policy and the old notice as sources for South's waitlist.
Text review
Flag “when it fills up” if the help page doesn't say which studio “it” means.
Anti-slop
Flag a promise like “You'll always get a seat” when the policy makes no such guarantee.

Jevstice runs in oh-my-pi. For DeepSeek Harness, dsh-jev-planning offers Jev planning.

If you're adapting Jevstice for another harness, write to me or visit the repository.