Summary

  • A timing inversion occurs when a formal consultation remains open, an advertised participation event is still ahead, or comments have not yet been analysed, while the authorised decision or the bargain that constrains it has already moved materially forward.
  • ICANN's 2012 name-protection and .COM records show literal and venue-based inversions; the 2019 .ORG and .INFO renewals and the 2020 .COM amendment show how staff authority and negotiated commitments can narrow choice before or immediately after comment.
  • An early draft or preliminary agreement does not by itself prove a sham: the stronger test compares the decision calendar, the identity of the decision-maker, draft-to-final changes, specific responses to submissions and the legal capacity to choose another outcome.
  • Later reconsideration or arbitral review can establish procedural failure and improve future conduct, but it rarely recreates the bargaining position or public choice that existed before a contract, application window or programme step became settled.

The calendar is part of the decision

Public comment is often described as a period between two dates. A notice opens, submissions arrive, a closing date passes and a report appears. That sequence is easy to display and easy to count. It is not enough to establish that participation mattered. The decisive calendar also includes the date on which staff received negotiating authority, the date negotiators reached a preliminary bargain, the date a committee gave direction, the date the Board resolved the issue, the date a contract was signed and the date implementation became costly to reverse.

When those milestones precede the end of participation, consultation can become performative. The public is invited to influence a choice after the institution has already made it, or after it has incurred political, legal and operational costs that make another outcome unlikely. Comments may still be read. A summary may still be published. The final act may occur after the formal closing date. Yet the opportunity to change direction may have disappeared earlier.

Timing alone does not prove bad faith. Complex institutions prepare drafts before consultation. Negotiators need a text on which the public can comment. A Board may identify a policy direction and then seek advice on implementation. Urgent deadlines can require provisional action. Comments may confirm that an early proposal is sound, so an unchanged final text is not necessarily evidence of disregard.

The accountability question is counterfactual: what was genuinely open to change when the public was asked to speak? If a submission had identified a persuasive legal, technical or public-interest objection, who held authority to alter the outcome, by what procedure and before what irreversible step? A consultation is meaningful when the answer is concrete. It becomes ceremonial when the only available response is to defend a commitment already made.

ICANN is especially exposed to this problem because its decisions combine global participation with private contracting and programme deadlines. Registry agreements are negotiated by staff but operate within Board-approved policies and Bylaw commitments. Supporting organisations develop recommendations on their own calendars. Governmental advice can arrive late. Public meetings create live participation alongside formal written proceedings. A single page labelled "public comment" can therefore conceal several decision clocks.

Four recurring forms should be distinguished. A decision inversion occurs when the authorised body acts before submissions or replies close. A venue inversion occurs when formal written comment has ended but an advertised public forum remains ahead of the decision. A bargaining inversion occurs when the institution presents a preliminary negotiated outcome whose core trade-offs were settled before consultation. An implementation consultation occurs when a legitimate direction has already been chosen and the public is asked only about execution.

The first three create increasing risks of performance unless the institution proves that live alternatives remained. The fourth can be legitimate if the limited scope is stated honestly.

What a meaningful comment record should prove

ICANN's commitment to open and transparent action is not satisfied merely by receiving text. A meaningful record should connect participation to authority. It should show what decision was being made, which body or officer would make it, which terms could change, what constraints were fixed and how the comment period fit the broader calendar.

Minutes matter because they reveal when direction crystallised. A resolution may authorise a contract, reject a recommendation or preserve existing programme rules. Workshop notes may show that the Board had already selected a preferred route. Staff memoranda may record a negotiating boundary. Silence in the public minutes does not prove that no prior view existed, but it prevents the community from testing whether consultation preceded commitment.

Draft differences matter because they show movement. The strongest evidence is not the number of words changed but whether the contested term changed. A final agreement might contain many edits while leaving the price provision, ownership rule or remedy that drew public opposition untouched. Conversely, one carefully targeted revision can demonstrate material influence. A credible account identifies which comments supported the change and why the final text adopted it.

