71 lines
3.4 KiB
Markdown
71 lines
3.4 KiB
Markdown
**Language:** [Русский](../ru/team.md) | [English](team.md)
|
||
|
||
---
|
||
|
||
# Team
|
||
|
||
**Navigation:** [← Contents](../README.md) · [Contacts](CONTACTS.md) · [Glossary](GLOSSARY.md) · [Governance](governance.md)
|
||
|
||
---
|
||
|
||
The VC HB3 Accelerator team is **token holders** (the founder among them, with the largest share) and **AI tools** in the DLE platform. There is no traditional payroll: the product and ecosystem are built on on-chain voting by holders, contractor tasks, and product coordination.
|
||
---
|
||
|
||
## 1. Core: founder
|
||
|
||
**Alexander Viktorovich Tarabanov** — developer of the DLE platform, architect of the VC HB3 Accelerator ecosystem, and the contact person’s CEO (LLC “ERAYTI” is the license seller in the Russian Federation).
|
||
|
||
- Sole developer and architect of DLE from day one; coordinates product, documentation, and partner discussions (hubs, regulators)
|
||
- Leads negotiations with hubs and regulators and coordinates pilots; contractors and experts are brought in as needed (development, setup, resident support)
|
||
- Largest token holder (70% of governance tokens); decisions on development are made via on-chain voting among token holders
|
||
|
||
Contact: [CONTACTS.md](CONTACTS.md).
|
||
|
||
---
|
||
|
||
## 2. AI models and technology
|
||
|
||
**AI models** (including cloud and local) are used in product development and support. They are not legal entities or “employees” but act as tools for analysis, prototyping, and documentation.
|
||
|
||
**In the DLE platform:**
|
||
- **AI agents** — specialized assistants for business processes (customer service, analytics, HR, etc.). They run on local models (Ollama); data stays on the client’s server (on-premises).
|
||
- One model, many agents: each agent is defined by its prompt, rules, and knowledge base.
|
||
|
||
More: [Glossary](GLOSSARY.md) (AI agents, RAG, Ollama), [sandbox description](sandbox-description.md) (Technology architecture).
|
||
|
||
---
|
||
|
||
## 3. Token holders and community
|
||
|
||
**Token holders** own governance tokens or admin tokens; the founder is one of them (70%). They contribute to the platform and fund through on-chain voting, tasks, and expertise.
|
||
|
||
| Role | Description |
|
||
|------|-------------|
|
||
| **LP (investors)** | Receive governance tokens, voting rights, and co-investment access. Effectively become GP. |
|
||
| **Customer** | Holder who publishes tasks for development and support. Payment from the treasury (15% of costs). |
|
||
| **Contractor** | Holder who executes customers’ tasks. Payment from the treasury. |
|
||
| **Flexible network** | Mentors, lawyers, regional operators — engaged as needed; not necessarily holders. |
|
||
|
||
Governance (quorum, voting, balance of rights): [governance.md](governance.md). Terms: [GLOSSARY.md](GLOSSARY.md).
|
||
|
||
---
|
||
|
||
## 4. Why this structure
|
||
|
||
- **Scale without linear headcount growth:** one coordinator plus AI plus a community of holders and contractors allows developing the product and launching sandboxes without a classic hierarchy; as the number of sandboxes and residents grows, the on-the-ground team can be expanded (regional operators, contractors from among holders).
|
||
- **Transparency:** voting and proposals are recorded in smart contracts; treasury and costs are described in the fund’s documents.
|
||
- **Alignment with the product:** DLE itself is built on on-chain governance and AI agents; the team reflects that model.
|
||
|
||
---
|
||
|
||
## See also
|
||
|
||
- [Contacts](CONTACTS.md)
|
||
- [For investors](for-investors.md) — “Team” and “Management model” sections
|
||
- [Governance](governance.md)
|
||
- [Glossary](GLOSSARY.md)
|
||
|
||
---
|
||
|
||
**Last updated:** 2026-02-27
|