> For the complete documentation index, see [llms.txt](https://maurelles-organization.gitbook.io/vst-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://maurelles-organization.gitbook.io/vst-whitepaper/team.md).

# Team

**Core Team**

* **Marko Veber**: CEO | Business Analyst with over 8 years in IT, specializing in blockchain development and international management systems.
* **Ethan Mason**: CTO | Technical leader with expertise in cryptography and smart contract security.
* **Claire Warner**: Financial Consultant | 5+ years in financial advisory with a proven track record in blockchain finance.
* **William Cox**: Software Development | Expert in platform development and mobile application management.

**Advisors**

* **Darren Leonard**: Advisor to large enterprises in Western Europe and the US.
* **Pauline Rose**: Crypto fund manager with extensive industry experience.
* **Robert Parks**: Financial expert and advisor in crypto-exchange markets since 2010.
* **Gilbert Carr**: Technology advisor for global startups.


---

# 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://maurelles-organization.gitbook.io/vst-whitepaper/team.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.