fix(forecasting): USP di>0 gate + unit-explicit coverage #1046
No reviewers
Labels
No labels
admin
analytics
auth
automation
bug
business
chore
ci
compliance
data
data-moat
docs
duplicate
dx
enhancement
Fable 5 ревью
feedback/max
generative
GG-форсайт
needs-discussion
needs-human
observability
pause-bots
performance
priority/p0
priority/p1
priority/p2
priority/p3
scope/backend
scope/db
scope/devops
scope/frontend
scope/qa
scrapers
security
site-finder
stage/1
stage/2
status/blocked
status/done
status/needs-analysis
status/needs-fix
status/qa
status/ready
status/review
status/wip
tech-debt
tradein
ux
week ревью 1
wontfix
вторичка
ИРД
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lekss361/gendesign#1046
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "fix/forecast-usp-coverage"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Read-only services audit findings (forecasting core otherwise CLEAN).
#1 (user-facing): recommendation._usp_from_deficits emitted «Дефицит формата X — стройте его» for OVERSUPPLIED formats (filtered only di is None, not di>0) → reached PDF/Excel USP-ниши with a negative deficit_index. Now gates di>0; all-surplus → [].
#3: report_assembler._domrf_coverage guessed percent-vs-fraction (value/100 if >1) → genuine 0.8% read as 80% → inflated confidence in thin-data. Now unit-explicit per-branch. 241+148 tests pass.
NOTE: competitors.weighted_avg_velocity is a naive mean despite the name — left for product decision (rename vs re-weight; a test locks it).