Skip to content

Wiring: expose reconciliation API + pipeline-core ensemble repoint #39

Description

@Polichinel

Epic: #31 · story implementation

⚠️ Corrected 2026-06-26 (verified on origin/development). The original body — "pipeline-core ensemble managers call views-postprocessing reconciliation" — was never true and is now doubly wrong:

What 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.reconciliation imports, direct-import views_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.

Activity

  1. added
    storyA single reviewable unit of an epic
    blockedBlocked on a dependency or decision
    reconciliationForecast reconciliation migration (views-reporting -> here)
    on Jun 23, 2026
  2. Polichinel commented on Jun 24, 2026

    @Polichinel
    CollaboratorAuthor

    Update 2026-06-24 — the repoint is now two parts.

    1. Point path (this issue's original scope): repoint ensemble.py / dataframe_ensemble.py — the only live reconciliation consumers (used by skinny_love / white_mustang). Cleanup that frees views-reporting of torch.
    2. NEW — probabilistic path: PredictionFrameEnsembleManager has 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).

  3. Polichinel commented on Jun 26, 2026

    @Polichinel
    CollaboratorAuthor

    Update (Epic 11): the pipeline-core repoint is already done via injection — pipeline-core #195 (PR #217) built the Reconciler port + 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 from views_frames_reconcile at the composition root (views-platform/views-models#191). Superseded by Epic 11 — nothing to do in vpp here.

  4. Polichinel commented on Jun 26, 2026

    @Polichinel
    CollaboratorAuthor

    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 to development 2026-06-26). pipeline-core ran its own cutover in-repo (PR #217 merged). Nothing actionable here. See register C-42.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedBlocked on a dependency or decisionimplementationCode implementation workreconciliationForecast reconciliation migration (views-reporting -> here)storyA single reviewable unit of an epic

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions