Deferred follow-up to #109. That issue
shipped only the offline part (the recursive-trust wildcard consistency fix, in v1.20.0); the
production-launch tracking was deferred because EBSI GA under EUROPEUM-EDIC is Q4 2026 and
the production endpoints do not exist yet (July 2026). Actionable once they do — not gated
forever.
Scope
Gate
EBSI production launch (Q4 2026). Until then there is nothing to point at — do not manufacture
filler. Invariants: EBSI stays read-only; host allow-list on every request incl. redirects;
short client-side TTL cache (ADR-0001).
Deferred follow-up to #109. That issue
shipped only the offline part (the recursive-trust wildcard consistency fix, in v1.20.0); the
production-launch tracking was deferred because EBSI GA under EUROPEUM-EDIC is Q4 2026 and
the production endpoints do not exist yet (July 2026). Actionable once they do — not gated
forever.
Scope
live-ebsi.yml,OPENVC_EBSI_LIVE=1) at the productionebsi.euhosts; confirm the https host allow-list covers them.shape changed after the 2025-06-30 breaking changes — the golden fixtures are the drift alarm.
openvc_ebsi/versioning.py) still cover the deployed APIversion; add a new adapter class + a golden fixture if the production version is new (one
adapter per version — never scatter
if version == …).Gate
EBSI production launch (Q4 2026). Until then there is nothing to point at — do not manufacture
filler. Invariants: EBSI stays read-only; host allow-list on every request incl. redirects;
short client-side TTL cache (ADR-0001).