> For the complete documentation index, see [llms.txt](https://kerc.gitbook.io/kerc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kerc.gitbook.io/kerc/others/core-team.md).
# Core Team
## Joyerlah - Founder, Head of Project
A seasoned C-level executive in healthcare and marketing firms with a demonstrated history of delivering exceptional results. Joyerlah specializes in business development, corporate communications, client acquisition strategies, relationship management, investor relations, and resource planning.
Prior to KERC, Joyerlah worked for various public and private corporates and his work has been accorded various corporate awards. Joyerlah graduated from the University of South Australia and has been active in crypto, web3, and all things DeFI since 2018.\
\
Linkedin:
## **FEELitJEE - Head of Finance and Operations**
FEELitJEE specializes in corporate finance, M\&As, FP\&As, budgeting, and all things finance and investing. He has over 15 years of experience working in a variety of industries and different organizations, including startups, corporates, governments, and NGOs, which provided hands-on operation and market execution experience.
---
# 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://kerc.gitbook.io/kerc/others/core-team.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.