Comment summaries matter because cataloguing is not reasoning. A report that says hundreds of people opposed a term records sentiment. It does not explain whether the decision-maker accepted the factual basis, rejected the policy preference, found itself legally constrained or offered a mitigation. Grouping comments can be efficient, but aggregation should not erase distinct arguments. Repeating the original justification after the comment period is weaker than confronting the strongest objection in the submissions.

Authority matters because a responsive staff team cannot cure a decision taken by the wrong actor. If the issue is policy and belongs to the Board or a community policy body, staff may collect excellent comments yet lack power to resolve them. If the Chief Executive has delegated contract authority, Board consultation should not blur who made the final choice. The public needs to know which official could say no.

Finally, remedies matter because an after-the-fact review may be accurate but incomplete. Reconsideration can ask ICANN to revisit a decision. Independent review can determine whether the Articles or Bylaws were violated. Neither automatically restores the pre-contract bargaining position, reopens a closed application window or removes reliance by third parties. A timing defect is best prevented before the choice hardens.

March and April 2012: action during the reply period

The clearest literal inversion in the record arose during the first round of the New Generic Top-Level Domain Program. The Governmental Advisory Committee and the Generic Names Supporting Organization were considering temporary protections for names associated with the International Olympic Committee and the Red Cross and Red Crescent movement. The issue was urgent because the application window for new top-level domains was due to close on 12 April 2012.

ICANN's public comment proceeding opened on 2 March. The initial comment phase closed on 23 March, and the reply phase ran from 24 March through 14 April. Under the format then used, replies were part of the announced opportunity. They allowed entities to address positions filed in the first phase rather than merely repeat opening views.

The GNSO Council acted on 26 March, after the initial comment period but while replies remained open. The New gTLD Program Committee of the Board met on 10 April, two days before the application window closed and four days before the reply period ended. Its minutes show the pressure created by the application timetable. The committee acknowledged the recommendation but decided not to modify the Applicant Guidebook at that time.

This was not a final adoption of a new permanent protection. The committee preserved the existing first-round position while leaving room for later work. That nuance matters. The action can be defended as a temporary response to an imminent application deadline rather than a covert attempt to foreclose the policy. Yet it was still a decision with practical consequences: applicants needed to know the rules governing applications due on 12 April, and reply submissions arriving through 14 April could not inform the 10 April choice.

The approved resolution therefore presents a direct calendar problem. The institution announced a two-stage comment opportunity but acted before the second stage ended. Urgency may explain the inversion, but it does not erase it. If the reply period could not influence the decision because the programme deadline came first, ICANN should have aligned the dates, shortened the proceeding openly or described replies as input only for later rounds.

A subsequent reconsideration request forced the issue into clearer view. The 27 June 2012 committee action denied reconsideration on the stated grounds but directed the Chief Executive to review inputs received after 10 April. That direction acknowledged the temporal gap. Later submissions could support later review; they could not travel backward and inform the resolution already taken.

This episode meets the strict definition of decision inversion. A formal phase remained open, an empowered committee acted and the immediate programme consequence took effect. It does not establish that committee members ignored every earlier submission or that the underlying choice was necessarily wrong. It establishes that ICANN's published participation calendar and its decision calendar did not match.

The lesson is procedural and practical. If a programme deadline requires action on 10 April, a reply phase ending on 14 April cannot be represented as input to that action. The institution must decide whether to move the decision, move the participation period or divide the questions. Transparent urgency is more legitimate than a nominally open door after the room has moved elsewhere.

Prague 2012: the formal period closed, the advertised forum did not

The .COM registry agreement renewal in June 2012 illustrates a different inversion. ICANN conducted a written public comment proceeding from 27 March to 17 May. According to the Board record, 40 comments were submitted by 34 commenters, and the proposed agreement was not revised in response. The formal written period had therefore ended before the Board acted.

