Skip to content

Remove Estonian BO history branch after register access change #22

Description

@StephenAbbott

Summary

Access to beneficial-ownership data in the Estonian Business Register (e-äriregister) changes on 10 July 2026 an unknown future date. The Time Machine's Estonian BO-history events were deliberately isolated in the codebase so the whole branch can be dropped cleanly when that date arrives. This is a well-scoped maintenance task — a good first contribution.

What to remove

  • _bo_events() in backend/opencheck/timeline/ariregister.py — the function that maps tegelikudKasusaajad_v2 (beneficial-owner history) responses into ChangeEvents. It is deliberately self-contained.
  • The tegelikudKasusaajad_v2 SOAP call in AriregisterAdapter.fetch_timeline_data() (backend/opencheck/sources/ariregister.py).
  • Any related fixtures/tests in backend/tests/ that exercise the BO branch of the Estonian timeline.

What to keep

  • The rest of fetch_timeline_data() — the detailandmed_v2 registry-card history (officers, and shareholders on the register card since Sept 2023) is unaffected.
  • The live-lookup web scraper path (company_print_json) is entirely separate — do not touch.

Verify

  • python3 -m pytest from backend/ stays green.
  • An Estonian entity lookup with the Time Machine enabled still shows registry-card history events, minus BO events.
  • Check whether the register offers a replacement/authorised access route worth documenting in docs/sources.md — if the new regime allows some BO access, note it as a follow-up rather than reimplementing here.

Background

CLAUDE.md § "Estonian adapter (ariregister) — hard-won constraints" documents the SOAP history path and this planned removal ("BO access changes 10 July 2026. BO events are deliberately isolated in _bo_events() … so the whole branch can be dropped then").

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions