LACNIC's Statutes and the Boundary Between Association and Infrastructure

Summary

• LACNIC's Statutes organise a civil association established in Uruguay. They define membership, assemblies, directors, officers, discipline, assets and dissolution, and they make the Spanish text controlling.
• A valid association decision does not by itself explain why a particular holder's registry record, RPKI status, IRR entry or related service should change. The holder's service contract and the applicable resource policy provide the necessary operational bridge.
• The history of LAC-2019-9 shows that proposal, staff interpretation, Board ratification and implementation are distinct stages. Its dates make policy change visible, but process alone does not resolve the contractual effect on every pre-existing holder.
• Because registry action can affect networks and counterparties beyond the voting membership, high-impact decisions need identified authority, factual reasons, notice, cure where available, proportionality, technical sequencing and a practical review route.

A vote in one room, a consequence in another

Imagine two rooms in Montevideo. In the first, members of a civil association receive notice, debate a resolution and vote. In the second, registry staff operate systems that publish resource records and support reverse DNS, routing registries and resource certification. The rooms are connected, but they are not the same room. A resolution can direct the association. It does not press every operational button by its own force.

That separation is the central governance fact in LACNIC's design. The Estatuto de LACNIC creates and organises an association under Uruguayan law. It defines internal organs and corporate processes. LACNIC's registration-documents page separately confirms that an organisation approved for Internet number resources must sign a service contract. The LACNIC Policy Manual separately states the resource-management rules and includes procedures for return and revocation.

Each instrument has a proper task. The Statutes answer who can act for the association. The service contract connects a holder to LACNIC. The policy manual identifies resource rules and procedures. Technical systems implement authorised changes. Uruguayan law supplies the legal setting in which the association and contract exist. Treating the instruments as one undifferentiated mandate makes both power and remedy harder to understand.

The distinction matters because the infrastructure effect may be much wider than the corporate act. Removing a member from an association affects internal standing. Altering a registry record can influence due diligence, routing-security decisions, transfers, customer confidence and counterparties that never voted. One action may eventually justify the other, but the bridge must be visible.

This is not an argument that member government is irrelevant. Elections and assemblies constrain staff and directors. Public policy processes can improve rules. The argument is narrower: association autonomy is authority over association affairs. When the decision crosses into a holder's contract and systems relied on by outsiders, additional rights and procedures become part of legitimate administration.

What the Statutes are for

The Statutes perform constitutional work for LACNIC as a legal person. They address the association's constitution and purposes, legal capacity, assets, member categories, admission and discipline, assemblies, the Board, officers and dissolution. These are the questions any durable association must answer. Who belongs? Who votes? Who manages? How are officers selected? How can rules be changed? What happens if the organisation ends?

This internal allocation matters operationally because someone must have authority to sign contracts, hire staff, approve budgets, maintain systems and adopt procedures. Without a governing constitution, registry operation would rest on informal personal power. The Statutes turn that power into offices, competences and processes that can be checked.

They also create member accountability. A director is not entitled to act merely because a technical choice appears sensible. The director must act within the powers assigned to the governing body. A disciplinary decision concerning a member must follow the membership rules. An assembly must be called and conducted under the applicable provisions. A purported amendment must satisfy the required process and host-law rules.

Yet a constitutional instrument is not a complete service manual. It need not set out every database field, payment sequence, transfer condition, certification action or revocation step. If it tried, the association would be unable to adapt operations without constitutional amendment. The document instead creates the organs capable of entering contracts and administering policies.

That design produces a limit as well as a power. The Board may act for LACNIC, but a statement that the Board acted does not identify the effect on a particular holder. The assembly may amend the Statutes, but an amendment does not automatically rewrite every existing service contract unless the contract and applicable law give it that effect. Internal validity is necessary; it is not always sufficient.

The Spanish text is controlling for a reason

LACNIC serves a multilingual region, but its official statute page says that the Spanish text controls because the association is established in Uruguay and subject to Uruguayan rules. That is not a matter of linguistic pride. It identifies the text that carries legal weight when translations differ.

An English or Portuguese explanation can be useful to members and operators. It can widen participation and reduce misunderstanding. But a translated summary should not be treated as the executed constitutional text. If a dispute depends on whether the Board may impose a particular measure, the relevant Spanish wording, punctuation, cross-references and registered version matter.

