Scope (pages): /swap, /trade

This module is the user entry point for executing token trades. Both /swap and /trade present the core call-to-action “Connect Wallet”, implying the swap router/quote flow is gated until a wallet session exists.

Observed interactive elements

• Primary button: Connect Wallet on both pages.
• The product positioning copy is consistent across pages: “A composable DEX with HFT-grade liquidity.” This suggests an emphasis on fast price updates and deep liquidity sourcing (likely via the CLMM pool set surfaced elsewhere).

How it likely behaves (based on the rest of the app surface)

• Trades are expected to route against the CLMM pools shown under /index and pool detail pages (/pools/:address), where fee tiers and pool stats are available.
• A separation between /swap and /trade commonly indicates simple swap vs advanced trading UX (e.g., more controls, price impact details). Even if not visible pre-connection, the split is intentional in information architecture.

Strategic significance

• Swap/trade is the primary volume driver that feeds 24h Vol. and 24h Fees metrics displayed in the Pools module.
• By centering wallet connection first, Capricorn reduces partial-state complexity (quotes, approvals, slippage settings) and keeps the interface consistent across chains/wallets.

Scope (pages): /index, /pool, /liquidity, /pools/:address (multiple)

This is the deepest functional area: pool discovery, pool-level analytics, and the entry points to create pools and provide liquidity.

Pool discovery (home / list): /index

• Heading: “Earn seamlessly with Capricorn”
• Buttons: Create Pool, Explore Pools, Connect Wallet
• Search field: Search (filters the pool table)
• Pool table columns: # | Pool | Type | Fee Tier | Pool APR% | TVL | 24h Vol. | 24h Fees
• Visible global stats snippet includes: TVL 1.17M, 24h Vol. 2.209M, 24h Fees 2,189, 24h Trades 26,562.
• Example rows show Type = CLMM and fee tiers like 0.3% and 0.01%, with high displayed APRs (e.g., 193.14%, 362.24%, 76.953%).

Pool detail pages: /pools/0x…

• Common state: “Status No Active Positions Found” plus a prompt to create a new position.
• Each pool shows a quoted price line (e.g., WMON USDC 0.3% CLMM 0.0278 = 1) and metrics blocks including Pool APR%, Total Value Locked, 24h Vol., 24h Fees.
• Concrete examples: WMON USDC shows Pool APR% 149.99%, TVL 13,520.2, 24h Vol. 18,534, 24h Fees 55.641; CHOG WMON shows TVL 101.8k and 24h Vol. ~49,212.

Strategic significance

• CLMM pools are the liquidity substrate for trading and the primary yield surface via fee APR.
• The UI exposes institutional-relevant observability (fee tier, volume, fees) needed to assess pool quality and execution conditions.

Scope (pages): /my-positions, /portfolio

This module centralizes user-specific state: LP positions, balances, and likely PnL/fee tracking. Functionality is mostly gated behind wallet connection.

My Positions: /my-positions

• Heading: “My Positions”
• Buttons: Connect Wallet, Explore Pools
• Field: Search (expected to filter positions by pool/token)
• The navigation pattern matches pool pages (e.g., Pools / My Positions / Docs / Connect Wallet), indicating a shared shell and likely shared query/state management.

Portfolio: /portfolio

• Presents Connect Wallet with the same product description banner. Given the dedicated route, this is intended as an account dashboard separate from LP positions (tokens held vs. deployed liquidity).

How it connects to pool pages

• Pool detail pages repeatedly display: “No Active Positions Found” and position states like In range / Out of range / Closed (seen on /pools/0x714a…). Those states typically appear in a positions list UI, implying /my-positions aggregates these per-pool NFTs/ranges.

Strategic significance

• Positions/portfolio views reduce operational friction for LPs by consolidating monitoring and follow-up actions (add/remove liquidity, collect fees).
• For a CLMM DEX, surfacing range status is critical; it tells LPs whether they are currently earning fees, and it drives retention and rebalancing behavior.

Scope (pages): /earn, /farm, /stake

Capricorn separates yield acquisition into three dedicated routes, each gated behind Connect Wallet and sharing the same top-level positioning. Even without full pre-connection detail, the page taxonomy is explicit and maps to common DeFi primitives.

Earn (/earn)

• Likely the umbrella yield hub that routes users toward LP provision, staking, and incentive programs.

Farm (/farm)

• Typically indicates incentivized liquidity mining on top of pool fee APR (extra rewards paid per stake). This aligns with the platform’s heavy emphasis on pool APR metrics in /index and /pools/:address.

Stake (/stake)

• Usually a single-asset staking or protocol token staking area (often used for fee sharing, boosts, or governance alignment). The dedicated route suggests staking is first-class rather than embedded inside portfolio.

Strategic significance

• The separation improves user segmentation: traders (swap), LPs (pools/liquidity), and yield seekers (earn/farm/stake).
• By keeping these routes distinct, Capricorn can independently iterate program logic (reward schedules, multipliers, lockups) without overloading the pool UX.

Note: The pool pages already expose fee-derived performance (Pool APR%, 24h Fees). Farms and staking typically add a second yield layer; the architecture supports stacking fee APR + incentive APR.

Scope (pages): /privacy (and policy links referenced in-app)

This module covers user-facing compliance pages and policy linkouts that appear inside core product flows.

Privacy policy page: /privacy

• Title: “Capricorn”
• Description: “We care about your privacy. Learn how Capricorn collects, uses, and protects your personal information.”
• Heading: “Privacy Policy”

Policy surfaces inside product flows

• Some pool detail pages include footer links such as “Terms of use” and “Privacy policy” (e.g., /pools/0x714a… shows both). This indicates legal pages are intended to be reachable at decision points where users might take financial actions (creating positions, providing liquidity).

Strategic significance

• Legal surfaces reduce platform risk and provide a clear compliance baseline for institutional review.
• Embedding policy links in pool/position contexts is pragmatic: users encounter them where they are about to sign transactions.

What’s missing / implied

• The navigation bar references Docs, but a docs route is not listed here; this suggests documentation may be hosted externally or on a separate path not included in this slice. The UI still makes policy access explicit via /privacy and inline links.