referral_followed
0
external-attributable
No external-attributable event is published for this experiment yet.
runningReview · 2026-09-15Evidence · public-safe only
A useful delivery receipt can become a trustworthy referral surface when it states scope, evidence class, expiry, and the next bounded action.
§ TestSmallest useful loop
One problem, one action, one result.
- Observed problem
- Receipts usually prove a transaction to the parties but do not help the next buyer assess what was actually delivered.
- Smallest test
- Attach one public-safe referral path to an internal release receipt, then distinguish views from attributable follows and repeat use.
- Target actor
- A recipient who can refer another operator to the same bounded method
- Requested action
- Follow the receipt's named next action with its experiment identifier intact
- Success event
referral_followed- Live state
- running
- Next gate
- Review on 2026-09-15. Remove the referral mechanism if it obscures evidence scope or produces 50 attributable receipt views without one qualified follow.
§ Lim.Present limits
What this experiment does not yet establish.
- The current receipt is owner QA and does not establish external demand, payment, or customer delivery.
§ ReuseExisting components first
The experiment assembles what already works.
- Evidence Register envelope
- Neomorphic public receipt endpoint
- Pilot source classification
§ SignalCurrent public counters
The event and its source travel together.
Owner QA for the public lab release, explicitly not an external customer receipt.
§ KillPre-registered stop
A failed test earns a clear ending.
Remove the referral mechanism if it obscures evidence scope, leaks private delivery context, or produces 50 attributable receipt views without one qualified follow.