Science

Meronq completes Sprints 1–4 with CEM primitives, local project scanning, and GitHub integration

AI-Generated Summary

1 sources

3 hours ago

3 views

Meronq completes Sprints 1–4 with CEM primitives, local project scanning, and GitHub integration

Key Points

Meronq defines Canonical Engineering Model (CEM) primitives (entity, relation, evidence, event, action, result) in @meronq/core and exposes them in the handshake.
A local scanner builds a ProjectIndex from repository structure and converts it into a CEM snapshot, saving outputs under .meronq/local/.
Local MCP handshakes progress through versions, including project_scan/project_index and later additional modules for memory and GitHub operations.
Sprint 4 adds a GitHub integration package (@meronq/github) that fetches repository metadata, issues, and pull requests using the GitHub REST API and translates them into CEM.
Sprint 4 introduces CLI commands for GitHub sync, status, issue summarization, and documentation drafts, using GITHUB_TOKEN and a cached GitHub snapshot file.

Meronq reports completion of Sprints 1 through 4, building a shared engineering-data workflow that moves from repository inspection to structured “CEM” representations and local memory. Sprint 1 focuses on defining the Canonical Engineering Model (CEM) primitives used across components, including entity, relation, evidence, event, action, and result models in @meronq/core. It also updates the handshake so AI clients receive CEM snapshots and sprint hints at session start, with provisions for workspace discovery and a requirement to gate Git write access.

Sprint 2 then delivers a local project intelligence prototype. It introduces a scanner that builds a ProjectIndex from repository layout, converts it into a CEM snapshot using project data plus git log, and saves results to a local JSON file. CLI commands (such as meronq scan and meronq info) support this flow, and the local MCP handshake is updated to include project_scan and project_index.

Sprint 3 (described as part of the progression) adds a local “memory engine,” moving persistence toward SQLite.

Sprint 4 closes with a GitHub integration package (@meronq/github), adding GitHub repository metadata, issue and pull request data via the GitHub REST API, CEM translation, local MCP v1.13.0 modules, a local JSON cache, and CLI commands for syncing, status, summarization, and doc drafts.

How Outlets Covered This Story

DEV

Dev.to

Sprint 4 closed: GitHub Integration

Sprint 4 is closed. The goal was to connect Meronq to GitHub as the first external engineering system — reading metadata, issues, and pull requests, then translating that data into CEM and local memory. What Sprint 4 delivered Every item on the roadmap is checked off: Repository metadata — stars, branch, description Issues and PRs — GitHub REST API CEM translation — issue:owner/repo#N, pull_request:owner/repo#N Summaries — issue and PR text summaries Doc draft — markdown from git log + GitHub Local MCP v1.13.0 — github_sync, github_status, github_summarize, github_doc_draft. New package: @meronq/github scanProject → CEM → fetchGitHubSnapshot → appendGithubToCem → SQLite memory Auth: GITHUB_TOKEN (PAT). Cache: .meronq/local/github-snapshot.json. CLI meronq github sync meronq github status meronq github summarize issue 3 meronq github doc Sprint 5 — MCP Server Expose Meronq as a product MCP surface with handshake, memory search, and permissions. Follow along Roadmap GitHub setup Development blog Read the full post on meronq.pages.dev · Source on GitHub

2 hours ago

DEV

Dev.to

Sprint 2 closed: Local Project Intelligence

Sprint 2 is closed. The goal was to build the first local prototype that can read a project and produce structured project understanding. The scanner package, CLI commands, and an upgraded handshake now turn repository layout into a ProjectIndex and a CEM snapshot — not just directory names. What Sprint 2 delivered Every item on the roadmap is checked off: Project indexing model — ProjectIndex in packages/scanner CLI prototype — meronq scan and meronq info (apps/cli) Repository scanning — apps, packages, docs flags, ADRs, blog posts Package manager detection — pnpm, npm, yarn Structure summary — human-readable one-liner per project Local notes — scan output saved to .meronq/local/project-index.json Local MCP is now v1.11.0 with project_scan and project_index in handshake. New package: @meronq/scanner Module Role scanProject() Walk repo → ProjectIndex indexToCemSnapshot() ProjectIndex + git log → CEM saveProjectIndex() / loadProjectIndex() Persist under .meronq/local/ Example summary: meronq: pnpm monorepo=true · 4 app(s), 2 package(s) · 8 ADR(s), 3 blog post(s) CLI meronq scan # write .meronq/local/project-index.json meronq info # print summary (--json for full index) Handshake pipeline scanProject(root) → ProjectIndex → indexToCemSnapshot() → handshake.cem Still read-only from disk — Sprint 3 adds SQLite persistence. Sprint 3 — Memory Engine v0 Persist entities, relations, evidence, and events locally. Handshake reads from memory with optional refresh. Follow along Roadmap Development blog GitHub: Meronq-dev/meronq Read the full post on meronq.pages.dev · Source on GitHub

3 hours ago

DEV

Dev.to

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

4 hours ago

Skyhawk reports 12-month cUHDRS subcomponent results for SKY-0515 in Huntington’s trial

Skyhawk Therapeutics announces 12-month results from a Phase 1/2 clinical trial evaluating SKY-0515 in people with Hunti...

1 sources 1 day ago

Science

Proposed “Nautilus” array aims to study missing exoplanet atmospheres

Astronomers increasingly focus on exoplanet atmospheres as potential targets in the search for life beyond Earth, becaus...

2 sources 19 hours ago

Science

Paula Reid expected to leave CNN ahead of Paramount–Warner Bros. Discovery takeover

CNN chief legal affairs correspondent Paula Reid is expected to depart the network, according to multiple reports citing...

7 sources 21 hours ago