On 23 June, immediately before the ICANN meeting in Prague, the Board approved the renewal in a closed meeting. The public meeting began the next day. A public forum item concerning the .COM renewal was scheduled for 28 June, five days after approval.

The At-Large Advisory Committee objected to that sequence. Its concern was not primarily the substance of the agreement. It argued that approving the text before the advertised forum deprived the live exchange of decision relevance. Entities could question or criticise the agreement, but they could no longer influence whether the Board approved that version on 23 June.

This was not literally a resolution before the written public comment closed. Calling it that would misstate the calendar. It was a venue inversion: the institution completed the formal written stage but left a separately advertised participation event on the public schedule after the decision. The distinction shows why one opening and closing date cannot capture the full participation promise.

ICANN could argue that the Prague forum was not part of the formal proceeding and that the Board had a complete written record by 23 June. Legally and administratively, that distinction may be sound. From the entity's perspective, however, an agenda item at the principal public meeting reasonably appears to be an opportunity to affect the institution's position, especially when the approval has not been announced as final before attendees travel and prepare interventions.

The episode suggests a simple rule: label post-decision discussion as post-decision discussion. If a public forum will occur after approval, the agenda should say that the purpose is explanation, oversight or consideration of future amendments, not input into the completed act. If the forum is intended to inform the choice, the Board should wait. Precision about purpose protects both entities and the decision-maker from a false appearance of openness.

Venue inversion is less severe than acting during a formal reply period because the defined written proceeding was complete. It can still damage legitimacy. ICANN's model relies heavily on public meetings, remote participation and direct exchange among constituencies. Treating those venues as influential in rhetoric but irrelevant in scheduling teaches the community that only written submissions filed before an unstated real deadline matter.

The hidden date is often the date of commitment

Most modern timing disputes are not as neat as the 10 April resolution. The final signature may occur after public comment closes, and the comment report may be published first. The contested question is whether the negotiation or institutional direction had already made the result costly to change.

A preliminary agreement is not inherently illegitimate. Without one, the public might receive only abstract options and be unable to inspect concrete language. Negotiators commonly initial terms subject to consultation and final approval. The key is whether "preliminary" describes a genuinely contingent text or a bargain that both sides expect to preserve unless opposition becomes overwhelming.

Evidence of commitment can include public announcements that the parties have reached agreement, negotiated exchanges across several linked terms, payments or benefits conditioned on the package, implementation preparation, exclusivity, statements that reopening one clause would reopen the entire bargain and a final text that preserves every contested economic term. None is conclusive alone. Together, they can show that comments entered after bargaining leverage had been spent.

The institution bears a special explanatory burden because the public cannot see confidential negotiations. It should disclose enough to identify the alternatives considered, the authority already given, terms that remained negotiable and the standard for changing the proposal. Confidential business information may justify redaction, but it does not justify presenting a settled package as an open question.

Draft-to-final comparison is especially useful. If a contested clause remains unchanged, the decision record should explain why the comments did not alter it. Perhaps the argument was factually wrong, outside ICANN's Mission, inconsistent with existing policy or outweighed by a documented benefit. Those are reasons. Saying only that comments were reviewed is an assertion about attention, not a demonstration of responsiveness.

The timing of the comment report can also reveal whether analysis was plausible. A detailed report appearing immediately before signature may have been prepared efficiently as submissions arrived. It may also leave too little time for the authorised decision-maker to digest thousands of comments, obtain advice, negotiate changes and secure counterparty approval. The shorter the interval, the more the record should show when and how deliberation occurred.

The 2019 .ORG and .INFO renewals: authority after opposition

The 2019 renewals of the .ORG and .INFO registry agreements became a major test of ICANN's public-interest procedures. Proposed agreements removed historic price-control provisions. The change attracted overwhelming opposition from commenters concerned about registrants' exposure, the market position of legacy top-level domains and the absence of an adequate policy basis.