The current public landing page does not, on the evidence available here, expose a clear execution date or a complete amendment history. That creates a version-control problem. An analyst can describe the current published Statutes, but should not assert that a clause changed on a particular date without the approved instrument, certificate or deed that proves the change.

This caution is especially important where an English rendering uses a broad word such as authority, sanction, control or resources. Legal meaning may be narrower in the Spanish text. “Socio,” “asociado,” “patrimonio,” “sancion” and “recursos” carry context that a loose translation can flatten. The controlling language should therefore be quoted and analysed before a clause-specific legal conclusion is made.

Language control is also an accessibility obligation in practice. If Spanish controls while affected holders work primarily in Portuguese, English, French or another language, LACNIC should provide faithful translations and clearly identify their status. A person should not lose a practical right because the decisive procedure was available only in language it could not reasonably use. Controlling text and meaningful notice can coexist.

Uruguayan recognition creates a legal person, not a regional government

LACNIC's association form places it within Uruguay's legal order. Article 293 of Law No. 17.296, published on 23 February 2001, treats requests for recognition of legal personality and reforms of civil-association statutes as registrable acts. Registration helps establish which constitutional text and legal person the state recognises.

Law No. 12.771, promulgated on 6 September 1960 and published on 19 September 1960, addresses a supplementary convocation and the validity of statute reform under specified circumstances. It shows that association autonomy operates through legal rules rather than outside them. Members cannot cure every procedural defect merely by agreeing that an amendment would be useful.

These provisions are parts of a wider legal regime. They do not answer every question about member remedies, contracts, judicial proceedings, administrative supervision or mandatory law. A complete legal opinion would need the current registered Statutes, relevant decrees, civil-law rules, contract law and any case law bearing on the disputed act.

The host-law frame nevertheless supports an important conclusion. Recognition gives LACNIC legal personality and validates a method for governing the association. It does not confer public jurisdiction over every person, company or network in Latin America and the Caribbean. Service-region practice and technical coordination are not the same as territorial sovereignty.

This distinction avoids two common errors. The first is to say that a private association has no real authority. It does: it can own assets, contract, employ people, govern members and operate services. The second is to say that because the association performs an important regional function, its member resolutions bind the region as public law. Importance does not change the source or scope of power.

Membership is a real principal relationship, within its field

Members can authorise association affairs through the machinery the Statutes provide. They can elect directors, participate in assemblies, approve matters reserved to them and amend constitutional rules through the proper process. This gives LACNIC an internal accountability structure that a purely founder-controlled company would not have.

The authority is meaningful but bounded by membership and competence. The people entitled to vote are those who meet the statutory category and standing requirements, not everyone whose packets, customers or investments may be affected by registry operation. A resource holder, policy entity, end user, national regulator and downstream customer may occupy different positions. None should be silently counted as another.

An assembly resolution is therefore strong evidence of member authorisation for an association decision. It may approve a budget, elect leadership, amend a rule or direct corporate policy. It is not evidence that every affected nonmember consented. Nor is it proof that the resolution falls within the association's legal capacity or complies with mandatory law.

This denominator problem becomes acute when public language speaks of “the community.” The term can refer to members, meeting entities, mailing-list contributors, resource holders, regional operators or Internet users. These groups overlap without being identical. A resolution adopted by members should be reported as a member resolution. A policy developed through an open process should be reported as a policy outcome. Precision protects rather than diminishes participation.

Member authority also cannot erase individual rights within the association. A majority may govern, but admission, discipline, notice, voting and amendment still depend on the Statutes and law. The fact that a decision was popular does not establish that the affected member received the procedure promised by the constitution.

The service contract is the first bridge to a holder

LACNIC's registration page confirms a basic fact that governance rhetoric can obscure: organisations approved for resources must sign a service contract. That executed agreement is the first direct bridge between LACNIC's institutional decisions and the rights and duties of a particular holder.

The contract should identify the parties, services, payment duties, information requirements, applicable policies, duration, termination conditions, governing law and dispute routes. Its exact current Spanish text and prior versions are therefore essential for clause-specific analysis. The public locator proves that a contract is required; it is not a substitute for capturing the agreement actually signed.

This difference matters in disputes over later policy. A current standard form may incorporate the policy manual dynamically. An older agreement may use different language. A holder may have entered through a predecessor arrangement, merger or transfer. The contract history determines whether and how a later rule reaches the relationship.

The agreement also establishes reciprocity. The holder owes duties, but LACNIC owes services and performance under the agreed terms. This is not simply an administrative licence granted at will. Even if the contract describes number resources as delegated rather than proprietary, the parties still create enforceable expectations about registration services, records, procedure and termination.

