Journey events
plan_view · compare_open · term_flip · checkout_start · faq_open
MINIMAL PAYLOADTHE MECHANISM
Five steps, and one of them is a receipt.
A bounded decision contract turns journey evidence into silence or the minimum useful response—then preserves the counterfactual.
signal → hypothesis → decision → response → receipt
Signals, not identity.
Yesward reads a minimal, versioned event stream. Consent state travels with every event; personal identity is neither required nor inferred.
Session context
Time, sequence, declared page state, eligibility and consent.
NO CROSS-SITE IDENTITYOutcome events
Purchase, qualified lead, abandonment, dismissal, frustration.
VERSIONED CONTRACT02 · INFER
A hypothesis, with its evidence attached.
Friction is always a provisional explanation—not a fact about the visitor.
Commitment
Repeated term changes, returning from checkout, cancellation FAQ.
Choice overload
Repeated comparison without a plan selection.
Coverage
Address changes, serviceability questions, install timing.
Trust in billing
Price detail, fee and renewal questions.
03 · DECIDE
Four tests, five gates, then a coin the engine cannot see.
The policy must justify speaking before stable holdout assignment is applied.
Evidence
Is the hypothesis supported strongly enough?
Eligibility
Is this journey, moment and consent state permitted?
Trust cost
Is the smallest useful response proportionate?
Economics
Can the response create value after its cost?
Assignment
Stable hashing preserves a permanent control.
04 · ACT
The smallest permitted response, in your brand.
The intervention ladder begins with silence and is capped at one question during founding pilots.
Native, not platform chrome
The surface inherits the host brand. Yesward never becomes the visitor-facing brand.
One dismissal, forever
Close one intervention and every Yesward surface stays closed for that session.
Declared actions only
AI self-identifies; tools state what they will do before doing it.
05 · PROVE
Both branches write a receipt.
A decision receipt records why the engine stayed silent or acted, the stable assignment, response, control and measurable outcome.
status
eligible → held out
SIX STATUS WORDS, USED VERBATIMassignment
stable hash 0.41 vs 20% holdout
SAME ELIGIBLE POPULATIONresponse
L3 · One question
RENDERED OR SUPPRESSEDmeasured vs
permanent 20% holdout
COUNTERFACTUAL PRESERVEDSHADOW MODE
The whole mechanism, with the last step switched off.
For the first two weeks every decision is recorded and nothing renders. Operators inspect the would-be moments, hypotheses, suppression and data quality.
Decide
The engine runs the complete policy.
Render nothing
The visitor experience remains unchanged.
Review
Every would-be intervention is inspectable.
SHADOW BEFORE SIGNAL
Watch the mechanism decide in real time.
Send us one signup, checkout, application, or upgrade flow. We’ll identify where customers hesitate or drop off, then show what to test.