ICANN staff proceeded with execution on 30 June 2019. The core price terms remained. The public record did not show a Board resolution adopting the policy choice before the agreements were signed. A closed Board workshop took place that month, but the record available to the community did not establish a transparent Board decision on removal of the controls. This became central to Namecheap's later challenge.

In November 2019, when the Board considered reconsideration requests, it defended the process. The Board reasoned, among other points, that the purpose statement on the comment page was not itself an ICANN Mission, Commitment, Core Value or formal policy. It rejected the proposition that failure to adopt commenters' preferences meant ICANN had failed to obtain or use public input.

That response correctly identified an important principle: consultation is not a vote. A large majority cannot compel ICANN to adopt a position outside its authority or contrary to reasoned policy. The weakness was elsewhere. The record needed to show which authorised decision-maker evaluated the price-control question, what policy standard applied and how the strongest objections were answered before execution.

Namecheap brought the issue to the Independent Review Process. The December 2022 final declaration found that ICANN violated its Articles and Bylaws in important respects. The panel concluded that the decision was not made in an open and transparent manner and that the removal of price controls involved a policy choice that should have been handled by the Board rather than treated simply as staff contract administration.

The declaration also criticised the practical quality of the comment response. The report largely catalogued opposition and repeated rationales already offered before comment. It did not supply the kind of reasoned engagement needed for a consequential policy shift. The panel's analysis demonstrates why a summary is not a cure when authority and timing are defective.

The 2019 case is not a literal example of the Board resolving the issue while the public comment page remained open. It is more troubling in another way: staff commitment and contract execution occurred without a clearly evidenced, properly authorised and transparent Board policy decision responsive to the consultation. The timing inversion lay between public opposition, the undisclosed locus of authority and the signing of long-term agreements.

The remedy shows the cost of lateness. The panel declared violations but did not annul the contracts. ICANN's Board later commissioned economic studies and, in November 2024, decided not to pursue restoration of price controls. The institution revisited the issue and improved the public account, but the original bargaining position could not simply be recreated five years later.

The episode therefore supports two different conclusions. Public opposition does not govern by tally, and a final term can lawfully remain unchanged. But an unchanged term is legitimate only when the proper authority explains why after a process capable of changing it. In 2019, the problem was not that ICANN disagreed with commenters. It was that the record did not demonstrate a lawful and transparent route from their objections to the commitment made.

The 2020 .COM amendment: consultation after the bargain

The proposed third amendment to the .COM registry agreement offers the clearest bargaining inversion. On 3 January 2020, ICANN and Verisign announced that they had reached a preliminary agreement. ICANN opened public comment on the proposed amendment and a binding letter of intent through 14 February.

The package included permission for phased .COM wholesale price increases under specified limits and a Verisign commitment of $20 million over five years to support initiatives concerning DNS security, stability and resiliency. Those linked terms reflected negotiation. The public was not choosing among an unbounded range of price and payment options; it was commenting on a package that the parties had already described as a preliminary agreement.

ICANN's Chief Executive addressed public concerns on 11 February, while comments were still open, and encouraged continued participation. The post stated that staff would analyse submissions and publish a report after close. That communication is evidence that the institution had not formally ended consideration. It does not by itself show which core terms remained negotiable or what level of objection would cause ICANN to reopen them with Verisign.

The volume was extraordinary. The staff report dated 26 March recorded 9,043 submissions, with the great majority raising concern about price increases. On 27 March, one day later, the Chief Executive announced execution of the amendment. ICANN said the Board had been consulted before negotiations, before their completion and after public comment.

No Board resolution approved the agreement before comments closed. The final act occurred after the report, under executive authority. Accuracy about that sequence is essential. The accountability concern is not a fictitious early Board vote. It is whether a package negotiated before comment remained genuinely open, and whether one day between a report on more than nine thousand submissions and execution was sufficient for reasoned reconsideration of the core terms.

The final package preserved the central price provisions that generated opposition. That fact does not prove the comments were ignored. ICANN may have concluded that the contractual framework, existing policy, anticipated benefits and its Mission justified the result. Verisign may have been unwilling to alter one term without reopening others. But those explanations should appear in a decision record that responds to the strongest objections, identifies the authority exercised and states why the preliminary bargain remained preferable.

