Execution path
Users and bots interact with CLManager. CLManager orchestrates lifecycle flows and delegates DEX-specific execution to allowlisted adapters.
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 only user-facing execution entrypoint for lifecycle actions. CLCore is the only canonical state authority for position registration, custody, permissions, and accounting.
Adapters execute venue-specific liquidity and swap steps. They are only interacted with by the manager.
Core components
| Component | Responsibility |
|---|---|
| CLManager | Primary user/bot entrypoint for open, adjust, fee, 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. |
| 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. |