> For the complete documentation index, see [llms.txt](https://whitepaper.surge.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.surge.xyz/about/introduction/overview.md). # Overview Surge’s advantage is the tight integration of three pillars into a single operating system for AI-native venture creation: * **Launch Protocols -** programmable, fair token fundraising that replaces slow, gatekept equity rounds with open, audited, on-chain sales (Fairlaunch, Ignition, Gated). This is a deliberate shift away from the “low-float, high-FDV” meta that extracts value from communities and constrains sustainable growth. * **AI Foundry -** TBA. * **Knowledge & IP Systems** - a transparent framework that captures, and reuses collective intelligence. Through the **IP Bank** and builder data layer, every product, model, and insight becomes part of a shared innovation graph - allowing teams to build faster, investors to assess value more accurately, and the ecosystem to continuously evolve from each new contribution. AI is the execution engine; Web3 is the trust and liquidity layer. Together, they transform Surge from a “launchpad” into the **operating** **system** for AI-native capital formation. --- # 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://whitepaper.surge.xyz/about/introduction/overview.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.