How to read a launch page in ninety seconds

Start at the stack. Every launch names its blueprint and the blueprint names its blocks, in the canonical order, with the parameters printed. If a page ever showed you a hook you could not expand into numbers, that page would be broken; the registry does not store unreadable stacks.

Next, the status chip. Pool means graduated: the LP position is locked in the launchpad contract and the rules are frozen. Curve with a tranche count means you are early, which cuts both ways: tranche two is cheap, and tranche two is also a market that has not yet proven anyone else wants tranche three.

Then the overhead figure. It is computed by the same composition the contract runs, as a view function, so a third party can requote it. If someone quotes you a different number in a chat, the view function is right and the chat is wrong. This is most of what deterministic means in practice.

Last, the things that are deliberately absent. There is no lock-duration countdown, because there is nothing to unlock. There is no team allocation field, because the supply is fixed and printed. The page is short because the trust story is short: what you read is what runs.