> For the complete documentation index, see [llms.txt](https://docs.propfunding.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.propfunding.com/overview/about/core-contributors.md). # Core Contributors #### 🚀 Key Contributors Shaun Opoku Shaun brings a background in proprietary trading infrastructure, market modelling, and fintech entrepreneurship. He previously founded and exited Traders Central and now leads Prime Bridge Securities LLC, the infrastructure provider for PF. Shaun oversees protocol design, market making and ecosystem strategy.
Jose Villarroel Jose is responsible for building and maintaining the backend of Propfunding.com's technical stack. His work includes developing our internal risk algorithms, managing funded account books, and implementing performance tracking systems to ensure data reliability and pool safety.
Paula Opoku Paula leads core operations of the protocol, designing and managing systems for automated account issuance, client payout processing, and scaling day-to-day workflows. She also supports internal tooling, operations, and partner integrations. *** > 💬 Questions? Want to get involved? > Join us in[ Discord](https://discord.gg/8z37khrMA6) and help shape the future of prop funding. --- # 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.propfunding.com/overview/about/core-contributors.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.