Public story family selector

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

Once one partner-safe story asset is approved for public use, the next job is not dropping it into every page shell. The real job is choosing which public story family it should strengthen first: should it keep serving broader partner-channel demand, or should it help the referral public story family support one more aligned intro?

Open Partner Public Story Family Map Open Partner Public Story Lane

2 story families
1 family per approved story first
0 private channel leaks required

Partner Public Story Family Map

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

1. Start From One Approved Partner-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 redaction or approval, keep it out of family routing for now.

Open Partner Public Story Boundary Open Partner Public Proof

2. Decide Which Story Family The Asset Should Strengthen

Some story assets should still help broader partner-channel demand most, while others should mainly help one aligned referral path. Make that family choice before choosing the next page type.

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

3. Use The Partner Public Story Family When The Original Channel Still Carries The Sale

If the story mainly supports partner acquisition, white-label trust, or repeatable channel work, keep it in 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

4. Use The Referral Public Story Family When The Asset Should Drive The Next Intro

If the story should mainly help one 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

5. Keep Each Hidden Layer Attached To Its Own Story Family

Buyer identity, source path, screenshots, economics, and any masked operating context stay attached to the story family that created them. Reuse rights should stay narrow even when the asset looks portable.

Open Partner Public Proof Open Partner Public White Label Open Partner Public Payout

6. Keep The Next Paid Step Narrow And Story-Family Specific

Once the story family is clear, keep the next ask, payment path, and commercial follow-through attached to that same family instead of reopening the routing choice every time the story gets reused.

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

First Destinations

Most approved story assets belong in one of these first story-family destinations.

Partner Public Story Lane

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

Partner Public Story Boundary

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

Partner Public Story Router

Best when the story still belongs to partner-public demand and must choose whether to stay a bounded story, shrink, or widen next.

Referral Public Story Lane

Best when the story should mainly help one aligned referral path and still needs a lane choice before wider routing.

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 mainly helps one aligned introduction and must choose whether to stay a bounded story, shrink, or widen next.

Story Snapshot

Freeze the 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
Partner public story family	One story asset tied to partner-channel demand	Partner Public Story Lane	Private channel path and buyer detail	The original partner-public route still needs the story most
Referral public story family	One story asset tied to an aligned intro-forward path	Referral Public Story Lane	Referral path and buyer detail	The next best move is one aligned introduction
Partner story router first	One bounded public story unit ready for a next route decision	Partner Public Story Router	Anything not cleared for broader public use	The asset should stay a story, but the next move is still unclear
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 next best move may belong to the referral story system instead

Wallet

Once the story family is chosen, keep the next paid step inside the same story system.

Choose the story family first, keep the hidden layer fixed, then move payment through the same commercial route so the asset does not drift between partner-public and referral-public story claims.

0xB3e9568A9cbB624403743340358c85CCce130893 Open Payment Page