Story: ORE conventions import

Table of Contents

This page documents a story in Sprint 17. It captures the goal, current status, acceptance criteria, and the tasks that compose it.

Goal

Complete ORE conventions import: analyse and pilot zero_convention, implement deposit_convention (Phase 2 first type), generate full codegen stacks for seven convention types, and add the CLI conventions import handler (Phase 3).

Status

Field Value
State DONE
Parent sprint Sprint 17
Now Completed 2026-05-11.
Waiting on None.
Next None.
Last touched 2026-05-11

Acceptance

  • All tasks complete; PR-by-PR breakdown in git log.

Tasks

Task State Start End Description
Task: [refdata] ORE import analysis and zero_convention pilot DONE 2026-05-22 2026-05-22 Delivers Phase 1 of the ORE import conventions plan: a working end-to-end
Task: [refdata] deposit_convention: Phase 2 first type DONE 2026-05-22 2026-05-22 Second convention type in the ORE import Phase 2 roll-out (after
Task: Add full codegen stack for seven ORE convention types DONE 2026-05-22 2026-05-22 - Expands ORE import convention coverage from 2 (zero, deposit) to all 9 types: swap, ois, fra, ibor_index, overnight_in
Task: [cli] Add conventions import handler (Phase 3) DONE 2026-05-22 2026-05-22 - Adds `conventions` to the CLI entity enum so `–entity=conventions` is a valid import target

Decisions

zero_convention as pilot
used zero_convention as the first type to analyse because it has minimal fields, making it a clean vehicle for proving the conventions codegen pattern before generalising.
Phase 3 via CLI
the import handler was implemented as a CLI command consistent with the existing import pipeline pattern.

Out of scope

  • Conventions GUI (deferred).

See also

Emacs 29.1 (Org mode 9.6.6)