A research-network upgrade needs a roster of institutions that must remain visible
Reconcile the migration cohort with the authoritative member list before describing coverage.
Coverage begins with a denominator
A network modernization can promise broader research collaboration while its planning sheet omits an institution. An omitted row is different from an institution intentionally kept on a transition route. Truthound can check a prepared membership reconciliation. It cannot measure network reachability or establish that every student and researcher will receive the announced benefit.
The Brazilian research-network project
Nokia announced on October 6, 2026 that Brazil's RNP selected Nokia and Q13 to modernize rede Ipê. The release describes a network intended to connect more than 4,000,000 users and support research and education. That is a project scope, not a completed census of the institutions' current access experiences.
Keep transition members visible
Use an approved member roster as the denominator. For each institution and campus, record the roster version, proposed migration wave, transition route and evidence of reachability testing. An institution with no current migration date should remain visible. Removing it from a planning extract can make a partial rollout appear more inclusive than the underlying plan.
Reconcile the expected set
For the institution connectivity roster prepared as a Polars DataFrame, Truthound Core Python SDK 3.3.4's DistinctValuesEqualSetValidator can compare the observed institution identities with an expected set supplied by RNP or the authorized planning owner. A separate parent-reference check can connect campuses to institutions. Set equality cannot establish service quality, and the reference list must be appropriate for the reviewed date rather than assumed complete forever.
A maintained Pandera roster
Pandera 0.35.0 can retain an equivalent owner-written roster check in a dataframe workflow, including Polars. The transformation that builds the expected set and its exceptions needs explicit tests. Keep an existing maintained reconciliation if it accurately preserves those identities. Neither tool supplies the authoritative member list or decides which institutions should receive access.
Ask why a campus is unresolved
Review a sample of unresolved campuses with the people responsible for local access. A missing migration wave may reflect a deliberate transition, an incomplete plan or a recording mistake. Those explanations lead to different actions. Record the explanation and alternative route rather than using one missing-value label for all of them.
Report coverage within its window
Describe coverage only for the roster and observation window actually reviewed. Keep transition institutions in the published internal planning view, with owners for the next decision. When membership changes, update the denominator before comparing progress. This makes inclusion a traceable planning obligation instead of an optimistic count of rows already present.
Evidence
- Event checked
- Subject checked
- Modified
