# 2. Solution Planning

Next, Nyvo’s engine plans the dApp structure. The AI will decide what smart contracts are needed and what their functions should be, what the frontend should contain, and how users will interact with the system. For instance, if the prompt is to build a “voting system”, Nyvo will plan that it needs a smart contract to hold proposals and votes, and a frontend page for users to submit and view votes. Nyvo draws on a library of known design patterns for dApps during this planning (for example, recognizing that a “launchpad” usually involves a token sale contract and a vesting contract, or that a “marketplace” involves an escrow mechanism). This step might involve the AI performing reasoning or even doing research on standard implementations (Nyvo’s knowledge base is kept up-to-date with common Web3 practices). The outcome is an outline or pseudo-code for both contract and application – essentially a blueprint the AI will execute on.
