Proof-bounded growth route

Build Your PocketNode Network

A clear Builder guide for 21-level network structure, source-backed activity, compliant sharing, and Partner Kit handoff without income guarantees.

Open source-aware Partner Kit gate Read Academy proof feed
Route statusLOCAL SOURCE READY
Partner Kit gateBLOCKED/LIMITED by KB#3446
Proof layerroute copy + claim matrix
LIMITED Network growth needs accepted proof states
Source-backed relation Gate before launch copy
Role definition

Builder means growing the network responsibly

The public route explains the role, the tree vocabulary, and the proof labels users should expect before stronger claims appear.

FULL

Role surface

Builder has a dedicated public route, navigation entry, and softened role copy.

LIMITED

Mechanics

Tree terms and income-event states are described as product boundaries, not live payout proof.

BLOCKED

Launch handoff

Partner Kit attribution is blocked/limited until KB#3446 repair proof closes.

Network architecture

21 levels are structure, not a guaranteed result

The route may describe a 21-level tree because that is the accepted role architecture. It must not imply every branch is active, qualified, payable, or withdrawable.

Source
KB#3454 claim matrix + Builder task KB#3455
Does not prove
Referral tracking correctness, matched clicks, ledger credit, withdrawal availability, or live financial reconciliation.
L1Direct relation

A direct Builder relation can be explained only after attribution source and anti-abuse checks are accepted.

L2-L5Early branches

Branch depth shows structure. It does not prove activity, qualification, payable status, or earnings.

L6-L20Deep structure

Deep levels stay educational until canonical referral, event, and ledger sources agree.

L21Outer boundary

Level 21 is a product boundary, not a promise that the outer tree exists or pays.

BLOCKED

Live-looking stats stay hidden until sources are accepted

If source, freshness, status, or digest is missing, stale, or blocked, the route keeps the explanation static instead of inventing numbers.

Source
KB#3446 attribution gate + Doc#5745 claim packet
Freshness
No accepted public projection endpoint for this route
Status
No matched-click or referred-code proof; educational view only
Digest
KB#3456 static explainer; no runtime or finance proof
Income-event boundaries

Earning copy stays conditional and proof-labeled

A Builder event needs source, qualification, ledger state, and separate finance proof before users can treat it as earned or withdrawable.

Source eventA user action has an accepted attribution source.
Qualified relationPolicy and anti-abuse checks allow the relation to count.
Ledger stateCredit, hold, pending, and withdrawable states need backend/finance proof.
Proof boundaryThis route proves copy and navigation only, not money movement.
BLOCKEDReferral attribution events

Clicks and codes remain a launch gate until matched clicks and referred-code users are proven.

LIMITEDCompute/runtime events

Runtime activity can be described only through its own health, journal, and payout proof chain.

BLOCKEDPartner Kit events

Partner Kit can educate and hand off, but it is not a proven acquisition or income engine yet.

LIMITEDAccruals and withdrawals

Earned, pending, hold, and withdrawable states require separate ledger, reconciliation, and financial proof.

ROADMAPRoadmap events

Future Builder incentives stay labeled as roadmap until release, runtime, and finance evidence exist.

Partner Kit handoff

Partner Kit stays visible, but the launch state is honest

KB#3446 found serious attribution proof gaps: clicks existed, but matched clicks and referred-code users were not proven. The public handoff can educate, but cannot look like a ready acquisition engine.

Open source-aware Partner Kit Open proof boundaries
Gate state
BLOCKED/LIMITED by KB#3446 attribution repair
Web handoff
Passes source=builder-network and UTM labels into Partner Kit; the backend remains the attribution proof source.
Android handoff
Dashboard opens the Partner Kit tab, then native share actions reuse the existing referral route.
States to test
Signed-out landing, signed-in dashboard, unavailable code, attribution-gated, and future live-ready states.
Forbidden promise
No fake counters, fake safety badges, guaranteed income, or unsupported withdrawal wording.
Growth rules

Honest growth beats noisy acquisition

Builder messaging must help people understand PocketNode without pressure, spam, or invented outcomes.

01No guarantees

Do not promise a fixed percent, passive income, forever income, or payout readiness without fresh proof.

02Anti-spam

Use approved education paths and avoid mass unsolicited outreach.

03Proof labels

Every strong claim needs source, freshness, and a clear does-not-prove boundary.

04Approved paths first

Use Partner Kit, Academy, and prepared materials before custom claims or hand-written tracking links.

05Source quality review

Bought traffic, bots, fake screenshots, or misleading referral posts should be reviewed before any growth credit.

06Report disputed sources

Keep the source link, channel, timestamp, and screenshot so support can review evidence without exposing private data.

Evidence to keep
Source link or id, channel/campaign, timestamp, screenshot, visible claim, and proof label.
Admin view
Partner Kit admin may pause, block, stale-mark, or deprecate a source link with audit metadata only.
Support path
Support reviews source quality and disputes; it must not promise hidden registrations, accruals, or payouts.
No money override
Reviews do not change sponsor truth, balances, ledger rows, withdrawals, payouts, or accruals without a separate governed task.
Next reading

Users should move from role context to education and proof surfaces without confusing docs, runtime, release, or financial truth.

Partner KitSource-aware handoff with an explicit attribution gate. Academy & UpdatesProof-labeled updates and known gaps. Proof & TransparencyClaim states, limitations, and proof boundaries. RolesCompact Builder role card with softened public copy.