Auto Finance primary sources — 2026-05-08

Classification takeaway

Auto Finance is best classified as automated LP-capital routing and liquidity-direction infrastructure. The key design surface is not merely “yield aggregation” but the contract-governed decision process for when capital is allowed to move: solver proposes, strategy validates, Autopool executes, DestinationVaults hold downstream claims, and rewards are later liquidated and redeployed.

Primary sources reviewed

1. Docs introduction — https://docs.auto.finance/

   • Frames Autopools as a response to the complexity LPs face when managing positions across DEXes and lending venues.
   • Says the product is focused on autonomous, transparent, and sophisticated rebalancing for liquidity provision rather than generic DeFi portfolio management.

2. Docs query: core mechanism / roles — https://docs.auto.finance/auto-pools-protocol/introduction.md?ask=What%20is%20the%20core%20mechanism%20of%20Auto%20Finance%20Autopools%2C%20how%20do%20they%20rebalance%20capital%2C%20and%20what%20roles%20control%20strategy%20or%20execution%3F

   • Gives the cleanest short description of the role split: deposit → monitor → compare → propose → validate → execute.
   • Explicitly says the Solver finds rebalance paths and timing, the Strategy acts as gatekeeper, and the Autopool executes the rebalance after validation.
   • Useful because it identifies the protocol’s actual control surfaces rather than only its user-facing value proposition.

3. Autopool system high-level overview — https://docs.auto.finance/developer-docs/contracts-overview/autopool-eth-contracts-overview/autopool-system-high-level-overview.md

   • Describes the full asset flow: users deposit into Autopools, solver proposals turn base assets into destination LP tokens, DestinationVaults may further stake those LP tokens, rewards are later collected and liquidated, and debt reporting revalues positions before new rebalances.
   • Shows that the protocol holds destination claims through vault shares and rewarder contracts rather than directly presenting itself as one monolithic portfolio.

4. Autopool strategy docs — https://docs.auto.finance/developer-docs/contracts-overview/autopool-eth-contracts-overview/autopool-contracts-and-systems/autopool-strategy.md

   • This is the most informative source for mechanism analysis.
   • Specifies a composite return metric mixing base return, fee return, incentive return, and price return.
   • Explains swap-loss offset periods, adaptive tightening/loosening of turnover thresholds, and 30-60-90 NAV lookback tests that can pause pool swaps if recent turnover has not improved NAV.
   • These details matter because they reveal where policy, discretion, and risk controls actually sit.

5. AUTO staking docs query — https://docs.auto.finance/auto-pools-protocol/staking-auto.md?ask=What%20is%20AUTO%2C%20what%20rights%20or%20rewards%20does%20staking%20it%20provide%2C%20and%20how%20does%20it%20connect%20to%20protocol%20fees%20or%20governance%3F

   • Confirms the current branding shift from legacy TOKE to AUTO on a 1:1 basis.
   • Says staking AUTO mints sAUTO and connects holders to the current staking / revenue model, but the present docs do not foreground direct governance rights the way older Tokemak narratives did.
   • This is analytically useful because it suggests the current protocol story is more operational and product-centric than explicitly governance-direction-centric.

6. Public contracts repo README — https://raw.githubusercontent.com/Tokemak/v2-core-pub/main/README.md

   • Confirms the existence of a public contracts repo for the Autopilot system.
   • References the Tokemak Autopilot system and points to official explanatory material, helping connect the current Auto Finance branding back to the older Tokemak architecture lineage.

7. GitHub organization — https://github.com/Tokemak

   • Shows the live project still uses Tokemak-branded repositories.
   • Important for source-tracing because the protocol’s current product brand and historical repo namespace differ.

Whitepaper / technical-doc status

• No current single canonical whitepaper or litepaper surfaced clearly in this pass.
• The most useful primary materials were the docs introduction, contract-overview docs, doc-query answers, and the public repo README.
• For now, the docs are strong enough to classify the mechanism even without a polished whitepaper PDF.

Why it stays in the active corpus

• Good comparison class for vault control planes, liquidity direction systems, and automated capital allocators where offchain search is bounded by onchain policy.
• Useful for thinking about where authority sits when solver discovery, strategy gatekeeping, reward liquidation, and destination selection are deliberately separated.
• Distinct enough from generic yield aggregators to help with later comparisons against curator-driven vault frameworks, ALM systems, and programmable-liquidity allocators.