Boundaries

Link owns the address and the path traffic takes. It deliberately stops short of:

Money and attribution

Link never decides who paid, how much, or which fan a payment belongs to. It records the click/impression event and the link, and that's where its responsibility ends.

• Whether a click turned into a sale, and the revenue behind it → Club (OfConversion, OfTransaction, and everything under dashboard_vitrina's money half).
• Which fan a source/campaign belongs to → Club. The /sources screen (campaign scanning, confirm/unassign/hide, the fan-sources review tab) is Club's by code — OfCampaign, FanAttribution and the transaction join all live outside Link. Link's own surface there is narrow: the source_link rule table and the raw click/link data the rule resolves against.
• Telegram fan-revenue attribution (tg-attribution) → Club. Link's Telegram gate only writes the tg_bot_starts join key; Club's separate reporting reads it.
• Free-pool spare selection, "dressing" a spare onto a country → Club, even though it writes into Link's own SegmentLink table to do it.

Identity and permissions

• Who can do what (roles, team grants, session/device management) → Account Platform. Link only reads the scope Platform sets (host_in_scope, creator_id).
• Connecting an OnlyFans/Fansly account, proxies, browser sessions → Account Platform.

Shared infrastructure Link only calls into

• Bot / datacenter / country detection as a primitive — the general-purpose utilities (is_bot, datacenter ranges, country resolution) are common core, not Link's; Link's traffic layer only calls them.
• human_clicks() — the frozen predicate that excludes bot clicks from any count. It lives outside any single product on purpose; Link's code sets is_bot, it doesn't own the filter.
• The export/share token mechanism behind the buyer-link feature is the same one used platform-wide for PDF exports — Link reuses it rather than rolling its own.
• File/CDN storage for teaser media and uploads is shared infrastructure, not Link's own.

Adjacent features that sound like Link but aren't

• Cloudflare Turnstile (the login/registration CAPTCHA widget) is unrelated to the Telegram turnstile-gate bot — same English word, different feature, different owner.
• Ad Platforms / Meta Pixel / CAPI dispatch logic touches Link's tables (the pixel config, the postback log) but the dispatch scripts and the default event-mapping live with Club.

What's next

See Connections for the concrete, code-backed contracts behind each of these boundaries.