A serious case file should therefore include the executed contract, version, signature date, legal identities of the parties, resources covered, incorporated policies at the relevant time and every notice or modification. Without these materials, one can describe general policy but cannot responsibly decide whether a specific operational consequence was authorised.

Policy tells the system what to do, but not every reason why it may bind

The Policy Manual is indispensable because it states the substantive resource rules. Version 2.21 describes hierarchical distribution, delegation, compliance and section 7 procedures for return and revocation. It explains how LACNIC understands the relationship between resource administration and holder conduct.

The manual's language that resources are delegated rather than owned is important to institutional policy. It tells holders how LACNIC frames the service. But that label does not end every legal inquiry. Contractual rights, reliance, transfer value, operating continuity and mandatory law can exist even where the policy rejects proprietary terminology. The consequence must still be traced through the agreement and the applicable procedure.

Policy is strongest when it defines objective conditions. A rule can identify nonpayment, fraud, repeated violation, invalid information, voluntary return or another ground. A procedure can specify notice, cure, escalation, exceptional treatment and record effects. These details make staff action predictable and reviewable.

Policy is weakest when broad aspiration substitutes for a condition. A statement that LACNIC must protect efficient resource use or the regional Internet cannot by itself show that a particular holder committed a breach. Nor can it show which sanction is proportionate. The decision must connect evidence to a rule and a rule to a permitted consequence.

The manual also cannot prove its own contractual effect. Publication shows what LACNIC says the policy is. Adoption records show institutional process. The holder's agreement and applicable law determine how the rule enters the bilateral relationship. These are complementary questions, not rival descriptions of the same fact.

LAC-2019-9 makes the stages visible

The public record for LAC-2019-9, Update of Recovery and Return of Resources, is valuable because it supplies a dated sequence. The proposal was submitted on 12 July 2019, ratified on 13 May 2020 and implemented on 22 November 2021. Those dates separate proposal, corporate approval and operational effect.

The change moved and revised revocation rules and addressed grounds including repeated policy violations, fraud and nonpayment. It also involved staff interpretation. This is a better governance record than an unexplained change appearing overnight in a manual. Entities can inspect the proposal history and see that implementation followed ratification rather than preceding it.

Yet the sequence does not answer every holder question. Ratification establishes that the appropriate institutional body approved the policy under the process described. Implementation establishes when LACNIC put it into operation. Neither fact, standing alone, decides whether an agreement signed years earlier incorporates the new ground or procedure.

Nor does a public proposal page adjudicate an individual case. “Repeated violation” requires a count and a definition. Fraud requires evidence and a standard. Nonpayment requires an invoice, due date and notice. Exceptional treatment for critical infrastructure requires criteria. The policy history supplies the rule's genealogy, not proof that a particular sanction was correctly applied.

LAC-2019-9 therefore provides an ideal instrument map. Policy entities propose. Staff analyse and prepare. A governing body ratifies. Implementation converts the rule into administrative practice. The holder's contract supplies the bilateral bridge. Staff then apply the rule to facts, and a review body or court may test the result. Legitimacy depends on the whole path.

Revocation is a sequence, not a synonym for discipline

Association discipline and resource revocation may arise from related conduct, but they are not the same act. Discipline changes a person's status or rights within the association. Revocation changes the registry treatment of number resources. A holder might be a member, but the practical effects and legal sources remain distinct.

The Policy Manual's staged revocation process is important precisely because it rejects the idea of a single invisible switch. Stages allow notice, explanation, correction and escalation. They create points at which staff can confirm identity, distinguish error from fraud and consider whether a less severe response protects the registry.

The final deletion of holder records, where authorised after the published process, has consequences beyond internal discipline. Counterparties may consult registration data. Routing-security systems may depend on certification state. Transfer entities may rely on the recognised holder. Customers may interpret an unexplained change as evidence that network operations are unstable. These effects justify stronger procedural care.

Not every breach requires the same consequence. A missed payment may be curable. A stale contact can be corrected. A disputed corporate succession may require preservation while documents are reviewed. Deliberate fraud may justify urgent protection. A critical-infrastructure case may require special sequencing to prevent harm to people who had no role in the breach.

Proportionality is therefore operational engineering as well as legal fairness. It asks whether the chosen act is necessary to address the identified risk, whether a narrower act would work, whether downstream harm can be reduced and whether restoration remains possible if the decision is reversed.

