Execution path
Users and bots interact with CLManager for lifecycle actions.
CLCore is the canonical state and custody layer: position NFTs, accounting state, permissions, and dust tracking live there.
Trust boundaries by layer
CLManager is the main execution entrypoint for lifecycle actions. CLCore is the canonical state authority for position registration, custody, permissions, and accounting.
Adapters execute venue-specific liquidity and swap steps. ReferralManager tracks referral balances separately from position accounting.
Core components
| Component | Responsibility |
|---|---|
| CLManager | Primary user/bot entrypoint for open, adjust, fee, copy, import, and exit operations. |
| CLCore | Canonical registry, cost basis/accounting state, permissions, NFT custody. |
| Adapters | DEX-specific swaps and liquidity operations for allowlisted venues. |
| Valuation | USDC pricing system used in accounting and safeguards. |
| ProtocolReserve | Protocol fee storage/distribution system. |
| ReferralManager | Referral attribution and claimable referral balances. |
| RebalancePlanner | Helper for balancing token mix in range workflows. |
How this architecture protects lifecycle integrity
| Control | Why it matters |
|---|---|
| Single canonical core state | Prevents fragmented position accounting across external calls. |
| Allowlisted adapters and pools | Restricts execution to explicitly approved venues and pool contracts. |
| Manager-mediated execution | Keeps user flows consistent across open, modify, fee actions, and exit. |
| Pause and recovery model | Enables incident containment and custody recovery without redefining state authority. |