One signature creates the whole launch

D17Factory.createLaunch receives the complete token metadata, supply split, treasury, five-round schedule, floors, refund terms, settlement duration, and unsold-token policy.

Within one transaction the suite:

1. validates hard field, timing, allocation, and basis-point bounds;
2. deploys the token;
3. deploys the launch;
4. deploys the launch's liquidity vault;
5. wires their immutable and one-time relationships;
6. mints sale/LP supply to the launch, creator distribution to the caller, and dead allocation to the canonical address;
7. configures token metadata and trading gate;
8. closes minting and renounces token ownership; and
9. records the launch and rules hash as canonical.

If any step fails, the transaction reverts and none of the launch is created. There is no interval where an independently deployed token waits for an operator to wire the sale correctly.

The cost of atomic immutability is intentional: a typo or poor economic choice cannot be edited afterward. The deploy page therefore validates and simulates before opening the wallet, and deployers should still inspect every decoded tuple field before signing.