The $20 million commitment intensifies the concern because linked benefits can raise the cost of rejection. Once an institution expects funding for agreed initiatives, abandoning the package means losing both the disputed term and the promised benefit. Consultation after such a trade has been struck begins from a different position than consultation before it. The public may oppose the price concession while valuing security spending, yet have no way to separate them.

The 2020 episode demonstrates why comment timing must be aligned with negotiation stages. A first consultation can address objectives and acceptable trade-offs before negotiators reach a package. A second can test actual language. If only the second occurs, ICANN should publish the negotiating mandate, material alternatives and the terms still open. Otherwise, participation risks becoming a ratification exercise without the clarity of a formal ratification vote.

Draft differences can rebut the charge of performance

The best response to a claim of performative consultation is evidence that the proposal changed for intelligible reasons. ICANN does not need to accept every submission. It does need to show that the decision remained open enough for supported objections to matter.

A useful recent comparator is the 2026 transition concerning Standard Bylaws amendments. Public comment ran from 11 February to 13 April 2026. The Board acted on 3 May. Its resolution and supporting material described changes involving reporting, extension and sequencing. The chronology placed Board action after the participation period, and the approved version reflected adjustments that could be traced through the record.

The example should not be treated as proof that every 2026 submission prevailed or that timing alone guaranteed quality. It demonstrates what a more legible sequence looks like: a defined proposal, an open period, a report, identifiable changes and later Board approval. Observers can compare versions and ask whether the revisions answer comments.

Draft comparison should focus on materiality. Editorial corrections, reordered clauses and explanatory recitals may improve a text without changing its effect. A substantive redline identifies movement in rights, prices, review, reporting, deadlines or authority. When a final text does not change, the response should identify whether comments supplied new facts, legal interpretations or alternatives and why those did not alter the outcome.

There are also legitimate cases in which consultation validates a proposal. If technically informed submissions agree that the design is sound, preserving the draft is evidence of responsiveness when the record says so. If opposition rests on matters beyond ICANN's Mission, the decision-maker should explain the jurisdictional limit. If competing comments cancel each other, the institution should disclose the balance it struck. Meaningful participation requires reasons, not automatic revision.

The counterfactual revision test

A disciplined review of any disputed consultation can use seven questions. First, what exactly was open for comment? Broad statements such as "the proposed agreement" are less useful than a list of negotiable clauses, policy questions and fixed constraints.

Second, when did each participation phase begin and end? Initial comments, replies, webinars, public forums and advisory inputs should be plotted separately. An advertised event after approval must be described as retrospective unless the decision can still change.

Third, who held authority at each stage? The record should distinguish staff negotiating authority, Chief Executive execution authority, committee direction, Board policy decisions and supporting-organisation recommendations. Consultation cannot influence an official who lacks power over the contested issue.

Fourth, when did commitment occur? The date may be earlier than signature. A Board direction, preliminary agreement, signed letter of intent, public promise or implementation expenditure can narrow alternatives. The relevant threshold is not any expression of preference, but a step whose reversal carries substantial institutional cost.

Fifth, what changed between the consulted text and the final act? A redline should be published where possible, accompanied by explanations for material changes and non-changes. The analysis should isolate the terms that drew the most significant evidence-based objections.

Sixth, how did the authorised decision-maker respond? A staff summary can support but not replace reasons from the person or body accountable for the choice. The response should address the strongest version of each major argument, not a weakened paraphrase.

Seventh, what remedy remained at closing time and after action? If comments could still cause withdrawal, renegotiation, postponement or amendment, the participation had practical force. If the only avenue was a later challenge that could not undo the contract, the consultation's preventive value was thin.

These questions form a counterfactual revision test: identify a plausible comment supported by evidence, then ask whether the institution had a lawful route and sufficient time to adopt it. A meaningful process can answer yes even when the route was not used. A performative one cannot identify a live route at all.

