Referral public story lane selector

Decide whether one approved referral-safe story asset should stay in the referral public story lane or strengthen the partner public story lane next.

Once a referral-safe story asset is already approved for public use, the next job is not cloning it across every page. The real job is deciding whether that asset should keep serving the referral-public story lane that created it or be repurposed into the broader partner-public story lane as a more general signal.

Open Referral Public Story Lane Map Open Referral Public Story Family

2 story lanes
1 lane per approved story first
0 hidden relationship leaks required

Referral Story Lane Rule

Keep the story in the referral public story lane unless the public job now clearly belongs to the broader partner-public story system.

Referral-safe story can travel farther without becoming generic. Good routing chooses one story lane first, keeps buyer and referrer identity locked, and stops one approved asset from drifting between referral and partner claims without a reason.

Choose: the story lane first
Route: into one narrower story system
Protect: the hidden referral path

Referral Public Story Lane Map

Use one sequence from approved referral-safe story asset to the right public story lane.

1. Start After The Story Family Is Fixed

Use this page only after the asset already belongs to one public story family. Family decides the commercial job before the lane gets chosen.

Open Referral Public Story Family Open Partner Public Story Family

2. Decide Whether The Asset Should Stay Referral-Specific

Some story assets should keep helping the next aligned intro, while others can now reinforce the broader partner-public story lane because the narrative pattern has become portable enough.

Open Referral Public Lane Open Partner Public Lane Open Referral Public Story Boundary

3. Keep It In The Referral Public Story Lane When The Next Win Still Depends On Referral Context

If the story mainly helps another aligned introduction, keep it inside the referral public story lane and choose the narrower destination there.

Open Referral Public Story Boundary Open Referral Public Story Router Open Referral Public Router Open Referral Public Case Router

4. Shift It Into The Partner Public Story Lane Only When The Public Job Is Now Broader

If the narrative pattern can now support broader partner-channel demand without relying on referral context, move it into the partner public story lane and choose the narrower destination there.

Open Partner Public Story Boundary Open Partner Public Story Router Open Partner Public Router Open Partner Public Case Router

5. Freeze What Must Stay Hidden

Referrer identity, buyer identity, screenshots, economics, and relationship logic remain attached to the lane that created them even if one story unit becomes reusable elsewhere.

Open Partner Public Proof Open Referral Public Payout Open Proof Board

6. Keep The Payment Path Attached To The Chosen Lane

Once the story lane is chosen, keep the next ask, payment path, and commercial follow-through inside that same lane instead of reopening the routing decision every time the story gets reused.

Open Referral Public Story Router Open Partner Public Story Router Open Referral Public Story Page Open Partner Public Story Page Open Referral Public Story Converter Open Partner Public Story Converter Open Payment Page

First Destinations

Most approved referral-safe story assets belong in one of these first story-lane destinations.

Referral Public Story Boundary

Best when the referral-public lane only needs the smallest safe public story format before it widens.

Referral Public Story Router

Best when the referral-public lane still needs a tighter stay-story, shrink, or widen decision before page placement.

Referral Public Case Router

Best when the referral-public story already needs bounded case escalation instead of another smaller proof move.

Partner Public Story Boundary

Best when the broader partner-public lane only needs the smallest safe public story format before it widens.

Partner Public Story Router

Best when the broader partner-public lane still needs a tighter stay-story, shrink, or widen decision before page placement.

Partner Public Case Router

Best when the broader partner-public story already needs bounded case escalation instead of another smaller proof move.

Story Snapshot

Freeze the chosen story lane, the first story system, and the hidden layer before the asset spreads.

Story Lane	Best Asset	First Story System	Keep Hidden	Promotion Trigger
Referral public story lane	One story asset tied to a referral-safe story	Referral Public Story Boundary	Referral path and buyer detail	The next best move is another aligned introduction
Partner public story lane	One portable story asset no longer dependent on referral context	Partner Public Story Boundary	Private channel path and buyer detail	The pattern now supports broader partner-public conversion
Referral story router first	One bounded referral-safe story route	Referral Public Story Router	Anything not cleared for broader public use	The asset should stay a story, but the next route is still undecided
Partner story router first	One bounded portable story route	Partner Public Story Router	Anything not cleared for broader public use	The asset is reusable but the broader partner route still needs a tighter call

Wallet

Once the story lane is chosen, keep the next paid step inside that same route.

Choose the story lane first, lock the hidden relationship layer, then move payment through the matching commercial path so the story does not drift between referral-public and partner-public claims.

0xB3e9568A9cbB624403743340358c85CCce130893 Open Payment Page