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.

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
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions