Referral public story family selector

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

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

Open Referral Public Story Family Map Open Referral Public Story Lane

2 story families
1 family per approved story first
0 hidden relationship leaks required

Referral Story Family Rule

Keep the story in the referral public story family 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 family 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 family first
Route: into one narrower story system
Protect: the hidden referral path

Referral Public Story Family Map

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

1. Start From One Approved Referral-Safe Story Asset

Use this page only after one bounded story unit already exists and is cleared for public use. If the story still needs boundary work or approval, keep it out of family routing for now.

Open Referral Public Story Boundary Open Referral Public Proof

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 family because the narrative pattern has become portable enough.

Open Referral Public Family Open Partner Public Family Open Referral Public Story Lane Open Partner Public Story Lane

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

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

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

4. Repurpose It Into The Partner Public Story Family 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 family and choose the narrower destination there.

Open Partner Public Story Lane 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, delivery detail, and private relationship logic remain attached to the family 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 Family

Once the story family is chosen, keep the next ask, payment path, and commercial follow-through inside that same family 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-family destinations.

Referral Public Story Lane

Best when the referral-safe story asset still needs a lane choice before it expands into a boundary, router, or case decision.

Referral Public Story Boundary

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

Referral Public Story Router

Best when the story still belongs to one aligned introduction path and must choose whether to stay a bounded story, shrink, or widen next.

Partner Public Story Lane

Best when the story can now support broader partner demand and still needs a lane choice before wider routing.

Partner Public Story Boundary

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

Partner Public Story Router

Best when the story can now support broader partner demand and must choose whether to stay a bounded story, shrink, or widen next.

Story Snapshot

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

Story Family	Best Asset	First Story System	Keep Hidden	Promotion Trigger
Referral public story family	One story asset tied to a referral-safe story	Referral Public Story Lane	Referral path and buyer detail	The next best move is another aligned introduction
Partner public story family	One portable story asset no longer dependent on referral context	Partner Public Story Lane	Private channel path and buyer detail	The pattern now supports broader partner-public conversion
Referral story router first	One bounded referral-safe story unit ready for a next route decision	Referral Public Story Router	Anything not cleared for broader public use	The asset should stay a story, but the next move is still unclear
Partner story router first	One bounded portable story unit ready for a next route decision	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 referral-safe story family is chosen, keep the next paid step inside that same route.

Choose the story family 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