Meronq
Meronq team

Sprint 8 closed: Productization

sprint-8productizationdesktopcloudadr

Sprint 8 is closed.

The goal was to turn prototypes into a usable product direction — desktop and cloud exploration, team workspace model, authentication, and billing — without over-building before validation.

What Sprint 8 delivered

Every item on the roadmap is checked off:

  • Desktop app exploration — Tauri 2 direction, MVP scope, apps/desktop stub
  • Cloud backend exploration — optional sync, org admin, API boundaries
  • Team workspace model — Organization → Workspace → Project
  • Authentication model — local-only default, GitHub OAuth for teams, API keys for automation
  • Billing and pricing exploration — Local / Team / Enterprise tiers (no payment integration)

Canonical decisions live in ADR-0008.

New package: @meronq/product

Shared TypeScript types for product boundaries (exploration only — no cloud service yet):

Type Role
Organization Billing and SSO boundary
Workspace Team grouping for projects
ProjectLink Repo connection inside a workspace
WorkspaceMember / WorkspaceRole Access control model
BillingTier local · team · enterprise
AuthMode local_only · github_oauth · api_key

These types document intent for Sprint 9+ implementation; local Meronq continues to work without any cloud account.

Documentation

Doc Topic
Productization Delivery map and phased rollout
Authentication Local vs team auth
Billing Tier exploration
Desktop exploration Tauri shell plan
Cloud backend exploration Sync and admin boundaries

Delivery phases (ADR-0008)

Now     CLI + MCP     Power users, IDE integration
Next    Desktop       Project picker, handshake, memory viewer
Later   Cloud         Optional team sync and org admin

Meronq stays local-first. Desktop is a shell over existing packages — not a parallel codebase. Cloud is optional for teams that want shared workspace admin and backup.

Sprint 9 — Desktop MVP

Sprint 9 goal: ship the first desktop shell — Tauri scaffold, project folder picker, handshake and memory stats UI, MCP lifecycle status.

Exploration is done. Sprint 9 is implementation.

Follow along

Sprint 7 gave AI clients specialized engineering roles. Sprint 8 defines how Meronq becomes a product others can adopt.

← Back to blog