Why comment totals are a poor legitimacy metric

High participation can make a weak process look strong. The 9,043 submissions on the 2020 .COM amendment demonstrated public concern and mobilisation. They did not establish that the proposal was open to revision. Conversely, a technically specialised proceeding may receive few comments and still be meaningful if those comments change the text or sharpen the reasons.

Counting also creates a false plebiscite. ICANN is not required to adopt the preference with the most submissions. Coordinated campaigns, duplicate language and unequal awareness affect totals. Expertise may be concentrated in a small number of detailed filings. Governments, registries, registrars, civil-society groups and individual users occupy different roles that cannot be reduced to one vote each.

The proper metric is decision responsiveness. Did comments identify facts the institution verified? Did legal arguments change the stated authority? Did technical evidence alter risk controls? Did distributional concerns produce mitigation? Did the final decision explain why a popular proposal was rejected? Those questions assess influence without confusing participation with majority rule.

Comment reports should therefore publish categories, representative reasoning and the institution's disposition. "Noted" is not a disposition. Useful categories include accepted with change, accepted without textual change, rejected on evidence, rejected on policy balance, outside authority, deferred to another proceeding and requiring further study. Each category should connect to the final decision.

Where thousands of comments use common language, the report can aggregate them while preserving unique evidence. Where a late submission arrives after a formal deadline but before the decision, the institution should state whether it was considered and under what rule. Such discipline makes the calendar visible and reduces speculation about selective attention.

Remedy limits make prevention more valuable

ICANN offers reconsideration and Independent Review as accountability mechanisms, but both arrive after the contested step or near its edge. Reconsideration remains a decision by ICANN about its own action. It can correct missing information or misapplication of policy, yet it may defer to the original allocation of authority.

Independent Review is stronger because neutral panelists can determine whether ICANN violated its Articles or Bylaws. The Namecheap declaration proved that even a completed registry renewal could be subjected to searching review. The panel could establish that staff and Board treatment of the issue failed constitutional standards. It could not simply cancel the agreements and restore the price clauses.

That remedial limit is not accidental. Contracts create counterparty rights and reliance. Top-level-domain programmes involve applicants and users beyond the claimant. An adjudicator must avoid administering ICANN's affairs in place of the authorised bodies. But restraint means that a claimant may win the legality question while losing the original opportunity to influence the bargain.

Delay compounds the problem. The .ORG and .INFO agreements were executed in 2019; the final declaration arrived at the end of 2022; the Board completed its principal substantive response in late 2024. By then, market conduct, budgets and expectations had developed under the signed terms. Returning to June 2019 was impossible in any practical sense.

The first remedy for timing inversion is therefore calendar design. Public comment should occur before irreversible direction where feasible. If negotiation requires confidentiality, ICANN can consult on objectives, red lines and trade-offs first, then on actual text. If urgency makes full sequencing impossible, the decision should be provisional, time-limited and explicitly subject to revision after comments. If a live forum is advertised, approval should wait or the forum's retrospective purpose should be clear.

Interim relief can preserve choices in serious disputes, but relying on claimants to seek emergency adjudication is costly and selective. ICANN is better positioned to build preservation into its own decisions. Sunset clauses, staged approvals, delayed effectiveness and express reopening rights can prevent a consultation defect from becoming irrevocable.

A public decision clock for ICANN

ICANN could make timing accountability much easier by publishing a decision clock for every material consultation. The clock would show the public opening and closing dates, reply periods, webinars and meeting forums; staff and Board authority; relevant negotiating milestones; expected report date; decision date; execution date; and effective date.

For negotiated agreements, the clock should state whether the counterparty has accepted the text subject to consultation, whether any term is legally fixed, whether material revision requires renewed counterparty approval and whether linked benefits would be lost if the package changes. It need not disclose privileged advice or commercially sensitive detail. It must disclose enough to show that consultation has a purpose beyond notification.

