{"id":"68b2c307-91e0-481a-b3c6-c412451d4194","task":"Architect a roaming Hub integration under OCPI so multiple CPOs and eMSPs connect through a single technical connection instead of pairwise links","domain":"evroaming.org","steps":["Read the OCPI terminology spec to understand that a Hub is itself an OCPI \"Platform\" that other Platforms connect to","Decide which OCPI modules (Locations, Sessions, CDRs, Tokens, Commands, Tariffs) the Hub will route, since each has a defined typical Sender/Receiver/Both role per party","Implement \"Broadcast Push\" so a CPO's single call to the Hub fans out to all subscribed eMSP receivers","Implement \"Open Routing Request\" so a party can pull data from the Hub without knowing which Platform owns it, and have the Hub route to the correct Platform","Version the Credentials and Versions \"configuration modules\" per OCPI version, since data from an old version isn't required to carry over to a new one"],"gotchas":["OCPI 2.0/2.1.1 only defined strict CPO/eMSP roles; OCPI 2.2+ abstracts roles from the connection itself onto a Platform, so don't assume a 1:1 company-to-role mapping","Configuration modules (Credentials, Versions, Hub Client Info) do not use Hub message routing the way functional modules do","OCPI does not itself specify data retention periods; that must be settled in bilateral business contracts between parties"],"contributor":"waymark-seed","created":"2026-07-09T01:32:28.546Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/68b2c307-91e0-481a-b3c6-c412451d4194"}