The technical systems multiply the effect

A registry relationship is expressed through several systems. Registration data identifies the recognised holder and related contacts. Reverse DNS connects delegated number space to name resolution. The Internet Routing Registry can carry routing policy information. RPKI supports cryptographic statements about route origination. Account systems control who can maintain these functions.

An association resolution does not have the same effect in each system. A membership suspension may require no immediate RPKI action. Contract termination may end some services while a staged revocation process continues. A disputed control change may justify limiting account credentials without deleting historical registration data. Good governance requires an effect map.

The map should identify the action, system, timing, reversibility and external reliance. Will a record be marked, hidden, transferred or deleted? Will certificates expire, be revoked or remain until a later stage? Will IRR objects be frozen or removed? Will reverse-DNS delegations persist during review? Will public history remain available? Each answer should point to authority.

This technical separation protects continuity. The registry's essential function is to preserve coherent, auditable information about unique number resources. Protecting that function does not necessarily require preserving every institution, account privilege or disputed data field unchanged. It requires controlled transitions and an ability to reconstruct what happened.

It also protects LACNIC from overbroad claims. If staff can show that a narrow account measure was used while core records were preserved pending review, the decision appears more proportionate. If every service and record changes simultaneously without a documented reason, the institution looks less like a careful coordinator and more like an unreviewable gatekeeper.

Infrastructure reliance creates duties beyond corporate voting

People outside LACNIC's formal membership rely on the registry environment. An operator's customers depend on address continuity. Peering partners and security teams consult data. Governments may regard networks as critical infrastructure. Lenders, buyers and courts may examine registration history in commercial disputes. These people do not become members merely because they are affected.

Their absence from the membership vote does not mean LACNIC can never act. A service organisation routinely makes decisions with third-party effects. It means internal approval is not the only legitimacy measure. Notice, reasons, proportionality, continuity and review matter because the cost can fall beyond the corporate electorate.

This is where the difference between stakeholder and principal becomes useful. A stakeholder may provide evidence, expertise or warning. A member may have a formal vote. A contracting holder may accept duties. A court or legislature may supply mandatory law. These roles can overlap, but participation in one category does not automatically grant authority in another.

The most responsible institutional language would therefore avoid saying that “the region decided” when a subset of members or policy entities acted. It should name the body and process: members at an assembly amended the Statutes; the Board ratified a policy; staff implemented a rule; a holder accepted a contract. Precision lets outsiders understand why the decision should bind and where it can be challenged.

Infrastructure significance also raises a continuity question. If a decision is disputed, can essential public data and security services remain stable while the legal question is resolved? The answer should be designed in advance. Continuity is safer when attached to the records and functions people need, rather than to the proposition that every institutional decision must take immediate irreversible effect.

Notice must travel farther than the meeting notice

Association law and the Statutes govern notice for assemblies and corporate decisions. A properly called meeting is essential to the validity of member action. But meeting notice is not necessarily notice to a holder that its service or records will change.

Holder notice should identify the legal entity, covered resources, agreement, policy provision, alleged facts, proposed consequence, effective date, cure opportunity and review route. It should be delivered through reliable channels to contacts reasonably capable of acting. Where the operating language differs from Spanish, a faithful explanation may be necessary even though Spanish remains controlling.

Downstream operational notice may also matter. If a record or certificate change could disrupt critical service, a carefully controlled period may allow the holder to challenge error and affected operators to prepare. Such notice need not reveal confidential fraud evidence or create an opportunity to evade a security measure. Urgent cases can have tailored procedures.

The important point is that notice is part of authority. A power conditioned on notice is not fully exercised until proper notice is given. An institution should not describe notice as administrative courtesy when it determines whether the holder had a fair chance to cure or seek review.

LACNIC's public documents would be easier to evaluate if annual reporting showed how notices work in practice: median periods, delivery failures, cures, escalations, urgent actions and reversals. The text can show the designed procedure; only use data can show whether people actually receive it.

Reasons convert discretion into a reviewable decision

A decision letter should do more than cite the association's objectives or a broad policy chapter. It should state the material facts, the evidence relied on, the condition in the applicable instrument and the reasoning that connects breach to consequence. Confidential details can be protected without reducing the explanation to a conclusion.

Reasons improve accuracy. They force staff to distinguish an allegation from a finding, repeated violation from a single event, fraud from documentation error, and nonpayment from a disputed invoice. They allow another decision-maker to identify inconsistency. They also help the holder cure the actual problem rather than guess.

