One sentence.
Two decisions.

Change one fact. See where SERV draws the line.

ORIGINAL FACT4 days
ONE CONTROLLED EDIT45 days
SERV ANSWERApprove
SERV ANSWEREscalate
SAMPLEONE FACT CHANGEDIllustrative values / no API call

WORKED EXAMPLE

One changed fact. Two bounded answers. One human judgment.

A one-variable refund example, clearly marked as illustrative.

SAMPLE

Should this refund request be approved, escalated, or declined?

Allowed: Approve / Escalate / Decline
ORIGINAL SERV ANSWERApprove
EXACT INPUT EDIT / 3 EDITED CHARACTERS
445
ANSWER CHANGEDone controlled fact
CHALLENGED SERV ANSWEREscalate
Read the complete inputs and exact diff
ORIGINAL INPUT

Order #1842 arrived 12 days late. The package is unopened. The refund request was submitted 4 days after arrival. Policy allows returns within 30 days.

CHALLENGED INPUT

Order #1842 arrived 12 days late. The package is unopened. The refund request was submitted 45 days after arrival. Policy allows returns within 30 days.

Order #1842 arrived 12 days late. The package is unopened. The refund request was submitted 445 days after arrival. Policy allows returns within 30 days.
Want a fresh measurement?Two new SERV requests. Existing recorded evidence is never overwritten.

CLEAR RESPONSIBILITY

Four roles. No invented certainty.

A changed answer stays an observation until a person labels what should have happened.

  1. SERV decides

    It must select exactly one configured answer. Anything else is FAILED.

  2. Jev analyzes

    It can assess the experiment's hold or flip, apparent edit relevance, and review priority.

  3. A human labels

    The reviewer confirms the expected answer and the edit's intended effect.

  4. Code keeps proof

    Choiceproof validates, stores, publishes by consent, and reruns cases against revisions.

PRIVATE BY DEFAULT

Test a boundary in under a minute. Keep the cases that matter.

Test a decision