Skip to content

Align formal product scope with implemented capabilities - #28

Merged
fengting124 merged 7 commits into
mainfrom
refactor/product-scope-truthfulness
Jul 11, 2026
Merged

Align formal product scope with implemented capabilities#28
fengting124 merged 7 commits into
mainfrom
refactor/product-scope-truthfulness

Conversation

@fengting124

Copy link
Copy Markdown
Owner

What

  • establish document lifecycle governance and ADR records
  • add a tested capability registry and reviewer-facing capability matrix
  • remove video detection from formal product navigation and move retained concepts under /dev/showcase/*
  • remove fabricated confidence, evidence, timelines, and export success behavior from formal reports
  • reconcile README model-runtime claims with server-pending weights

Why

The formal product must expose only capabilities backed by persisted behavior and tests. Visual showcases remain useful, but cannot substitute for Java backend or model-service implementation evidence.

Verification

  • frontend: 18 tests passed
  • ESLint passed
  • Vite production build passed
  • npm audit: 0 vulnerabilities
  • Java: 116 tests passed
  • model service: 6 tests passed
  • smoke tools: 3 tests passed
  • static scan confirms formal Report and Review code do not import mock data

Closes Phase 1 of roadmap PR #27.

@fengting124
fengting124 merged commit e34c14b into main Jul 11, 2026
4 checks passed
@fengting124
fengting124 deleted the refactor/product-scope-truthfulness branch July 11, 2026 05:24
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.

1 participant