Ecosystem
The project should be legible to more than one audience
DELIGHT already touches developer, privacy, protocol, and tool-builder narratives. This page makes that map explicit.
Developers
Need self-hosted control, low-cost compute, clear docs, and a credible path to integrations.
Privacy community
Care about routing privacy, reduced platform dependence, and language that takes anonymity seriously.
Web3 / protocol crowd
Care about standards, category formation, composability, and infrastructure that can evolve into a network.
Tool ecosystems
MCP- and OpenClaw-style integration paths make DELIGHT legible as a backend and execution surface.
Expansion path
- Public docs and protocol clarity.
- Contributor and community entry points.
- Integration surface for tools and agents.
- Grants, inbound interest, and ecosystem alignment.