Skip to content

Design: one central store for every app's bug and feature reports - #26

Merged
kenatleap merged 1 commit into
mainfrom
docs/central-store
Nov 14, 2026
Merged

kenatleap merged 1 commit into
mainfrom
docs/central-store

Conversation

@kmoy007

@kmoy007 kmoy007 commented Nov 14, 2026

Copy link
Copy Markdown
Collaborator

Design only; nothing is built. Ken chose on 2026-11-14 to put every app's reports in one central store on Postgres, rather than keep LeapHQ's read-only federation of five stores.

docs/CENTRAL-STORE.md

  • Service. leaphq-reports runs this library's blueprint with a new PostgresStore, promoted from fleet's bug_store_pg.py. It uses its own reports database on leaphq-pg.
  • Apps keep their /api/bugs as a proxy to the service, and call it as their own managed identity. The service takes app from the caller's token. Nothing changes in the widget or in BugQueue.
  • Contract v3 adds product, a stored kind, area, priority (now/next/later), owner, parentId, duplicateOf and votes. It keeps the four statuses.
  • One viewer: @leap/ui BugQueue, with a Product → App → Area roll-up.
  • Migration goes one app at a time (seal first, LeapHQ last). Each step is an idempotent import with a count check, and the old store is kept read-only for 30 days.

For Ken to confirm in review:

  • the levels and the product list;
  • features in the same store as bugs;
  • the identity, database and gateway steps that only you can run.

🤖 Generated with Claude Code

…stgres, proxy per app, contract v3 hierarchy)

Ken decided 2026-11-14: one central store on Postgres, not federation.
Design only; nothing built.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kenatleap
kenatleap enabled auto-merge (squash) November 14, 2026 16:26
@kenatleap
kenatleap merged commit a01e1b0 into main Nov 14, 2026
1 check passed
@kenatleap
kenatleap deleted the docs/central-store branch November 14, 2026 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants