What the page may do, and when

A campaign lists the experiences the system may infer from behavior. A visitor who says what they want in their own words can reach any enabled experience, and help is always available.

Model confidence and donation readiness are separate. A visitor can look ready to give and the model can still be unsure it can tell. That combination changes nothing. The tester below runs the real policy function, so what you see is what the site would do.

Current values

Jev picks a key. The site renders the approved variant behind it, filling in only a topic name from a fixed list. Nothing here is written by a model. Variants marked Draft are proposals: they are stored, but the site never renders them until someone approves them.

Jev picks an event by its id, or names a kind of event. Every date, price and total on the card comes from this list. An event markedDraft is never shown. Events are typed-request only: no campaign infers them from behavior.

A commitment only counts if something in the system holds it. Each one is paired with the mechanism and the place to read it.

1. 1

   We never claim to know an individual's search

   Search Console is aggregate history for a page. It says nothing certain about the person in front of us.

   How it’s enforced. Imported queries are averaged by landing page into a prior that is shrunk by click volume. No per-visitor query field exists anywhere in the visitor state.

   lib/gsc/aggregate.ts · visitorStateSchema

2. 2

   No sensitive or protected attributes

   Nothing infers or stores who someone is: health, faith, income, race, age, location or similar.

   How it’s enforced. The model sees a closed, validated snapshot of session behavior. Every question asks what the visitor is trying to do right now, never what kind of person they are.

   lib/domain/types.ts · lib/jev/questions.ts

3. 3

   Help outranks fundraising

   Someone who might need help gets help, not an ask.

   How it’s enforced. The help rule runs first and at a deliberately low bar (0.40). Service pages carry no asks in either experiment arm, whatever the model says.

   lib/decision/policy.ts · lib/content/pages.ts

4. 4

   Consequential actions are deterministic

   The model never touches money, forms or payment.

   How it’s enforced. Amounts and frequency are parsed by code from what the visitor typed. Gifts, sign-ups and submissions run through ordinary components. Jev's answer keys are a closed set.

   lib/donation/parse.ts · components/adaptive/modules.tsx

5. 5

   The nonprofit approves every word

   The model chooses a key. It never writes copy.

   How it’s enforced. Variants and calendar events are looked up from approved content. Anything with a draft status is skipped, and if no approved variant exists the page is left alone. A ticket price or a date can only come from the calendar.

   lib/content/experiences.ts · findVariant()

6. 6

   Adaptive behavior can be switched off entirely

   One control returns every visitor to the normal static page.

   How it’s enforced. The kill switch on the overview, or ?adaptive=off. When off, no state is inferred and no decision is requested.

   admin overview · DemoProvider

7. 7

   Confidence is never shown to visitors

   A probability is a working signal for the team, not a label to put on a person.

   How it’s enforced. Confidence appears only in the presenter panel and this admin view. Public components render approved copy and nothing else.

   components/adaptive/* · PresenterPanel

8. 8

   A model answer is a signal, not a fact

   When the model isn't sure, the page stays as it is.

   How it’s enforced. Below 0.45 confidence nothing changes. Donation needs readiness and confidence in that readiness. A new experience must win repeatedly before the page changes, to avoid flicker.

   lib/decision/policy.ts · lib/decision/stabilize.ts

9. 9

   Only what's needed, nothing identifying

   No names, emails, device fingerprints or cross-site tracking feed a decision.

   How it’s enforced. The request is validated against a strict schema on the server. The visitor id is a random on-device value used only to assign an experiment arm.

   app/api/decide/route.ts · visitorStateSchema

10. 10

    The visitor's word beats our inference

    If someone tells us what they want, or dismisses a prompt, we listen.

    How it’s enforced. A stated request skips inference and resolves straight to approved content, and a request that asks for two things gets both. A dismissed experience is not shown again this session.

    lib/decision/policy.ts · explicitResolved() · dismissed