Open-source Knowledge Compiler for AI agents. Built in Rust. MCP. AI Infrastructure. TG: https://xitter.cf/t.co/MtIyMbZffa

Joined August 2026
EKOS Technical Progress & Tokenomics 2.0 One engineer. 100 days. 508 commits. And we’re just getting started. 🚀 Could your software engineers work this effectively? I ran ZAUTH on my open-source project, EKOS, for the second time. 📊 Aug 23 → Oct 19 • 126 → 508 commits • ZAUTH score: 73 → 74 • Zero external code matches reported • No high-risk security patterns flagged 4x the commits. Real engineering progress. Here’s what sits behind those numbers: 🧠 Original Engineering • fact_ledger.rs: A custom log-structured storage engine built for time-travel queries. • semantics.rs: Business semantics synthesis with Git-blame-based hypothesis tracking. • cross_system.rs: Cross-database identity resolution using Jaro-Winkler and Jaccard scoring. 🛡 Built with Safeguards • Consistent Result error handling • Token validation on the setup server • Defensive coding practices designed to reduce common attack vectors ✅ Tested Where It Matters • Unit and integration tests across major modules • Time-travel edge cases and cross-database identity collisions • AI agents using MCP cannot resolve conflicts autonomously. That decision stays with humans. 📐 Architecture Before Implementation • RFC-driven development • A modular Rust workspace spanning ledger, identity, CLI, EKL, and distributed components This isn’t about chasing commit counts. It’s about building infrastructure engineers can actually use to bridge legacy systems and AI. And this is where solana:CwubepDFJndzSKFmAMAm9u8Xx3PrizAwSq8hcGimpump becomes part of the bigger picture. We’re building the technology first. At the same time, we’re exploring how the ecosystem can better recognize and reward meaningful contributions—from development and testing to community participation. That’s the thinking behind the ongoing Tokenomics 2.0 discussions: aligning the long-term interests of builders, contributors, and the wider EKOS community. The goal isn’t just to launch a token around an idea. It’s to build something real—and develop an ecosystem worthy of growing around it. More engineering. More transparency. More opportunities for the community to contribute. EKOS is open source. We’re building in public. And we’re far from done. 🔥 🔗 ZAUTH: zauth.inc/reposcan/scan/cmvf… 💻 GitHub: github.com/alexeyban/EKOS/ solana:CwubepDFJndzSKFmAMAm9u8Xx3PrizAwSq8hcGimpump #Rust #OpenSource #AI #DataEngineering @IBM @Dell @intel @AnthropicAI @UberEng @micro1_ai @pentagoniac @databricks
14
11
1
40
5,066
Ekos Project retweeted
AI reliability requires more than a powerful model. It requires structured, traceable knowledge. EKOS is an open-source knowledge compiler that turns code, SQL, documentation, and Git history into evidence-backed knowledge for AI agents. Our first reproducible benchmark, run against a real 2,022-file repository, measured 67–93% fewer tokens for specific knowledge-retrieval tasks compared with raw-source approaches. Methodology, commands, and raw outputs are publicly available: alexeyban.github.io/EKOS/pre… The next step for AI is not just smarter models — it’s better context and verifiable engineering knowledge. github.com/alexeyban/EKOS
3
7
57
Buy the $EKOS | @ekosproject dip. Scoop them up like they’re running away. $EKOS ➡️ An open-source knowledge layer for AI agents, turning fragmented code, databases, documentation and Git history into a structured, evidence-backed knowledge system that AI agents can query and verify. Think fewer hallucinations, traceable answers and more efficient AI workflows. The compiler is live. The bigger vision? A knowledge network, plugin marketplace, AI agent economy and enterprise infrastructure with $EKOS designed to reward contributors and power ecosystem transactions as adoption grows. That’s why I’m watching this one. Real infrastructure, an expanding roadmap and a token utility thesis that could strengthen with usage. I’ve seen promising projects get overlooked before the market catches on. If $EKOS executes and adoption follows, today’s dip could look very different in hindsight. Accumulate with conviction. The vision is promising. $EKOS | @ekosproject
solana:CwubepDFJndzSKFmAMAm9u8Xx3PrizAwSq8hcGimpump
4
3
20
1,089
A pipeline that says “success” is one thing. A pipeline that can prove it caught a failure is another. 🧪⚡ That’s the difference between simply moving data and building infrastructure you can trust. 🏗️🔐 In the EKOS Lakehouse demo: 🔎 We deliberately introduce a data discrepancy and test whether the system catches it. 🔄 We reconcile data across source, bronze, and silver layers. 🌿 Schema changes become reviewable Git branches, making downstream impact visible. 🧠 When data definitions are ambiguous, the system asks instead of guessing. No blind trust. Just verifiable checks, traceable changes, and engineering you can inspect. 🔍✅ This is how open-source infrastructure earns trust: by making verification part of the process, not an afterthought. 🚀 🎥 Watch the demo: youtu.be/EGpYzn_-fv4 💻 Explore the code: github.com/alexeyban/ekos-la…
PostgreSQL → Apache Iceberg. What does real infrastructure look like when data integrity, traceability, and verification are built into the workflow? The EKOS Lakehouse demo puts that question into practice. Using the Pagila sample database, the project demonstrates how a data pipeline can generate its own code, move data through a structured lakehouse workflow, verify loaded data against its source, and surface schema changes for review. Here’s what happens in the demo: → Incremental loading: Tables are loaded incrementally when the declared watermark logic is supported by the required database trigger. Otherwise, the pipeline explains why a full load is needed. → Data reconciliation: Row counts, per-column aggregates, and 64-bucket checksums help verify consistency across the pipeline. → Failure detection: A deliberately planted discrepancy tests whether the reconciliation process catches a real difference. → Controlled schema evolution: A new nullable column can be applied automatically, while a column rename becomes a reviewable Git branch with its downstream impact identified. → Knowledge-driven data modeling: Describe a gold data mart in plain language. If a requested metric is ambiguous or a column is missing, the system asks for clarification instead of inventing an answer. The result is a more transparent approach to data engineering—where generated code, verification, change review, and explicit limitations are part of the process. Built with Trino, Polaris, dbt, and Dagster. The demo also documents known limitations: PostgreSQL sources only, and manual execution of the ledger compilation step. 14 minutes. Real execution. Verifiable results. @AnthropicAI @IBM @Dell @intel @UberEng @FactoryAI @micro1_ai @MSCloud @Google Watch the demo: youtu.be/EGpYzn_-fv4
3
6
1
15
424
Ekos Project retweeted
PostgreSQL → Apache Iceberg. What does real infrastructure look like when data integrity, traceability, and verification are built into the workflow? The EKOS Lakehouse demo puts that question into practice. Using the Pagila sample database, the project demonstrates how a data pipeline can generate its own code, move data through a structured lakehouse workflow, verify loaded data against its source, and surface schema changes for review. Here’s what happens in the demo: → Incremental loading: Tables are loaded incrementally when the declared watermark logic is supported by the required database trigger. Otherwise, the pipeline explains why a full load is needed. → Data reconciliation: Row counts, per-column aggregates, and 64-bucket checksums help verify consistency across the pipeline. → Failure detection: A deliberately planted discrepancy tests whether the reconciliation process catches a real difference. → Controlled schema evolution: A new nullable column can be applied automatically, while a column rename becomes a reviewable Git branch with its downstream impact identified. → Knowledge-driven data modeling: Describe a gold data mart in plain language. If a requested metric is ambiguous or a column is missing, the system asks for clarification instead of inventing an answer. The result is a more transparent approach to data engineering—where generated code, verification, change review, and explicit limitations are part of the process. Built with Trino, Polaris, dbt, and Dagster. The demo also documents known limitations: PostgreSQL sources only, and manual execution of the ledger compilation step. 14 minutes. Real execution. Verifiable results. @AnthropicAI @IBM @Dell @intel @UberEng @FactoryAI @micro1_ai @MSCloud @Google Watch the demo: youtu.be/EGpYzn_-fv4
7
10
3
38
3,472
I left @Apple to build healthcare that listens and acts early. Today, I'm excited to introduce UniqueHuman. We're building proactive healthcare agents that handle every step of care for people with chronic conditions. Our mission is to end chronic suffering. Today, we begin with migraines.
292
558
121
3,656
902,104
Ekos Project retweeted
Replying to @OMID_0909 @Apple
means a lot Ekos
2
2
2
79
Replying to @OMID_0909 @Apple
agreed, and boundaries are the part people skip. our agent is deliberately limited in what it can do on its own, everything it says is grounded in your own data, and we treat evals as production infrastructure rather than a qa step
2
3
9
2,273
When AI Moves from Prediction to Action medium.com/@Omid.EKOS/when-a…
I left @Apple to build healthcare that listens and acts early. Today, I'm excited to introduce UniqueHuman. We're building proactive healthcare agents that handle every step of care for people with chronic conditions. Our mission is to end chronic suffering. Today, we begin with migraines.
2
14
583
Ekos Project retweeted
AI agents don’t just need better intelligence. They need proof. RAG can retrieve. Models can reason. But who compiles enterprise knowledge, preserves its provenance, and makes every claim verifiable? That’s the problem EKOS is built to solve.
5
3
1
10
879
PostgreSQL → Apache Iceberg. What does real infrastructure look like when data integrity, traceability, and verification are built into the workflow? The EKOS Lakehouse demo puts that question into practice. Using the Pagila sample database, the project demonstrates how a data pipeline can generate its own code, move data through a structured lakehouse workflow, verify loaded data against its source, and surface schema changes for review. Here’s what happens in the demo: → Incremental loading: Tables are loaded incrementally when the declared watermark logic is supported by the required database trigger. Otherwise, the pipeline explains why a full load is needed. → Data reconciliation: Row counts, per-column aggregates, and 64-bucket checksums help verify consistency across the pipeline. → Failure detection: A deliberately planted discrepancy tests whether the reconciliation process catches a real difference. → Controlled schema evolution: A new nullable column can be applied automatically, while a column rename becomes a reviewable Git branch with its downstream impact identified. → Knowledge-driven data modeling: Describe a gold data mart in plain language. If a requested metric is ambiguous or a column is missing, the system asks for clarification instead of inventing an answer. The result is a more transparent approach to data engineering—where generated code, verification, change review, and explicit limitations are part of the process. Built with Trino, Polaris, dbt, and Dagster. The demo also documents known limitations: PostgreSQL sources only, and manual execution of the ledger compilation step. 14 minutes. Real execution. Verifiable results. @AnthropicAI @IBM @Dell @intel @UberEng @FactoryAI @micro1_ai @MSCloud @Google Watch the demo: youtu.be/EGpYzn_-fv4
7
10
3
38
3,472
Ekos Project retweeted
It takes a rare combination of conviction, patience, and hard-earned experience to build something this complex—and your perspective makes clear just how much is involved beyond the technology itself. I completely agree: better predictions alone won’t transform chronic care. Sustained behavioral change, longitudinal context, clinical validation, coordinated execution, and sustainable economics all have to work together. That’s what makes this such a difficult problem, and why solving it requires more than another AI model or point solution. What stands out to me is that you chose to build through that complexity rather than wait for the market to catch up with what you already understood. There’s still so much work to do, and I believe the next step forward will come from people and systems that can bring complementary capabilities together around real-world outcomes. After everything you’ve built, I’d imagine you know better than most how valuable the right infrastructure and collaborators can be. We’re always interested in contributing where our work can help move that mission forward. Respect for the journey—and thank you for sharing the reality behind it. 🫂🤝
Replying to @ekosproject
It’s like one of our 350 internal briefs that could only have been written if you suffered through and lived for ten years decade. This is one of the most comprehensive assessments I’ve read. You hit all the primary challenges with precision. Adherence alone is 50% of worldwide treatment failures. Of 8.3B it’s 1 in 3 with multiple morbidities. Poly pharmacy is a huge issue and with gradually declining liver and kidney function while aging, response to treatment changes over time. Early identification requires more than an app or point solution (device). And the AI meeting reality is a big one. Longitudinal data is important, but which data? Everyone has a data point or two they claim is the gold standard, but for long term chronic disease management and early ID, the correct layers and insights matter. There’s another big challenge beyond capturing utilization and engagement that doesn’t drop off. You need to be able to drive sustained behavioral change. That is far more difficult and requires a tall stack of techniques, skills, capabilities, and coordination that challenges the economics as much as the efficacy. These are the most difficult metrics. So is time. Years to build POC. Years to refine and optimize before scale. Years to validate efficacy. Not a 2 year old dated IRB study. It needs to be “here are thousands of patients under daily support, let’s see the data and outcomes in real time. We just caught a medication contradiction. This patient at this moment is having suicidal ideation right now.” Once validated at adequate enough scale, various payer approvals may take another 1-3 years. Your VC/PE firms start burning out at 4 years. big hyper scalers lose focus and remain with essential business models. Finally, head count is a sort of it. This cannot be a pure SaaS model. I used to run into the guys at Sequoia and Summit Partners. They told me if you’re adding headcount in your growth model you’ll never get funded and the business model will never succeed. People expect SaaS level margins. I told him once optimization was finished we’d achieve it. They said I was crazy. About three months ago, Sequoia published their new investment thesis and suddenly shifted their tune. They said Services built over the AI as the proper model. For every one dollar you receive in Software you receive six dollars in Services. We learn over time. We ultimately had to start building many years ago. We didn’t have time to wait for venture capitalist to figure out what we believed we already knew. So $165 million later here we are. We own it. We’re shipping. But it was so damn complicated I would never go back and do it all again. :)
3
15
382
Ekos Project retweeted
Replying to @ekosproject
It’s like one of our 350 internal briefs that could only have been written if you suffered through and lived for ten years decade. This is one of the most comprehensive assessments I’ve read. You hit all the primary challenges with precision. Adherence alone is 50% of worldwide treatment failures. Of 8.3B it’s 1 in 3 with multiple morbidities. Poly pharmacy is a huge issue and with gradually declining liver and kidney function while aging, response to treatment changes over time. Early identification requires more than an app or point solution (device). And the AI meeting reality is a big one. Longitudinal data is important, but which data? Everyone has a data point or two they claim is the gold standard, but for long term chronic disease management and early ID, the correct layers and insights matter. There’s another big challenge beyond capturing utilization and engagement that doesn’t drop off. You need to be able to drive sustained behavioral change. That is far more difficult and requires a tall stack of techniques, skills, capabilities, and coordination that challenges the economics as much as the efficacy. These are the most difficult metrics. So is time. Years to build POC. Years to refine and optimize before scale. Years to validate efficacy. Not a 2 year old dated IRB study. It needs to be “here are thousands of patients under daily support, let’s see the data and outcomes in real time. We just caught a medication contradiction. This patient at this moment is having suicidal ideation right now.” Once validated at adequate enough scale, various payer approvals may take another 1-3 years. Your VC/PE firms start burning out at 4 years. big hyper scalers lose focus and remain with essential business models. Finally, head count is a sort of it. This cannot be a pure SaaS model. I used to run into the guys at Sequoia and Summit Partners. They told me if you’re adding headcount in your growth model you’ll never get funded and the business model will never succeed. People expect SaaS level margins. I told him once optimization was finished we’d achieve it. They said I was crazy. About three months ago, Sequoia published their new investment thesis and suddenly shifted their tune. They said Services built over the AI as the proper model. For every one dollar you receive in Software you receive six dollars in Services. We learn over time. We ultimately had to start building many years ago. We didn’t have time to wait for venture capitalist to figure out what we believed we already knew. So $165 million later here we are. We own it. We’re shipping. But it was so damn complicated I would never go back and do it all again. :)
1
2
1
6
470
Ekos Project retweeted
Crypto moves fast. Infrastructure is what lasts. While the market watches price, we’re focused on what gets built beneath the surface. Real systems. Verifiable data. Open-source infrastructure. @ekosproject is building beyond the narrative. More soon. 👀
4
6
28
453
AI can predict risk. But prediction alone cannot deliver better care. Chronic disease management exposes a deeper challenge: turning AI-generated insights into reliable, coordinated action over time. In our latest article, we explore three critical gaps: → Prediction is not understanding. Detecting a pattern does not establish its cause—or prove that acting on it is appropriate. → Longitudinal data is not longitudinal understanding. More data does not automatically mean better context or better decisions. → Intelligence is not execution. Better care depends on clinical judgment, sustained patient engagement, coordinated workflows, and safe escalation—not just smarter models. The real challenge is not simply building AI that anticipates what might happen. It is building systems that help translate evidence into appropriate action, consistently and safely. For AI researchers and healthcare professionals alike: What is the biggest barrier between AI insight and better patient outcomes? @tdohrmann @OMID_0909 @PraneetaPujari @CorrelationVC @AntlerGlobal @anamitra @gshewakr @WHO @OpenAI @AnthropicAI @elonmusk Read the full article: medium.com/@Omid.EKOS/when-a…
5
7
5
31
2,898
We’ve spent a long time thinking about how systems understand what already exists. Now, we’re looking at a different question: What happens when that understanding starts to shape what comes next? 🦾 A new domain. A different kind of complexity. The same principle: Evidence first. Intelligence follows. EKOS is moving into new territory. More soon......🧐
4
9
29
610
Ekos Project retweeted
Correct. And chronic disease becomes very complex. Early ID, daily adherence, escalation management, FDA devices, caregiver support, social isolation and loneliness, countless staffing models, workflows, diverse automation, endless disease states and combos, huge numbers of plans of care, payer models and approvals, and you need unwavering, persistent engagement and utilization, layers of longitudinal data managed, and expect five-ten years of process improvements, optimization for care and economics, TeleCare infrastructure behind the tech, and a very sophisticated and diverse operational infrastructure.
3
3
3
92
🚨 IT’S OFFICIAL. EKOS IS ON @coingecko ! 🚀🔥 A major milestone for the EKOS ecosystem. solana:CwubepDFJndzSKFmAMAm9u8Xx3PrizAwSq8hcGimpump is now listed on CoinGecko! 💎 This is more than a listing. It’s another step forward in our journey to build something bigger — an ecosystem driven by technology, transparency, and community. ⚡ A stronger presence. 🌍 Greater visibility. 🧠 A vision that keeps moving forward. We’re building, improving, and pushing EKOS toward its next chapter. And this is only the beginning. To everyone who has supported us, contributed, and believed in what we’re building: THIS MILESTONE IS YOURS TOO. 🤝❤️ The journey continues. The vision gets bigger. The work never stops. EKOS IS MOVING FORWARD. THE WORLD IS STARTING TO NOTICE. 🚀💎 🔎 Find solana:CwubepDFJndzSKFmAMAm9u8Xx3PrizAwSq8hcGimpump on CoinGecko: [coingecko.com/en/coins/ekos #EKOS #CoinGecko #Crypto #AI
11
13
44
1,269