> For the complete documentation index, see [llms.txt](https://docs.micro.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.micro.fun/team/core-leadership.md).

# Core Leadership

The Micro.fun project is led by a core team of four, combining years of experience across Web3 development, product strategy, and high-growth marketing.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><p><mark style="color:$warning;"><strong>Dogan Dinc</strong></mark></p><p><mark style="color:$warning;">CEO</mark></p><p><mark style="color:$warning;">(Vision &#x26; Management)</mark></p></td><td>Responsible for the overall vision, strategy, partnerships, and fundraising for Micro.fun.</td><td><a href="https://1774913162-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6STy4F4v1nYWL1U7D29v%2Fuploads%2Fv13w8rhmrhG8t8yBOuYD%2Fdogan.png?alt=media&amp;token=6a032801-2d96-4d49-826b-28f0eb667e77">dogan.png</a></td></tr><tr><td><p><mark style="color:$warning;"><strong>Eren Akkaya</strong></mark></p><p><mark style="color:$warning;">Full-Stack Developer</mark></p><p><mark style="color:$warning;">(Product &#x26; Engineering)</mark></p></td><td>Leads the development of the web app, infrastructure, and the core AI narrative integration. Guides the product direction and gameplay UI/UX.</td><td><a href="https://1774913162-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6STy4F4v1nYWL1U7D29v%2Fuploads%2F1ZLibpV7rQirMkJQ2WrX%2Feren.png?alt=media&amp;token=114320b2-4601-4556-9094-c819bd355cb0">eren.png</a></td></tr><tr><td><p><mark style="color:$warning;"><strong>Mert Can Mutlu</strong></mark></p><p><mark style="color:$warning;">Smart-Contract Developer</mark></p><p><mark style="color:$warning;">(On-Chain Architecture)</mark></p></td><td>Designs and architects the on-chain world of Micro.fun. Responsible for Solidity development, tokenomics design, and the core logic of the game mechanics, including the siphon.</td><td><a href="https://1774913162-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6STy4F4v1nYWL1U7D29v%2Fuploads%2FeWStT4tmyOPFl2fbuZSu%2Fmertcan.png?alt=media&amp;token=16b12d19-d745-4e82-bfd5-330f4dcc26f3">mertcan.png</a></td></tr><tr><td><p><mark style="color:$warning;"><strong>Tugrul Karakas</strong></mark></p><p><mark style="color:$warning;">Business Developer</mark></p><p><mark style="color:$warning;">(Growth &#x26; Partnerships)</mark></p></td><td>Leads business development and ecosystem growth for Micro.fun. Secures strategic partnerships (guilds, L2s, infra, creators), manages launchpad and marketplace relations from evaluation to listing, and negotiates revenue deals and distribution channels to scale adoption.</td><td><a href="https://1774913162-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6STy4F4v1nYWL1U7D29v%2Fuploads%2Fr6cz1m6XPHp9QlvPAqsl%2Ftugrul.png?alt=media&amp;token=7262fb3b-f000-45fa-8158-6b6936acf02e">tugrul.png</a></td></tr></tbody></table>


---

# 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.micro.fun/team/core-leadership.md?ask=<question>&goal=<endgoal>
```

`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.