Summary

  • The 27 January 2026 notice created an authoritative interim state: the October meeting would no longer take place in Guatemala, but no replacement venue or precise Mendoza date range had yet been published. The 27 March 2026 message then confirmed Mendoza, Argentina, and 19–22 October 2026.
  • The current meetings page, public event-system page and 25 June 2026 fellowship notice align on the event identity, location and dates. That proves the present public state, not the migration, exception or closure of each registration, invitation, fellowship case, programme commitment, supplier instruction or participant request.
  • The loss mechanism to test is state drift, not relocation itself. A stable meeting can be correct on its landing page while a calendar, invitation, travel plan or operational instruction retains an earlier version. A public versioned change record can define the common state; a protected per-participant receipt can prove delivery, dependency status, response, remedy and closure without exposing personal data. The checked sources prove neither participant loss nor process failure, and they do not prove universal reconciliation.

The first public interval: relocation pending

The January notice changed the authoritative state of a named event. LACNIC said the meeting would be relocated from Guatemala because of the recent situation in the country and exceptional measures announced by the authorities. It framed the decision around safety and conditions for good participation, said it was working to minimise impact, said a replacement would be communicated through official channels, and expressed the hope that a future edition could be held in Guatemala.

That is the full evidential boundary. The notice supports no broader characterisation of Guatemala, allegation about avoidability or inference about motive. It also does not identify a replacement city or give the precise 19–22 October 2026 range later used for Mendoza. From 27 January 2026, the earlier venue state was superseded while the replacement state remained pending.

A pending state is not evidence of administrative failure. A decision may need publication before every consequential detail is settled. Yet the interval still requires control: records already carrying the event identity must distinguish a superseded Guatemala state, a relocation-pending state and the later Mendoza state. Otherwise, an unchanged calendar or invitation can look current merely because it still names LACNIC 46 / LACNOG 2026.

The checked evidence does not show whether LACNIC used such a distinction internally or sent private notices. It establishes only the public notice and its limits. A versioned transition record would preserve the interim state and show which dependent items were paused, withdrawn, awaiting reissue, unaffected or not yet applicable.

The second public interval: Mendoza and adjusted dates

The archive timestamps the March message at 11:10:06 -03 on 27 March 2026 and presents aligned Spanish, English and Portuguese sections. LACNIC said it made additional efforts to avoid changing the dates originally announced, but limited availability of suitable venues required an exceptional adjustment. The message confirms Mendoza, Argentina, and 19–22 October 2026, while acknowledging and regretting possible inconvenience to annual planning.

The exact superseded dates are not stated and should not be reconstructed. What the message proves is that the second transition affected both place and time. It supplied the replacement fields needed for downstream reconciliation; it did not prove that reconciliation had occurred.

Publication and propagation are different events. The public statement could be complete at 11:10:06 -03 while calendars, registration records, invitation letters, fellowship files, programme commitments, sponsor arrangements or supplier instructions remained at different stages. The reverse is also possible: private dependencies may have been updated promptly without appearing in the checked public sources. The evidence supports neither a presumption of completion nor a presumption of failure.

Later public surfaces converge on the March state. The meetings page and event-system page use the same event identity, Mendoza, Argentina, and 19–22 October 2026; the event system calls the meeting hybrid. The fellowship notice dated 25 June 2026 uses the same location and dates and says applications would be received through 6 August 2026.

That convergence matters, but it is not a transition receipt. The fellowship notice does not establish whether any earlier fellowship workflow existed or required migration. The hybrid label describes the current attendance mode; it is not evidence that hybrid participation was offered as a relocation remedy. A current landing page can show where the event is now without showing how every dependency moved there.

What the evidence proves—and stops short of proving

The two notices establish a public chronology. January withdrew Guatemala as the location and left the replacement open. March filled that open field with Mendoza, Argentina, and adjusted the dates to 19–22 October 2026. The March communication also has an identifiable archive, timestamp and three aligned language sections.

The current meeting, event-system and fellowship surfaces establish canonical convergence. LACNIC also expressly recognised possible inconvenience to annual planning. That recognition shows that the change could affect planning; it does not show that any particular person incurred cost, lost an opportunity or qualified for a remedy.

The checked sources do not quantify changed bookings, refunds, visa cases, fellowship migrations, speaker or programme changes, sponsor or supplier changes, accessibility adjustments, support requests or remedies. They do not prove loss to any attendee, fellow, speaker, sponsor or supplier. They do not show whether private notices were sent, invitations reissued, registrations migrated automatically or manually, or any dependency required no action. They do not establish that LACNIC's internal process failed, and they do not describe the event as cancelled.

Public registration counts provide no shortcut. The event-system figures are dynamic and changed between snapshots. One snapshot cannot support fixed claims about attendance, representation, disruption or notice effectiveness; movement between snapshots cannot support those inferences either.

One event, several retained versions

The event identity remained stable while its attributes changed. That is the condition in which state drift can arise.

A registration may identify the correct meeting while a calendar retains a prior date. An invitation may identify the correct organiser while a travel plan retains Guatemala. A programme or supplier instruction may carry the right event name but an earlier venue field. These are possible mechanisms, not claims that any such conflict occurred.

