Repository navigation
Wiring: expose reconciliation API + pipeline-core ensemble repoint #39
Description
Activity
- addedstoryA single reviewable unit of an epicA single reviewable unit of an epicimplementationCode implementation workCode implementation workblockedBlocked on a dependency or decisionBlocked on a dependency or decisionreconciliationForecast reconciliation migration (views-reporting -> here)Forecast reconciliation migration (views-reporting -> here)
on Jun 23, 2026 Update 2026-06-24 — the repoint is now two parts.
- Point path (this issue's original scope): repoint
ensemble.py/dataframe_ensemble.py— the only live reconciliation consumers (used byskinny_love/white_mustang). Cleanup that frees views-reporting of torch. - NEW — probabilistic path:
PredictionFrameEnsembleManagerhas no reconciliation hooks (reconciliation=None,prediction_frame_ensemble.py:280-281). The upcoming UN deliverable needs probabilistic reconciliation there. Tracked in a new pipeline-core issue under their S1 (#182) — appwrite_env logs before it raises; ADR-008 pinned across both entry validators #193.
The reconciler API here (
ReconciliationModule,reconcile_proportional) is already probabilistic-ready; consumers must chunk by time (C-38) and resolve sample alignment (C-37).- Point path (this issue's original scope): repoint
Update (Epic 11): the pipeline-core repoint is already done via injection — pipeline-core #195 (PR #217) built the
Reconcilerport + a frames-only adapter; pipeline-core has zero imports of vpp reconciliation. With the reconciler moving to views-frames (#131, below pipeline-core in the graph), the consumer repoint is simply import fromviews_frames_reconcileat the composition root (views-platform/views-models#191). Superseded by Epic 11 — nothing to do in vpp here.Closing — superseded (as the corrected body says). The pipeline-core repoint was never a vpp task and never targeted vpp; the reconciler's home became views-frames (
views_frames_reconcile, Epic 11 / views-frames#131, v1.7.0). vpp's copy is now deleted (#62 / PR #63, merged todevelopment2026-06-26). pipeline-core ran its own cutover in-repo (PR #217 merged). Nothing actionable here. See register C-42.- added a commit that references this issue
on Aug 11, 2026
Epic: #31 ·
storyimplementationWhat this becomes
The pipeline-core "repoint" is no longer a vpp task and no longer targets vpp. It becomes the pipeline-core clean cutover (gated on views-frames v1.7.0): delete the
views_reporting.reconciliationimports, direct-importviews_frames_reconcile(a stable foundation pipeline-core already depends on — no port/injection needed: decision C / collapse), geography injected as data sourced from the producer (datafactory/viewser, per D-07), never fetched by the reconciler (ADR-023 charter). Tracked in pipeline-core.Superseded by Epic 11 (views-frames#131). Nothing actionable remains in vpp here — the cutover lives in pipeline-core, vpp's deletion is #62. See register C-42 (the stranded-migration risk). Recommend close.