EKOS — Enterprise Knowledge Operating System
Token utility, earned — not promised.
EKOS aims to become the operating system for enterprise knowledge. The EKOS
token is designed to coordinate, reward, and sustain the people who build that infrastructure —
its relevance is meant to grow the same way the platform's usefulness grows: as a consequence
of adoption, never as a claim about future price.
contribute knowledge→
platform gets more useful→
token utility grows
§ 01 / principle
The one sentence that governs everything below
The token is a coordination mechanism, not the goal of the project.
VISION.md — guiding principle
"EKOS exists to build an open
knowledge infrastructure for
enterprise AI. The EKOS token
exists to coordinate, reward, and
sustain the people who build that
infrastructure."
This document deliberately avoids describing the token in terms of future price. Instead
it describes what the token is for at each stage of the platform — utility that
compounds with real usage, the same way the Canonical Knowledge Model itself compounds
with every source system connected.
§ 02 / phases 1–3
Contributors first
Community, then a knowledge network, then a marketplace to sell into.
- Phase 1 — CommunityOpen source, docs, discussions. Token rewards bug reports, docs, parsers, connectors, tutorials, moderation. Contribute knowledge → earn EKOS.
- Phase 2 — Knowledge NetworkUsers extend recovery coverage — SQL, Pentaho, dbt, metadata. Token funds community grants, contributor rewards, bounties, plugin development.
- Phase 3 — Plugin MarketplaceAny developer publishes a parser, connector, prompt pack, or agent, attributed by name. Free or premium; premium is priced and paid in EKOS, to the author.
§ 03 / phases 4–6
Where enterprises start paying
Utility that only matters once a company is already on the platform.
- Phase 4 — Enterprise AI PlatformA company connects GitHub, Postgres, Confluence, Databricks, Synapse, Pentaho; EKOS compiles a Knowledge Graph AI can query. AI credits, premium agents, cloud processing, and knowledge packs can be paid in EKOS alongside fiat.
- Phase 5 — AI Agent MarketplacePublished, authored agents — Pentaho Migration Agent, SQL Optimizer, Databricks Reviewer, Data Lineage Explorer. The author earns EKOS when others use the agent.
- Phase 6 — Knowledge MarketplaceCompanies license curated Knowledge Packs for legacy ecosystems — SAP, Oracle EBS, Snowflake, Fabric, dbt — instead of rebuilding that recovery coverage themselves. Paid in EKOS.
§ 04 / phases 7–9
Governance without letting a large wallet buy influence
Reputation gates what a token balance alone cannot.
- Phase 7 — GovernanceScoped to product decisions, not a general DAO — e.g. which legacy-format parser to build next (Talend, SSIS, ADF, Fabric). Voting weight tied to EKOS.
- Phase 8 — ReputationReputation is tracked separately from token holdings. Becoming a maintainer requires reputation and a modest EKOS stake — large holdings alone don't confer influence without a track record of contribution.
- Phase 9 — Enterprise MarketplaceA company posts a need ("Pentaho migration"); the community responds; the company picks a winner, paid in EKOS.
§ 05 / the mechanism
Not proof of work. Not proof of stake.
Proof of Knowledge.
Anyone can contribute knowledge — a parser, a lineage mapping, documentation, a schema
mapping, an ontology, an agent, a connector. The more useful the contribution, the more
EKOS it earns. The token is the distribution mechanism for value moving between the
people who create knowledge and the people who use it — not a bet on the loop happening.
the loop
Knowledge
↓
AI becomes smarter
↓
Platform becomes more valuable
↓
More companies use EKOS
↓
More contributors join
↓
More knowledge
§ 06 / roadmap
Ordered by dependency, not by date certainty
A marketplace needs contributors before it needs buyers.
| Year | Focus |
|---|
| 2026 | Open source platform · Community · Parser SDK · Contributor rewards · GitHub knowledge graph |
| 2027 | Plugin marketplace · Agent marketplace · Cloud AI credits · Premium knowledge packs · Governance |
| 2028 | Enterprise marketplace · Knowledge economy · Third-party agent ecosystem · Public knowledge graph · Cross-company knowledge sharing |
Read the source documents
Vision and tokenomics are two separate documents on purpose.
| Doc | Covers |
|---|
| VISION.md | Product direction and phased token utility — what the token is for at each stage |
| TOKENOMICS.md | Supply, allocation, vesting — current facts, kept up to date on a best-effort basis |