> For the complete documentation index, see [llms.txt](https://sply-1.gitbook.io/sply/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sply-1.gitbook.io/sply/template-lifecycle.md). # Template Lifecycle ## Template Lifecycle This page explains how a developer template moves from submission to becoming a public platform template. ### 1. Development The developer implements a deployer and token core path that satisfy platform requirements. ### 2. Submission The template is submitted through the developer submission flow and enters the review queue. ### 3. Review The admin side reviews: * the mechanism * interface completeness * parameter structure * obvious permission and lifecycle risks ### 4. Registration Approved templates are registered through `FactoryAdmin`, which stores the template in the on-chain registry with policy metadata. ### 5. Public listing Once registered, the frontend reads the template from the on-chain template set and exposes it to project owners. ### 6. Live use Project owners can now select the template, provide its parameter set, and launch through the platform. ### 7. Ongoing governance The platform can still manage whether the template remains enabled, which prevents the public template set from becoming unmanaged over time. *** ## Agent Instructions: 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: ``` GET https://sply.fun/daoi-docs-import/developer-template-guide/template-lifecycle.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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. --- # 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://sply-1.gitbook.io/sply/template-lifecycle.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.