Sprint 0 is closed.
When we started Meronq, the goal was simple: make the repository a reliable source of truth before scaling product code. That foundation is now in place.
What Sprint 0 delivered
Every item on the roadmap is checked off:
- GitHub organization and repository
- Product vision and principles
- Architecture overview and ADR process
- Contribution guidelines and issue/PR templates
- Monorepo scaffold (TypeScript, pnpm workspaces)
- Local MCP server for dogfooding (
apps/local-mcp) - Handshake prototype for structured AI onboarding
Along the way we also shipped:
- Public site at meronq.pages.dev — landing page and this development blog
- First blog post documenting Sprint 0 goals and architecture
- Distribution channels — Discord, Telegram, dev.to, and Hashnode for building in public
Sprint 0 was never about features at scale. It was about vocabulary, boundaries, and a place where decisions and history live durably.
What we learned
Three patterns are already paying off:
- Document before you scale code. ADRs, vision, and architecture docs gave AI assistants (and humans) a shared starting point.
- Dogfood early. The local MCP server and handshake let us develop Meronq inside Meronq's own repo — fewer repeated explanations, more time on real work.
- Build in public. Publishing the blog, site, and updates across channels keeps us honest and invites early feedback.
The hypothesis from day one still holds: the missing piece is not a better LLM. Teams need a layer that turns engineering reality into engineering understanding before AI sees it.
Sprint 1 — Canonical Engineering Model
Sprint 1 goal: define the first Meronq language primitives that all runtime, memory, scanner, and translator components will use.
Planned work:
- Define Entity, Relation, Evidence, Event, and Action/Result models
- Export the first core domain API from
packages/core - Add tests for core primitives
This is the vocabulary everything else will build on. Significant decisions will land as ADRs; progress updates will appear here.
Follow along
- Roadmap — sprint plan and checkboxes
- ADRs — architecture decisions
- Contributing — how to participate
- Development blog — build log
- GitHub: Meronq-dev/meronq
If you care about durable engineering memory and AI that understands your project — not just your last prompt — we are building for you. Sprint 0 is done. Sprint 1 starts now.
Read the full post on meronq.pages.dev · Source on GitHub
Top comments (0)