A decade of learning where anyone could inspect the work.
This is not a wall of repositories. It is the progression that connected complete applications, developer tools, ML/NLP, product platforms, external OSS contribution, and public infrastructure.
- 5,972
- stars
- Across 38 source repositories owned by tortuvshin and intelligo-mn
- 1,206
- forks
- Repository forks received across the same public source set
- 56,794
- GitHub contributions
- Contribution calendar since 2014; 12,649 public and 44,145 private/restricted
- 392
- authored pull requests
- 149 public, 243 private; 359 merged overall
- 21
- independent npm packages
- Personal, Intelligo, dev.mn, and Grove families only
- 1,869,096
- cumulative npm downloads
- Official API total from first publication through 2026-07-21; not unique users
How the totals are scoped
Repository totals cover public, non-fork repositories owned by tortuvshin and intelligo-mn at the 2026-07-21 snapshot. Contribution-calendar and PR totals include private activity visible to my account; they do not expose private repository names. npm lists 53 packages where I am a maintainer across personal, employer, and collaborative scopes. The 21-package and download totals above deliberately include only the independently maintained personal, Intelligo, dev.mn, and Grove families. Maintainer status is not the same as sole authorship.
- 01 · 2016–2017
Complete applications were the curriculum
I learned by running and tracing entire PHP, Java, Android, and Node.js applications. Full systems exposed boundaries, data flow, deployment assumptions, and failure in a way tutorials could not.
ApplicationsReverse engineeringPublic learning - 02 · 2017–2019
Intelligo: from API to developer product
A Messenger framework grew documentation, examples, tests, Slack support, and a CLI. The main package accumulated 643,422 downloads; the five-package historical Intelligo family reached 1,384,024 through 2026-07-21.
FrameworkCLIMessengerSlack - 03 · 2017–2019
Neuro.js: applied ML before the current AI wave
Neuro.js moved the question from messaging APIs toward classification and learning for assistants in browser and Node.js environments. It became a companion layer, not a generic claim that Intelligo had “AI.”
ML/NLPBrowserNode.js - 04 · 2019–2021
The framework became a visual product
The third Intelligo generation moved up the stack into a drag-and-drop chatbot builder with API, simulator, studio, and web applications. The repository has a 2,195-commit history. I led it and remain the dominant human contributor; I was not the only contributor.
AngularNestJSProduct platform - 05 · 2023–2024
Fleetbase tested the method in somebody else’s system
I entered an unfamiliar logistics OSS stack and authored 46 PRs across ten repositories. Forty were merged. The work crossed SDKs, release tooling, storefront, mobile, dashboards, Laravel, and Ember surfaces.
External OSSLogisticsCross-repository - 06 · 2017 → 2026
Open Apps productized the way I learn
A curated list evolved into a structured directory of complete open-source applications. Its 4,334 stars carry the repository’s full history; they did not appear after the 2026 product rebuild. That continuity is context, not something to hide.
DiscoveryAstroStructured data - 07 · 2026
Grove extracted the repeated maintenance problem
Open Apps needed schemas, imports, validation, review workflows, generated data, and release tooling. Grove extracted those needs into core, UI, CLI, Astro, and documentation packages. Next.js and Svelte remain roadmap-only; external adoption remains the missing evidence.
Framework extractionCLIEarly adoption
The honest reading
Some projects found adoption. Some were abandoned. Some architectures grew before demand justified them.
The record still compounds: applications became libraries; libraries became products; product pain became infrastructure; and the learning returned to professional systems.