feat(forecasting): §25.3 TRUE own-portfolio cannibalization overlap (#1169 PR2) #1171
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#1171
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "feat/cannibalization-overlap-952b"
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?
Summary
PR 2 (Integration) of #1169 — §25.3 cannibalization upgraded from a proxy (same-class competitor density, #986) to TRUE own-portfolio overlap.
_build_cannibalizationnow callsget_own_portfolio(db)(PR1):competitors._normalize_class), price ₽/м² (interval overlap on the narrower band), unit-mix (1 − ½·L1), timing (half-life decay, 0.5 @ 12mo) — weighted by geo proximity (haversine + exp decay to the parcel), aggregated by geo-weighted soft-max (a single strong nearby cannibalizer dominates, not a diluting mean). Explanation lists top contributing own projects + per-axis breakdown (§16 explainability).proxy=true+ reason — never presented as the true index.Honest confidence (§26): thin / only-current (no future pipeline) portfolio → low + note. None-not-0 on every missing axis. Deterministic (sorted tie-breaks, no RNG). advisory=True always, confidence ≤ cap.
Axis status: class + price + geo active now. unit-mix + timing are plumbed via optional params but not yet fed by the call site — a small follow-up will wire
candidate_release_monthfrom the orchestrator horizon (special_indices.pycall site) to activate timing; unit-mix needs a project-level recommended mix (phase 2).Test plan
uv run pytest tests/services/forecasting/test_special_indices.py -q→ 151 passed (964 forecasting dir, no regressions)ruff check+mypy special_indices.py→ clean (0 errors in file)OWN_DEVELOPER_IDSis set (chip filed) — until then runs the labelled proxy fallback.Follow-up
candidate_release_monthfrom orchestrator horizon → timing axis.Refs #1169