Redeployment Timing

After a position settles, the operator has a window to identify and enter the next market.

Timing Rules

Metric	Value
Target redeployment window	≤ 7 days after settlement
Maximum before communication required	7 days

What Happens If Redeployment Is Delayed

If no suitable market is found within 7 days: - Capital remains in idleReserve - Vault operates with fewer active positions - Yield to investors decreases proportionally to the idle fraction - The operator must communicate this to stakeholders

If all 4 slots are idle: - Vault earns zero yield - Investors hold a stablecoin-equivalent position subject to the 0.5% exit fee - The operator must communicate this immediately — investors are paying an exit fee for zero yield

Why 7 Days

Seven days provides: - Enough time to screen markets without rushing - A reasonable upper bound before investors reasonably expect to see a new position - Alignment with the rebase cooldown (also 7 days) — decisions are made on weekly cadence

Pre-Screening

To minimize redeployment gaps, the operator should maintain a pipeline of pre-screened markets before existing positions approach maturity. Best practice: - Begin screening candidates when a position has ≥ 21 days remaining - Have a confirmed candidate ready by the time a position has ≤ 7 days remaining - Deploy the adapter contract while the current position is still active (adapter deployment is independent of openPosition())