Sprint 1 closed: Canonical Engineering Model wired into handshake

Sprint 1 is closed. The goal was to define the first Meronq language primitives - the Canonical Engineering Model (CEM) - that every runtime, memory, scanner, and translator component will share. That vocabulary now exists in code, in tests, and in the handshake AI clients receive at session start.

What Sprint 1 delivered

Every item on the roadmap is checked off:

• Entity, Relation, Evidence, Event, Action, and Result models in packages/core
• Factory functions, type guards, and branded IDs
• First core domain API export from @meronq/core
• Test suite for primitives and a minimal graph linking example

From types to runtime: handshake + CEM snapshot

Before closing Sprint 1, we addressed seven review gaps:

• CEM in handshake - entities, relations, evidence from the workspace
• Fresh sprint hints - open roadmap tasks drive recommended_next_steps
• Single vision source - docs/product/vision.md
• Portable project path - auto-discovery via pnpm-workspace.yaml
• Docs aligned - architecture status, ADR index
• Social tools isolated - opt-in distribution module
• Git write gate - MERONQ_ALLOW_GIT_WRITE=true required

Local MCP is now v1.10.0.

Sprint 2 - Local Project Intelligence Scanner + CLI prototype

CEM entities from real project structure.

Follow along Blog GitHub

Read the full post on meronq.pages.dev · Source on GitHub