Reasons improve institutional learning. If many decisions rely on the same ambiguous clause, the policy may need clarification. If reviews repeatedly reverse a category, staff guidance may be wrong. If urgent actions are common, ordinary procedures may be too slow. Without reasons and outcome data, these patterns remain invisible.

They also clarify the role of the Board. A Board can ratify a policy without deciding every file. Staff can apply the policy without creating a new ground. A reviewer can test application without reopening the policy's wisdom. Keeping these functions separate prevents a complaint about one decision from turning into a referendum on the entire registry.

Most importantly, reasons stop broad purpose from becoming residual authority. LACNIC may legitimately protect registry accuracy and stability. The decision must still explain why this evidence, under this rule and contract, authorises this particular act now.

Review must match the level of the dispute

Different disputes belong in different forums. A challenge to the calling or conduct of an assembly is an association-governance question. A claim that the service agreement was breached is contractual. A disagreement about the wisdom of a future resource rule belongs in the policy process. A challenge to a factual revocation decision needs a case-level review route. Mandatory Uruguayan law may ultimately require judicial consideration.

No single forum should be advertised as universal. Policy discussion cannot restore a record in an urgent individual dispute unless the process has that power. An internal appeal may not determine the validity of a registered statutory amendment. A court may resolve legal rights without possessing the technical expertise needed to design a routing transition. Good governance routes each question correctly.

Review also requires practical access. A nominal right is weak if the holder cannot obtain the evidence, understand the controlling language, secure a temporary stay or receive a decision before operational damage becomes irreversible. Costs and distance matter across a large, economically diverse region.

A robust system would publish the route with the original decision, preserve the state necessary for review, define the reviewer's independence, permit urgent interim measures and explain the restoration process. It would also publish anonymised outcomes so members can see how often staff decisions are affirmed, modified or reversed.

None of this assumes that every challenge has merit. Review can confirm firm enforcement and expose abusive delay. Its value is structural: power is more legitimate when another body can test the stated authority, facts and procedure.

The strongest defence of LACNIC's current model

The association is not governed solely by unelected staff. Members can elect directors and amend the Statutes. The public policy record exposes proposals, versions, staff analysis, ratification and implementation. The Policy Manual describes staged procedures rather than hiding all discretion. Critical-infrastructure considerations can introduce proportionality into enforcement.

These are meaningful safeguards. A regional registry requires technical coordination, professional staff and the ability to respond to nonpayment, fraud, inaccurate records and repeated violations. It cannot ask every affected Internet user to vote on an account case. Nor can it guarantee continuity if no one has authority to correct records.

The service contract also matters against the claim that LACNIC simply imposes private will. An approved organisation signs an agreement and receives registry services. Contract can lawfully allocate rights and duties even though LACNIC is not a government. The absence of public-law delegation does not invalidate voluntary obligations.

The strongest defence is therefore that LACNIC combines member governance, a public policy process, contracts and operational procedures. That is a genuine institutional architecture. The proper critique is not that the architecture has no force, but that each high-impact consequence must travel through it correctly.

That defence succeeds only if the bridge can be audited. LACNIC should be able to show the registered Statutes, authorised policy, applicable agreement, facts, notice, proportionate technical effect and review. If it relies instead on a broad assertion that the association speaks for the region, it discards the very documentary strengths that make its authority defensible.

The missing denominator is enforcement in practice

The public sources do not provide a complete annual count of resource holders, statutory members, eligible voters, policy entities, disciplinary cases, revocation notices, completed revocations, appeals, reversals and restorations. Without those denominators, outsiders cannot measure how the governance system behaves.

Counts should distinguish association discipline from service enforcement and registry action. They should identify grounds such as nonpayment, fraud, repeated policy violation, invalid authority, voluntary return and organisational dissolution. They should show how many cases were cured at each stage and how many reached record deletion or security-service consequences.

Version data is equally important. Which version of the service agreement governed each case? Which policy-manual version was applied? How many holders remain under earlier forms? Did a disputed obligation arise before or after LAC-2019-9 implementation on 22 November 2021? These facts determine whether apparently uniform administration rests on uniform terms.

Annual reporting should also include review. How many decisions were challenged internally or in court? How long did review take? Were technical effects stayed? How often was the original decision modified? How quickly were records and certificates restored? Aggregated reporting can answer these questions without exposing holder secrets.

