Skip to main content
Business Case · 06

Next Steps

Immediate (0–2 weeks)​

  • Public npm release of @nirnex/cli, @nirnex/core, @nirnex/parser
  • Landing page live at nirnex.ai
  • Documentation site deployed to GitHub Pages
  • Alpha tester outreach — 50 developers from personal network and HN

Short-term (2–8 weeks)​

  • LSP integration — in-process TypeScript language service for Tier 2 retrieval
  • Ground truth review UI — simple web UI for the review queue (currently CLI only)
  • JavaScript support — tree-sitter-javascript parser for JS-only projects
  • First calibration cycle with alpha tester data

Medium-term (8–16 weeks)​

  • Team sync — optional encrypted trace export for shared calibration (opt-in only)
  • GitHub Actions integration — gate results automatically feed back into the index from CI
  • Pro tier launch — Stripe integration, upgrade flow from CLI
  • Python parser — tree-sitter-python for cross-language monorepos

North Star​

10,000 weekly active indexers within 12 months of public launch. At that scale, calibration data becomes statistically significant enough to begin training intent detection improvements.

What Success Looks Like at 90 days​

  1. 500+ developers have run nirnex index at least once
  2. 50+ developers have a post-commit hook running daily
  3. 5+ teams have completed a full calibration cycle
  4. Net Promoter Score ≥ 40 from survey of active users