Space on Solana is not a vague cloud allotment. When an account is created, the transaction asks for a data length. Those bytes are reserved. The account must hold enough lamports to be rent-exempt for that length, or it is not a healthy place to store state.
The rent-exempt minimum rises with size. A larger data array costs more lamports to keep. Beginners often copy a number from a sample and never ask what the number is buying. At the week-five sitting we compute one figure together from a published minimum and a chosen byte length, then write the sentence: this many bytes, this many lamports, this owner.
Empty space is still space
Unused bytes in the allocation still count. Asking for a generous buffer 'just in case' ties up lamports for the life of the account. Asking for too little means a later resize, which is a separate conversation and a poor first design. The desk teaches a modest habit: size the account for the fields you can name, and leave a note in the margin if you are guessing.
Rent is a storage idea, not a fee for calling
People mix rent with the fee paid to land a transaction. The transaction fee compensates the cluster for processing. Rent-exempt lamports stay in the account so the data can remain. When you close an account, the lamports can move back to a recipient you name, subject to the rules of the owner program. That closing step is mentioned in the circle and practiced at home, not rushed on a Tuesday.
If the arithmetic in week five feels short, book the follow-up desk hour for that figure alone. Several learners have done exactly that, and the notebook usually needs only one corrected line.
See the Beginner Concept Desk if you want these chapters read with a group.