---
title: "Roadmap"
description: "Designs that are specified against the deployed contracts but not yet built. What each one adds, what it reuses, and what still has to be proven."
audience: both
type: reference
status: design
lang: en
updated: "2026-09-06"
publish: true
---

# Roadmap

> **Nothing on these pages is deployed.** Every other section of these docs describes shipped behaviour and is written against live contracts. This section does not. Pages here are design specifications: they are written in the present tense because they are complete and specified against the contracts as deployed, not because the feature exists. Each page names what is built today, what is not, and what has to be proven before it can be.

Designs reach this section once they are specified precisely enough to be audited and costed, and once the mechanism they rest on is verified in the deployed code rather than assumed. That bar is deliberate. A design that still needs a core-contract change, or that rests on an unverified property of the pricing engine, is not ready to be published as a plan.

| Page | Content |
|------|---------|
| [Total Return Swaps](/docs/6-1-total-return-swaps) | Leveraged directional exposure built on the liability-swap primitive: margin accounting, coverage as the utilization curve, skew-based funding, and progressive deleveraging |
| [Single-Asset Vaults](/docs/6-2-single-asset-vaults) | One vault per asset allocating across every pool that lists it, as a Morpho Vaults V2 adapter: the allocation signal, the circularity rule, and why Pendle tokenization is not currently viable |

The mechanism these build on is documented under [AIMM](/docs/1-overview). Where a roadmap page depends on a property of that mechanism, it links to the page that establishes it.