Board and committee minutes should identify prior direction without inventing false certainty. A statement that members expressed a preliminary preference is different from a formal instruction to execute if specified conditions are met. Both are relevant, but only the latter may constitute commitment. Accurate labels let the community assess rather than speculate.

Comment reports should be delivered with enough time for the decision-maker to read them. No universal minimum fits every case, but one day after a report on thousands of submissions invites legitimate doubt. Where the interval is short, the record should explain rolling analysis, briefings, legal review and any renegotiation that occurred before signature.

Final decisions should include a draft-difference table. For each material contested term, it would list the consulted text, final text, comment themes and reason for disposition. When nothing changed, the table would make the justification visible. This is more useful than a generic assertion that all comments were considered.

Later accountability decisions should be linked from the original consultation page. Entities should be able to see reconsideration outcomes, review declarations, Board responses and any amendments without reconstructing years of separate pages. The resulting record would show not only that participation occurred but how the institution learned from a challenge.

Distinguishing early direction from consensus capture

The phrase "consensus capture" describes a risk, not an automatic conclusion. An organised group may secure early institutional direction and then use formal consultation to legitimise a result. Negotiated counterparties may possess information and access before the wider community. Staff may frame the public question around a preferred package. Once the choice is presented as technically necessary or contractually settled, dissenters carry the burden of proving why the institution should reverse.

Yet early expertise is unavoidable. Registry operators know their costs and systems. Supporting organisations develop recommendations before Board action. Governments and technical advisers have defined roles. The answer is not to pretend that every entity enters at the same moment with equal influence. It is to disclose early direction, preserve meaningful alternatives and test privileged claims against public evidence.

Capture is more likely where four conditions coincide: the beneficiary helped define the available options; the institution committed before broad participation; the comment report catalogued rather than answered objections; and later remedies could not restore the lost choice. It is less likely where early proposals are disclosed, counterproposals receive fair analysis, material terms change and the responsible body explains its decision.

This framework avoids two errors. The first is cynicism that treats every negotiated draft as a sham. Such a view would make practical contracting impossible and undervalue consultation that improves concrete text. The second is formalism that treats a closing date and published report as conclusive proof of legitimacy. A process can satisfy both formalities while leaving no live decision to influence.

The institutional verdict

Do timing inversions make ICANN public comment performative? Sometimes, but the finding must be specific. The April 2012 name-protection action was a literal inversion because the committee acted while the announced reply phase remained open. The June 2012 .COM renewal was a venue inversion because approval preceded an advertised public forum, even though formal written comments had closed. The 2019 .ORG and .INFO renewals exposed an authority and commitment failure: staff executed consequential terms without a transparent, properly situated Board policy decision responsive to opposition.

The 2020 .COM amendment was a bargaining inversion: consultation began after a preliminary package had been negotiated, and execution followed one day after the report.

These cases do not prove that every official had closed their mind or that each substantive outcome was wrong. They show why intention is the wrong primary test. Institutional legitimacy depends on whether the public had a practical route to affect the authorised choice before it hardened.

Minutes, calendars, draft differences and comment summaries provide the evidence. Minutes identify direction. Calendars expose overlap. Redlines show material movement. Summaries and final reasons show whether decision-makers engaged with the strongest arguments. Remedy analysis reveals whether later review could still make participation effective.

Public comment is not a referendum, and responsiveness does not require adoption of the majority view. It requires a live choice, a competent decision-maker and reasons that connect evidence to outcome. When those elements exist, an early draft can survive consultation legitimately. When they do not, even thousands of submissions and a polished report can amount to theatre.

ICANN's most credible response is preventive. Align the participation and decision clocks. Disclose preliminary commitments. State what remains negotiable. Leave enough time between analysis and action. Publish material redlines and reasoned dispositions. Preserve alternatives while serious objections are assessed. Those steps cost less than years of review and protect something a later declaration often cannot restore: the public's opportunity to matter before the decision is made.

Sources