The denominator would benefit LACNIC. It could demonstrate that severe measures are rare, staged and usually cured. It could identify where guidance reduces disputes. It could show members that staff discretion is supervised. Written rules establish possible legitimacy; outcome data establish experienced legitimacy.

A six-link test from association to infrastructure

The first link is valid association authority. Which body acted, under which provision of the controlling Spanish Statutes, after what notice and vote? If the act involved statute reform, was the required Uruguayan registration or recognition process completed?

The second link is valid policy authority. Which policy text was approved, by whom and on what date? Was the action taken under the version effective when the relevant conduct occurred? Proposal, ratification and implementation should not be treated as the same date.

The third link is contractual effect. Which service agreement did the holder execute, and how does it incorporate the policy or authorise change? A current public form cannot be assumed to govern an older relationship.

The fourth link is factual application. What evidence establishes the identified condition? If the ground is repeated violation, what were the incidents and notices? If fraud, what finding supports that characterisation? If nonpayment, what invoice and cure period apply?

The fifth link is proportionate technical consequence. Which account, registration, RPKI, IRR, reverse-DNS or other service action will occur, in what order, and why is each necessary? Can essential records be preserved during review? Is restoration technically possible?

The sixth link is remedy. What internal review, association right, contractual process or court route is available? Can the affected party obtain reasons and evidence? Can irreversible effects be stayed? Who confirms restoration if the action is reversed?

An action that passes all six links is much stronger than one supported by a general appeal to community policy. An action that fails one link may still be repairable, but another link cannot simply be stretched to cover the gap. A valid member vote cannot prove fraud. A valid policy cannot prove contractual incorporation. A valid contract cannot excuse defective notice.

Evidence limits should remain visible

Several findings are well supported. LACNIC's official page identifies Spanish as controlling. Its Statutes organise a Uruguayan civil association. The registration page requires an approved resource organisation to sign a service contract. Policy Manual 2.21 describes delegation and revocation procedures. LAC-2019-9 has identifiable submission, ratification and implementation dates. Uruguayan laws make legal-personality and statute-reform acts part of a registration framework.

Other propositions remain unproved. The current executed Spanish Statutes and a complete approval history have not been captured here. The exact current service agreement and its earlier versions require versioned preservation before clause-level claims are safe. The cited Uruguayan laws do not exhaust the law governing associations and contracts. Public sources do not reveal case-level notices, reasons, cure periods and review outcomes.

These limits prevent overstatement in both directions. It would be wrong to infer that every LACNIC infrastructure action lacks authority. It would also be wrong to infer that every ratified policy automatically binds every holder in the same way. The right conclusion is conditional: authority must be traced through the correct documents and facts.

The dates of LAC-2019-9 should likewise be used carefully. They prove the public history recorded for that policy change. They do not establish the date of every underlying contractual effect or adjudicate a dispute that arose before implementation. A case must still identify its own timeline.

Institutional analysis gains credibility by saying what is missing. The purpose is not to create suspicion from every absence. It is to prevent a public landing page, translated summary or policy history from being asked to prove more than it can.

The finding: association autonomy stops at the unproved bridge

LACNIC's members have a real power to govern their association. They can elect, deliberate, amend and supervise through the Statutes. Directors and staff can operate services under the authority allocated to them. The association can enter contracts, adopt resource policy and maintain technical systems. These powers are neither ceremonial nor sovereign.

The boundary appears when internal power produces an external operational consequence. A member vote may authorise LACNIC to adopt a rule. The service agreement must connect that rule to a holder. The policy must define the condition and procedure. Evidence must show the condition occurred. Staff must select a proportionate technical act. A review route must be capable of correcting error.

This layered account is more accurate than either extreme. LACNIC is not merely a discussion club with no authority. Nor is it a regional government whose membership vote binds all operators by public law. It is a Uruguayan civil association performing consequential infrastructure functions through contracts, policies and systems.

That form can be legitimate if it remains legible. Members should know what they authorised. Holders should know what they accepted. Staff should know which consequence a rule permits. Operators should know how continuity will be protected. Reviewers should be able to reconstruct the decision from the controlling Spanish text to the last technical change.

The two rooms in Montevideo should remain connected by more than confidence. Between the assembly vote and the registry console must stand an auditable chain of authority, agreement, policy, evidence, notice, proportionality and remedy. That chain is the boundary between governing an association and governing infrastructure responsibly.