The stable name can therefore conceal disagreement between versions. Search and navigation resolve towards the latest landing page, while downloaded files, calendar objects and earlier messages may remain fixed. Overwriting the canonical page repairs discovery for a new visitor, but it does not prove what an earlier recipient received, whether a dependent record was updated or whether an exception was accepted.

A notice proves that a public state was declared. Completion requires every dependent state to be reconciled to that state, explicitly excepted because no action was required, or kept open with an owner and next action. The join must be testable without publishing personal travel, visa, disability, financial or contractual details.

That requires two evidence layers. A public, versioned change record preserves the common chronology, authority, trigger, channels, replacement fields, aggregate dependency states and corrections. A protected receipt records what the relevant participant or counterparty received, which dependency was affected, the response, any remedy decision and the closure time. The public record prevents the event history disappearing into a landing-page overwrite; the receipt prevents aggregate assurance standing in for individual completion.

A record-and-receipt test for LACNIC 46

The following schema assumes neither that every field required action nor that any harm occurred. It makes the two public intervals and their dependencies joinable.

Field Public transition record Protected per-participant or counterparty receipt
Stable event/change ID Persistent identifier for LACNIC 46 / LACNOG 2026 and the 2026 cutover Same identifier on each affected record
Superseded public version Archived reference to the prior venue/date version without inventing unstated dates Version actually received or relied upon
Decision authority/time Authorised role or body and effective timestamp Time the decision applied to the dependency
Bounded trigger and public evidence LACNIC's stated Guatemala basis and links to both notices Minimum case-specific relevance, where needed
Notice language/channel/time Spanish, English and Portuguese; channel and publication times Language, channel, delivery time and acknowledgement state
Replacement venue/dates Mendoza, Argentina; 19–22 October 2026 Replacement fields applied to the relevant record
Registration migration Reconciled, excepted, open and corrected aggregates Migration action, confirmation and closure
Attendance mode Canonical mode history, including current hybrid status Selected or confirmed mode; no presumed remedy
Fellowship Public programme version and aggregate case status Application or award dependency, response and closure
Speaker/programme Aggregate status of invitations and programme objects Reissued commitment, exception, response or withdrawal
Sponsor/supplier Aggregate status by dependency class Contractual or operational instruction and closure
Travel/visa/accessibility Versioned guidance and privacy-safe totals Case dependency, response and disposition
Remedy eligibility/outcome Criteria, categories and safe aggregate outcomes, if remedies exist Decision, offer, acceptance or refusal, and completion
Participant request/response Safe volumes, open-case age and resolution classes Request, owner, response, escalation and closure
Remote fallback Public conditions and scope, if separately established Whether offered, chosen and completed
Closure state/time Criteria and closure time for each dependency class Closed, excepted or open status, owner and timestamp
Privacy-safe public aggregates Totals and rates that do not expose individual circumstances Detailed evidence retained under protection
Version/correction history Immutable amendments, reasons and effective times Receipt linked to the exact operative version

The separation between current truth and transition evidence is deliberate. The present hybrid description belongs in the mode history. It does not answer whether a particular registration changed, whether remote participation was offered in response to relocation or whether a participant accepted it. Those are case questions.

The superseded-version field is equally important even though the March message omits the earlier dates. An archive reference or immutable digest can identify the prior version without restating facts outside the checked evidence. That preserves both the transition and the factual boundary.

Two intervals, two closure questions

For the interval beginning on 27 January 2026, the closure question is whether dependent states were moved out of the superseded Guatemala condition and into a controlled pending condition. Some items might require immediate withdrawal or warning; others could be marked pending or might not yet exist. The sources do not establish which path applied.

For the interval beginning on 27 March 2026, the question is whether each pending or superseded dependency was reconciled to Mendoza, Argentina, and 19–22 October 2026, or explicitly excepted. Agreement among later public pages is evidence of canonical convergence, not universal participant-level convergence.

This avoids two errors. One is to treat the January notice as defective because it did not contain information LACNIC said would follow. The other is to treat the March notice and current landing pages as proof that every consequence closed. The first mistakes an interim state for failure; the second mistakes a public declaration for a completed join.

A transition record can show pending, confirmed, reconciled, excepted and open states without assigning blame. The absence of public participant-level evidence does not prove that private action was absent. Equally, the correctness of the current page does not prove that every private action occurred.

Accountability without accusation

The question is not whether LACNIC should have relocated the event, whether the move was avoidable or how Guatemala should be characterised beyond LACNIC's wording. The supplied evidence records LACNIC's stated basis, safety and participation rationale, effort to minimise impact, later explanation about venue availability and hope for a future edition in Guatemala.

Nor must loss be presumed. The reason for a transition record is simpler: one public event can change across many independent records, and current-page correctness cannot certify them all.

The evidential standard should remain layered. The notices prove chronology. The current pages prove the present canonical state. The fellowship notice proves that one later participant-facing programme used Mendoza and 19–22 October 2026 and accepted applications through 6 August 2026. None proves the state of every private dependency.

A public versioned record would make the common chronology inspectable. Protected receipts would make individual completion provable to the people and organisations concerned. Privacy-safe aggregates could show reconciled, excepted, corrected, open and remedied dependencies without revealing personal circumstances.

That is the join the two notices cannot perform alone. It does not presume disruption or failure. It records status, delivery, response and closure so that LACNIC 46 / LACNOG 2026 can remain one stable event across two public states without forcing participants to reconstruct the transition from scattered artefacts.

Sources