Operate the lifecycle
The creator can help the launch progress, but no required end-stage action depends on the creator.
During rounds
There are no owner controls to extend, shorten, pause, reprice, or reallocate a live launch. Publish the schedule clearly and monitor the same on-chain state as participants.
Finalize
After round 5 closes on a launch that met its success conditions, call finalizeLaunch() or let any other address call it. The transaction fixes successful-launch accounting and unsold-sale handling. The creator has no special result.
A launch that permanently failed does not need and cannot use successful finalization: finalizeLaunch() reverts, and lockers instead use the permanent failed-launch refund path.
Settlement grace
Owners can settle their lockers as soon as the launch is finalized. At poolCreationOpensAt, anyone can call settleAfterGrace for a known locker, with proceeds still credited to that locker.
An operator may run a permissionless sweep over known lockers before pool creation to maximize initial pool depth. This is an operational convenience, not a liveness requirement.
Create the official pool
Once the grace boundary opens, anyone may call the vault's createOfficialPool(minLpMinted, deadline). Use a current deadline and a defensible minimum-LP bound. The pool must not already be live and cannot be preseeded with the D17 token.
Initial pool composition is proportional to already settled liquidity WETH. Unsettled lockers retain a reserved LP-token share inside the launch.
After trading opens
Late settlement remains available. Each late settlement atomically moves the locker's liquidity WETH and reserved token share into the official pair, minting LP to the vault. Do not describe allFinalCommitmentsSettled as a creation gate; it is an informational metric.