Development blog
Build log, milestones, and lessons learned while building Meronq.
Sprint 20 closed: tools that answer questions, and traces that prove they do
Until this sprint, Meronq's product tools introduced themselves the way connectors do: by naming the system they talk to. `github_sync`, `memory_search`, `project_build`. Accurate labels — and the wrong unit for a host a…
Sprint 19 closed: a closed set of layers for any team that makes something
Meronq's engineering model has an axis called `layer` — the plane a piece of knowledge sits on when you look at a project as a stack. Until this sprint it held whatever the translators wrote: `apps`, `packages`, `docs/ad…
Sprint 18 deferred: what a blocked sprint got done anyway
Sprint 18 was Desktop CDN completeness: macOS installers on R2, an automated publish, a smoke test of *Check for updates* across a version bump. Not one of its four tasks is done, and the reason is not technical. The fir…
Sprint 17 closed: desktop distribution on R2 + in-app updates
Sprint 17 is closed. Meronq Desktop can be downloaded from the website and updated in-app via signed Tauri updater artifacts on Cloudflare R2 ([ADR-0016](../adr/ADR-0016-desktop-distribution-and-updates.md)).
Sprint 16 closed: memory soft sync and Temperature Map UX
Sprint 16 is closed. Desktop memory refresh no longer depends on knowing `memory_sync` by name, and the Temperature Map is easier to navigate when heat and focus matter.
Sprint 15 closed: product feedback inbox
Sprint 15 is closed. Product feedback no longer tries to open GitHub Issues from Desktop.
Sprint 14 closed: Memory Temperature Map
Sprint 14 is closed. Knowledge Vitality is now visible in Meronq Desktop as a force-directed CEM graph — hot, warm, cold, and archived — with session-local Expand / Pack dials that never mutate shared SQLite (ADR-0013).…
Sprint 13 closed: KV completeness and PUC with control values
Sprint 13 is closed. ADR-0014 (Product Metrics — KV Completeness and PUC) is Accepted.
Sprint 12 closed: engineering activity as signal
Sprint 12 is closed. ADR-0013 (Engineering Activity as Signal, and Knowledge Consolidation) is Accepted.
Sprint 11 closed: memory that forgets relevance, not facts
Sprint 11 is closed. Meronq's project memory now has a lifecycle: knowledge gains strength when it is used, cools when it is not, and is archived rather than deleted when it disappears from the codebase. ADR-0009 (Knowle…
Sprint 10 closed: Desktop polish and a cloud spike
Sprint 10 is closed.
Sprint 10 in progress: Rust sidecar supervise (A3)
Sprint 10 is still open. This is a mid-sprint build-in-public checkpoint, not a closure post.
Sprint 10 in progress: desktop packaging (A2)
Sprint 10 is still open. This is a mid-sprint build-in-public checkpoint, not a closure post.
Sprint 10 in progress: desktop packaging (A1)
Sprint 10 is still open. This is a mid-sprint build-in-public checkpoint, not a closure post.
Sprint 9 closed: Desktop MVP
Sprint 9 is closed.
Sprint 8 closed: Productization
Sprint 8 is closed.
Sprint 7 closed: Engineering Agents
Sprint 7 is closed.
Sprint 6 closed: Skills and Workflows
Sprint 6 is closed.
Sprint 5 closed: MCP Server
Sprint 5 is closed.
Sprint 4 closed: GitHub Integration
Sprint 4 is closed.
Sprint 3 closed: Memory Engine v0
Sprint 3 is closed.
Sprint 2 closed: Local Project Intelligence
Sprint 2 is closed.
Sprint 1 closed: Canonical Engineering Model wired into handshake
Sprint 1 is closed.
Sprint 0 closed: foundation complete, Sprint 1 begins
Sprint 0 is closed.
Starting Meronq: Sprint 0 and the foundation
Every AI assistant that joins a software project starts from zero. It re-reads the repository, re-parses Git history, re-discovers conventions — and spends tokens on discovery instead of reasoning.