One system. No duplicate pages.
Core products receive focused deep-dives. Supporting and version-sensitive capabilities stay inside the page where their role is clearest.
Focused deep-dives and routed supporting capabilities.
Each module should be reviewed where its role is clearest. This prevents duplicate pages from creating contradictory claims.
Begir
A buyer states a need; a seller can answer with current price or availability.
Open ↗02Final canonicalRadar
Nearby and time-sensitive demand can connect to a relevant business.
Open ↗03Final canonicalPulino
Follow represents a permissioned relationship—not purchase or guaranteed income.
Open ↗04Final canonicalBoard
Historical/source-described active review and comprehension—not expertise or purchase.
Open ↗05Current canonicalAnalytics
Connected activity can be interpreted without upgrading unresolved metrics into facts.
Open ↗06Illustrative companionPulino Earn
Currency examples are isolated from Pulino's core qualification and trust architecture.
Open ↗07Phase 1 modeled routesMonetization
Historical and modeled earning routes stay separate from audited revenue.
Open ↗08Inside Business + SellingGram
Content migration and visual merchandising support cold-start discovery.
Open ↗09Inside Pulino · chronology-qualifiedStyle / Taste
Presented as designed/supporting unless a specific live period is evidenced.
Open ↗10Inside Selling · version-sensitiveAutoChat
Reusable answers and assisted response logic; availability varied.
Open ↗Begir, Radar, Pulino, Board and Analytics retain standalone pages. Pulino Earn and Monetization are bounded companion records. Gram, Style/Taste and AutoChat stay routed through Business, Selling, Pulino or Architecture.