> For the complete documentation index, see [llms.txt](https://docs.takadao.io/takadao-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.takadao.io/takadao-docs/part-b.-takadao-the-daos/05-tdaos-tokens-aka-membership-credits/membership-agreement.md). # Membership agreement Once Credits are obtained, assuming the member completes the underwriting process, the Credits are locked in a smart contract that represents the membership agreement. The smart contract defines the rights and privileges of membership, including the Benefit Multiplier assigned to the member. The Credits are locked up in the contract for the duration of the membership, i.e. 1, 5, 10, 20 years. Additional Credits from subsequent contributions will continue to be added to the smart contract. Credits continue to be locked in smart contracts while the membership is in force. Upon membership contract expiration and assuming no Benefit payouts were made, the locked Credits will be unlocked. Once the Credits are unlocked, membership privileges and the associated protection terminates. At this point, the member may: * Relock his Credits in a new insurance contract (phase 2) * Redeem his Credits against his share of the underwriting surplus as described in the next section --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.takadao.io/takadao-docs/part-b.-takadao-the-daos/05-tdaos-tokens-aka-membership-credits/membership-agreement.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.