Skip to content

UK local target surface cannot compile since #855: sub-national geographies have no hierarchy label (needs chronicle geography.name) #920

Description

@juaristi22

Since #855 (schema-8 target hierarchy) the UK local target surface cannot compile against any Chronicle artifact: the hierarchy completion labels each target's geography from the fact's geography.name or, failing that, from microcosm.calibrate.geography_constants.UK_GEOGRAPHY_ID_TO_LABEL; Chronicle emits no geography.name and the catalog carries only the UK, GB, country and (since #904) the nine English region codes. Every constituency (650) and local-authority (361) reference is refused:

LedgerHierarchyMetadataError: Ledger target reference 'hmrc.self_employment_income.amount@E14001063':
Chronicle geography 'constituency'/'E14001063' has no display label and is not present in
Microcosm's authoritative geography catalog.

Until chronicle#263 landed the same references failed earlier on the missing dimension labels (chronicle#261), which masked this. Measured on the 474a0ae artifact in #904 (receipts Part I): tools/generate_uk_local_target_references.py fails, uk_local_target_surface refuses every local reference, the national surface compiles 424 / 0.

Affected: local reference regeneration (test_committed_surfaces_regenerate_from_pinned_feed[local] fails whenever the feed is present), dense and local calibration runs, #906's region fan-out beyond the catalogued region codes.

Fix

The durable fix is Chronicle's (PolicyEngine/chronicle#266): geography.name from the publisher's area label, then a feed re-pin here. On this side: re-pin, regenerate the local references and parity receipts, and drop nothing from the catalog (it stays the fallback for the codes Chronicle cannot name). No identifier-humanization fallback in Microcosm (per docs/calibration-target-hierarchy.md).

Not in #904

#904 (the #890 target binding) carries the region catalog entries its London rows need and the receipts; the local grain is out of its scope, so this issue tracks it.

Activity

  1. added a commit that references this issue on Sep 16, 2026
    7239760
  2. added a commit that references this issue on Sep 16, 2026
    d69a543
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions