Referral public case lane selector

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

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

Open Referral Public Case Lane Map Open Referral Public Case Family

2 case lane options
1 lane per asset first
0 hidden relationship leaks required

Referral Case Lane Rule

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

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

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

Referral Public Case Lane Map

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

1. Start From One Approved Referral-Safe Case Asset

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

Open Referral Public Case Family Open Referral Public Case Study

2. Decide Whether The Asset Should Stay Referral-Specific

Some case assets should keep serving the next aligned intro, while others can now reinforce the broader partner-public case lane because the narrative pattern has become portable enough. Make that lane choice before choosing the page type.

Open Referral Public Case Family Open Partner Public Case Family Open Partner Public Router

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

If the story mainly helps another aligned introduction, keep it inside the referral-public case lane and choose between the case router, case page, or converter there.

Open Referral Public Case Router Open Referral Public Case Study Page Open Referral Public Case Study Open Referral Public Case Converter

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

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

Open Partner Public Case Family Open Partner Public Case Router Open Partner Public Case Study Page Open Partner Public Case Study Open Partner Public Case Converter

5. Freeze What Must Stay Hidden

Referrer identity, buyer identity, screenshots, economics, delivery detail, and private relationship logic remain attached to the lane that created them even if one case asset 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 case 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 Case Converter Open Partner Public Case Converter Open Payment Page

First Destinations

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

Referral Public Case Router

Best when the asset should stay inside the referral-safe case lane and still needs a narrower routing decision.

Partner Public Case Router

Best when the story can now support broader partner-public demand without relying on referral context.

Referral Public Case Study Page

Best when the asset should stay referral-specific and only needs one exact public case page shell before broader routing reopens.

Referral Public Case Study

Best when one referral-safe case story still needs the broader page placement decision before final page assembly.

Partner Public Case Study Page

Best when the story can support one exact broader partner-public case page shell before broader conversion choices reopen.

Partner Public Case Study

Best when one portable narrative unit still needs the broader page placement decision before final page assembly.

Referral Public Case Converter

Best when the story belongs to the referral lane and now needs one clear next commercial ask.

Partner Public Case Converter

Best when the story should point into a broader partner-public revenue route after it transitions lanes.

Case Snapshot

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

Case Lane	Best Asset	First Case System	Keep Hidden	Promotion Trigger
Referral public case lane	One case asset tied to a referral-safe story	Referral Public Case Router	Referral path and buyer detail	The next best move is another aligned introduction
Partner public case lane	One portable case asset no longer dependent on referral context	Partner Public Case Router	Private channel path and buyer detail	The pattern now supports broader partner-public conversion
Referral page first	One bounded referral-safe case story	Referral Public Case Study Page	Anything not cleared for broader public use	The asset should stay narrow before wider routing
Partner page first	One bounded portable case story	Partner Public Case Study Page	Anything not cleared for broader public use	The asset is reusable but still not ready for full-page spread

Wallet

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

Choose the case 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