Summary

  • The official record contains an apparent contradiction. The 10 February 2016 Community Priority Evaluation report says that DotMusic Limited “Did Not Prevail” and scored 10 of the 16 available points. ICANN’s current application-status page, however, says the application is delegated and labels its contention result “Prevailed Contention (CPE Report)” while linking to that failed report. The later status does not prove that the CPE was reversed. It shows that the underlying application survived the loss and reached later gates.
  • Community Priority Evaluation was an optional priority mechanism inside an eight-application contention set, not a final licence to operate and not a general eligibility judgment. Under Module 4 of the 2012 Applicant Guidebook, 14 points were needed to displace directly contending standard applications. A lower score left the application in contention and sent the remaining parties towards settlement, withdrawal or auction. The report itself expressly told DotMusic that other Module 4 routes remained available.
  • Reconsideration Request 16-5 provided review access but no merits remedy. DotMusic and ten music-sector organisations challenged the evaluation and ICANN’s acceptance of it. A later process review examined communications with the provider, consistency across evaluations and the research trail. The Board accepted those review reports, resumed the held reconsideration matters and ultimately denied Request 16-5 on 14 March 2019. No authority ordered a new score, granted community priority or declared the 10-point report void. ICANN reconsideration docket
  • The enforceable outcome came from later instruments. ICANN approved several application and Public Interest Commitment changes in 2020; ICANN and DotMusic executed a community Registry Agreement on 4 May 2021; that contract made selected community promises enforceable through Section 2.19 and Specifications 11 and 12; and a separate delegation-readiness report confirmed that the remaining programme, contractual and technical gates had been passed. The IANA root record then registered .MUSIC on 14 October 2021, and the formal delegation report followed on 29 October. application update history

The collision in the official record

The first page of the 2016 evaluation is unambiguous. Application 1-1115-14110, for the string MUSIC, received 10 points. The report records zero points for Community Establishment, three for Nexus, four for Registration Policies and three for Community Endorsement. Fourteen points were required. Its result field says “Did Not Prevail”, and the accompanying notice says the application may still resolve contention through the other methods in Module 4. 2016 CPE report

ICANN’s current application page is equally unambiguous about a different stage. It identifies the same application and applicant, marks the application “Delegated”, marks contention “Resolved”, and uses the result label “Prevailed Contention (CPE Report)”. It also warns that information on the page may no longer be current for contracted and delegated TLDs. The linked CPE report is the failed 10-point report, not a later successful evaluation. ICANN application-status page

A third official record establishes the operational outcome without solving the classification puzzle. The IANA root-zone database names DotMusic Limited as the sponsoring organisation for .MUSIC and records 14 October 2021 as the registration date. The 29 October delegation report says that eligibility, party matching, contact confirmations, technical conformance and other processing were complete. Together, these records establish that DotMusic became the sponsoring organisation of the delegated .MUSIC TLD. They do not say that its CPE score changed.

The apparent contradiction disappears only when four statuses are kept separate. The CPE result answered whether DotMusic had earned priority over its rivals. Application viability answered whether the application remained capable of continuing after the failed priority test. Contracting answered whether ICANN and DotMusic had entered a binding Registry Agreement. Delegation answered whether the string and operator had passed the remaining checks for insertion into the DNS root. A later “yes” at one gate does not silently rewrite an earlier “no” at another.

Status Question answered Holder of the operative decision DotMusic outcome
CPE result Did the community application reach the priority threshold? CPE provider applying Module 4 No: 10 of 16
Application viability Did the application remain in the programme and contention set? ICANN programme process, subject to the Guidebook Yes
Contracting Did ICANN designate DotMusic by agreement, subject to delegation? ICANN and DotMusic as contracting parties Yes, 4 May 2021
Root delegation Were programme, technical, contact and procedural conditions complete for root entry? ICANN programme readiness and IANA/PTI root-zone processing Yes, October 2021

That separation is not semantic tidiness. It is the institutional architecture of the case. Treating “delegated” as proof that the CPE was later won would give an archival status label more authority than the signed evaluation report and Board decision. Treating “did not prevail” as application termination would ignore the sentence in the same report preserving other contention-resolution routes. The responsible reading is narrower: the present status page compresses a multi-stage history into a field whose wording is, at minimum, insufficiently precise. No primary record reviewed for this article explains why that field says “Prevailed Contention (CPE Report)”, and no such explanation should be invented. ICANN application-status page

Eight applications, one optional priority route

.MUSIC was not being allocated between DotMusic and ICANN alone. ICANN’s 2016 determination on Reconsideration Request 16-7 confirms that the set contained two community applications and six standard applications. The published objection records identify the eight applicants as DotMusic Limited, .music LLC, dot Music Limited, DotMusic Inc., Victor Cross, Amazon EU S.à r.l., Entertainment Names Inc. and Charleston Road Registry Inc. Only one identical ASCII string could proceed to delegation.

Module 4 gave applicants several ways to remove that collision. Applicants were encouraged to reach agreements, and contention could be self-resolved by one or more withdrawals. An application that had completed the prior stages and ceased to be part of a contention set because of composition changes or self-resolution could proceed. An application could also prevail in a formal contention procedure—CPE or auction—and then proceed. The Guidebook thus assigned meaningful power to private parties as well as to ICANN: rivals could maintain their applications, negotiate or withdraw; ICANN supplied the recognised procedures and determined, for programme purposes, when the set had been resolved. Applicant Guidebook Module 4

CPE was available only to applicants that had designated their applications as community-based and elected the process. The provider’s task was to score the application against Community Establishment, Nexus, Registration Policies and Community Endorsement. A single application reaching 14 points could eliminate directly contending standard applications. If no community applicant reached the threshold, all remaining parties—community and standard—continued towards auction unless they first resolved the set themselves. Applicant Guidebook Module 4

This design explains both the severity and the limits of the test. Priority was powerful because it could remove directly contending standard applications without requiring their voluntary withdrawal. The threshold was correspondingly demanding. Yet the Guidebook also cautioned that failure to reach 14 points was not necessarily a judgment that the asserted community was inadequate or invalid. CPE decided entitlement to priority under specified criteria; it did not decide whether an application was technically qualified, whether its operator could later contract, or whether the music sector existed as a social fact. Applicant Guidebook Module 4

The 2016 report should therefore be read for its procedural effect, not converted into a general verdict about music. DotMusic lost all four available points under Community Establishment, obtained three of four under Nexus, all four under Registration Policies and three of four under Community Endorsement. That arithmetic produced a four-point shortfall. The programme consequence was loss of the priority route. The report did not state that the application was rejected, withdrawn or barred from other contention procedures; it stated the opposite. 2016 CPE report

A community label did not itself create decision power. DotMusic chose the community application form and supplied evidence. Supporting organisations could endorse it. The Economist Intelligence Unit, acting as the CPE administrator, held the scoring function. Standard applicants did not participate in the CPE scoring exercise, but their applications could be eliminated by a successful community score. That asymmetry is why the provider’s scoring decision had executable consequences and why later objections to its procedure became so important. Applicant Guidebook Module 4

Request 16-5: broad participation, narrow authority

DotMusic did not accept the evaluation as the end of the dispute. On 24 February 2016 it and ten organisations submitted Reconsideration Request 16-5, challenging both the provider’s report and ICANN organisation’s acceptance of it. The co-requestors were the International Federation of Musicians, the International Federation of Arts Councils and Culture Agencies, Worldwide Independent Network, Merlin Network, Independent Music Companies Association, American Association of Independent Music, Association of Independent Music, Content Creators Coalition, Nashville Songwriters Association International and ReverbNation. The complete ICANN reconsideration docket records the request, exhibits, correspondence, presentation material, later review documents, the BAMC recommendation, rebuttal and Board disposition.

The number and standing of those organisations gave the challenge political and evidential weight, but not the power to decide it. They could file, support, submit material and seek a remedy. They did not sit on the CPE panel, control the accountability committee’s recommendation or vote on the Board resolution. Their participation rights opened a procedural channel; they did not transfer the decision right from ICANN’s accountability bodies to the music organisations.

The relief requested also reveals the institutional mismatch at the centre of the case. The BAMC’s later summary says the requestors asked the Board to determine that the application satisfied the requirements for community priority. But the operative reconsideration standard was not a general appeal permitting the Board to assign a fresh score because it preferred a different evidential conclusion. Under the version of the Bylaws applied to the request, review concerned staff action contradicting established ICANN policy, or Board action taken without material information or through reliance on materially false or inaccurate information. The BAMC recommended; the Board decided whether those reconsideration criteria had been met. BAMC recommendation

That standard did not make relief impossible. A demonstrated policy or procedural violation could have justified corrective action. It did, however, place the burden on the requestors to connect alleged flaws to an established rule and to material adverse effect. Arguments that the evaluator was substantively wrong, that the result seemed implausible, or that a different institutional design would have been fairer were not automatically enough. The forum was an accountability mechanism with defined jurisdiction, not a second CPE panel.

This is the difference between review access and remedy. Access meant that DotMusic could create a docket, place allegations and evidence before ICANN, receive committee analysis and obtain a Board resolution. Remedy would have meant an executable change: rescission of the report, a new evaluation, a changed score, an award of priority or another order altering the application’s position. The first occurred. The second did not.

Three process-review scopes, none a fresh evaluation

While Request 16-5 was pending, ICANN placed it and other CPE-related accountability matters on hold and commissioned FTI Consulting to examine the CPE process. The review had three scopes. Scope 1 concerned communications and interactions between ICANN organisation and the CPE provider. Scope 2 asked whether the provider applied CPE criteria consistently across reports. Scope 3 compiled the research and reference material underlying eight challenged evaluations, including .MUSIC. The architecture was investigative and comparative; it was not framed as a de novo re-evaluation of DotMusic’s application. 15 March 2018 Board resolutions

The Scope 1 report concluded that the reviewed material showed no evidence that ICANN had exerted undue influence or engaged in impropriety. FTI examined written communications, interviewed relevant personnel and reviewed draft reports. It found that most written exchanges were administrative and that substantive comments generally sought clearer wording, explanation or citations rather than different scores.

That conclusion had a material limitation which should not be edited out. FTI said many communications were verbal and not memorialised, so it could not evaluate them. It reported that it observed nothing indicating that those verbal contacts involved undue influence, but “nothing observed” is not the same proposition as a complete record of every exchange. The Board later acknowledged that the findings rested on the written communications and documents described in the reports. Transparency was increased, but the historical record remained incomplete. Scope 1 report

The Scope 2 report treated consistency as a compliance question. FTI reviewed the Guidebook and CPE guidelines, applicant complaints, working papers, communications and interviews. It concluded that the provider had consistently applied the criteria and that it found no instance in which the process or reports departed from the applicable guidelines. That was a finding about adherence and consistency across the body of CPE work. It was not an independent assignment of points to DotMusic.

The Scope 3 report was narrower still. FTI catalogued references in reports and working papers and tried to connect uncited research statements to underlying material. It expressly said it did not rely on the substance of the reference material or assess the propriety or reasonableness of the provider’s research; both questions were outside the scope. It also noted that working papers contained URLs rather than static captures, that some links were no longer active and that some contained typographical errors, making the original web state difficult to reconstruct.

Those limitations define what the process review can support. It supports the institutional findings that FTI reported: no identified undue influence in the material it examined, no identified inconsistency in applying the criteria, and a compiled research trail with documented imperfections. It does not support a claim that FTI independently agreed that every factual proposition in DotMusic’s score was correct. Nor does it support a claim that the review reproduced every undocumented conversation or reconstructed every webpage seen by evaluators years earlier.

Process legitimacy can be tested at several levels. One can ask whether the provider was improperly directed; whether similar criteria were applied consistently; whether the evidence trail can be audited; and whether the substantive judgment was persuasive. The FTI scopes addressed the first three in bounded ways. They were not commissioned as a fourth-level merits appeal. Conflating them would convert an investigation of process integrity into an adjudication it was not designed to perform.

March 2018: the Board closed the review, not the merits dispute

On 15 March 2018 the ICANN Board adopted Resolutions 2018.03.15.08 through 2018.03.15.11. It accepted the findings in the three FTI reports, concluded that no overhaul or change to CPE was necessary for the current application round, declared the process review complete and directed the BAMC to resume the CPE-related reconsideration requests that had been held. 15 March 2018 Board resolutions

The sequence is decisive. Acceptance of the reports did not itself deny Request 16-5. It removed the institutional hold that had prevented the request from reaching disposition. The Board also said DotMusic and other requestors would have an opportunity to submit supplemental material and make presentations addressing the relevance of the process-review reports to their own cases. The process review’s completion therefore reopened the accountability track; it did not substitute for the final decision on that track. 15 March 2018 Board resolutions

The Board’s “no overhaul” conclusion was also bounded to the current round. It was a programme-management decision based on the review findings, not a declaration that outsourced CPE could never be improved. More importantly for DotMusic, it did not contain an instruction to amend the 10-point report. The evaluation remained operative while the BAMC returned to the pending request.

The later record contains a dispute about the supplemental opportunity. The Board’s 2019 rationale says the BAMC invited additional written material and a presentation, and characterises the requestors as rejecting both invitations. The requestors’ rebuttal disputed that characterisation, saying they had sought unconstrained submissions and an in-person presentation. The Board concluded that their own April 2018 wording had rejected the constraints and noted that no additional briefing followed. That procedural disagreement was considered, but it did not produce a renewed hearing or change the result. 14 March 2019 Board resolution

This episode shows why the existence of an opportunity should not be equated with satisfaction about its terms. DotMusic had already supplied extensive material and objected to limits surrounding further participation. ICANN treated the offered channel as sufficient and the response as rejection. The Board, not the requestors, had authority to decide whether that exchange impaired reconsideration under the applicable standard.

March 2019: a denial, not a re-score

The BAMC issued its recommendation on 25 January 2019. It recorded that DotMusic’s application had been placed with seven rivals, that Request 16-5 had accumulated 41 exhibits and at least 11 later submissions, and that the CPE process review had intervened while the request was on hold. It recommended denial because it found no established policy or procedural violation in the evaluation and no misapplication that materially or adversely affected the requestors. BAMC recommendation

On 14 March 2019, Resolution 2019.03.14.12 adopted that recommendation. The Board considered a 12 February rebuttal even though it said the applicable Bylaws did not call for one, and concluded that the rebuttal supplied no additional argument or evidence supporting reconsideration. The resolution’s executable effect was denial.

The Board addressed several categories of allegation: the implications of another IRP declaration, GAC advice, alleged conflicts, ICANN-provider communications, and the provider’s use of the CPE criteria. It repeatedly returned to the same jurisdictional question—whether an established policy or procedure had been violated. The Board agreed with the BAMC that the requestors had not shown such a violation in the scoring of the application. 14 March 2019 Board resolution

The decision should neither be understated nor enlarged. It was authoritative for Request 16-5 and left the CPE report in place. It also endorsed the BAMC’s procedural analysis and rejected the grounds presented. But it was not a fresh scoring sheet. The Board did not award DotMusic zero, three, four and three points under the four criteria; the provider had done that. The Board did not order a second panel to assess the application. It did not grant priority. It did not state that DotMusic’s later route to the string would count as a successful CPE.

Nor did the denial terminate the application. The readiness report later recorded that the accountability mechanism had not resulted in a determination that the application should be barred from contracting. That is a different proposition from saying DotMusic won reconsideration. DotMusic lost the challenge, but the denial did not create a separate programme bar. In institutional terms, “no remedy” and “no programme bar” can coexist. delegation-readiness report

An April 2019 ICANN executive-team report adds one limited fact to the post-decision chronology: DotMusic withdrew four pending Cooperative Engagement Processes concerning .MUSIC. The report does not identify a substantive order issued in those CEPs or disclose a settlement. Their withdrawal closes a procedural branch; it does not establish the private bargain, if any, by which contention was later cleared. April 2019 executive-team report

The missing bridge: how contention ceased to block DotMusic

After the reconsideration denial, one institutional question remained before contracting: what happened to the other seven applications? The Guidebook says an unresolved direct contention set must be cleared by an accepted mechanism. Rivals could settle and withdraw; formal auction remained available if they did not. ICANN, in turn, had to recognise that no competing application still blocked the string. Applicant Guidebook Module 4

The public readiness record proves the result but does not disclose the mechanism. Its string-similarity section asks whether the application prevailed through “CPE, Auction, and/or Self-Resolution” including withdrawal or termination of all other members in contention, and answers “Yes”. That is a disjunctive checklist entry. It confirms that ICANN treated the contention set as resolved. It does not identify which combination of auction, private agreement, withdrawal or termination produced the clearance. delegation-readiness report

Because DotMusic’s own CPE report says it did not prevail, that failed evaluation cannot by itself be the executable event that caused all seven rival applications to cease blocking the string. The readiness report confirms that ICANN regarded the recognised contention-resolution condition as satisfied, while individual rival pages, such as dot Music Limited’s application record, show withdrawal and non-prevailing outcomes. Neither source discloses private consideration, a payment formula, bilateral terms or an auction type. The safe conclusion is therefore limited: no rival remained as a programme block, and ICANN treated the set as resolved; the reviewed public record does not prove the commercial terms or precise combination of mechanisms that produced that result.

This gap is not a licence to fill the story with industry custom. A private settlement may explain one or more withdrawals; an auction may have played a role; different applicants may have exited by different routes. Without a primary record, each is only a possibility. The distinction between a documented status and an undocumented transaction is central to governance reporting because the first tells us that a programme block disappeared while the second would tell us why and on what terms.

Rival applicants held practical leverage during this stage. As long as a qualified application remained in direct contention, DotMusic could not obtain an unambiguous path to the string. Each rival could maintain its position, negotiate or withdraw. ICANN did not necessarily control any consideration exchanged between private parties, but it controlled the official programme determination that the set was resolved and that the surviving application could move towards contracting. Participation by music organisations did not confer a right to compel another applicant’s exit.

The current application page’s “Prevailed Contention (CPE Report)” label obscures this distributed power. It makes the route appear singular and evaluator-driven when the available records show only that the remaining set was later cleared and that ICANN recorded the application as having prevailed in contention. Until ICANN publishes a status-history clarification, the label should be quoted as a field value, not repeated as the legal explanation of how DotMusic won the string. ICANN application-status page

2020: changing the application was not yet contracting

ICANN’s application update history records a series of approved changes in early 2020. Question 7 was updated on 29 January. Questions 16, 18A, 18B, 18C, 20D, 27 and 28 were updated on 20 March; the page says both confidential and non-confidential portions changed, so specific details were not posted. A new Public Interest Commitment attachment was posted on 23 March, replacing a 2015 version. Question 20E was updated on 25 March. The relevant postings opened 30-day public-comment windows where stated.

Those approvals are the documentary bridge between the contested application and the later contract, but they are not equivalent to the contract. DotMusic proposed changes; ICANN approved changes to the application record; the public could comment on specified postings. None of those acts, standing alone, designated DotMusic as registry operator or put .MUSIC into the root. They altered the terms on which the application could be carried forward.

The incomplete public redline also limits what can responsibly be claimed. The update page identifies the questions and dates, but it says some specific details are not posted because confidential material was involved. A line-by-line account of how every 2012 promise became a 2021 obligation would require the underlying versions and approval notices. The executed agreement supplies the final enforceable text; it should not be reverse-engineered into claims about every confidential change request.

The 2021 agreement converted selected promises into obligations

ICANN’s registry-agreement page identifies DotMusic as operator, gives 4 May 2021 as the agreement date and classifies .MUSIC as a Base, Community (Specification 12), non-sponsored agreement. That classification matters because community status after contracting was no longer merely an applicant’s narrative. It appeared in the legal instrument governing operation. .MUSIC Registry Agreement page

Yet even the executed Registry Agreement preserves the next gate. Section 1.1 designates DotMusic as registry operator subject to the requirements and necessary approvals for delegation and entry into the root zone. The agreement also allowed ICANN to terminate if the operator failed to complete identified delegation testing and procedures within 12 months, subject to a possible extension. Contractual designation therefore created rights and duties before it created an operating TLD.

Section 2.19 allocates the community-governance obligations. DotMusic must establish policies for naming conventions, registration by community members and use consistent with the community purpose. It must operate the TLD so that the community can discuss and participate in policy development and modification. It must establish enforcement and dispute procedures, enforce the policies, accept the Registry Restrictions Dispute Resolution Procedure and comply with Specification 12. executed Registry Agreement

The verbs reveal the power structure. The community is entitled to discussion and participation. DotMusic is required to establish, operate and enforce. ICANN holds contractual oversight, and specified dispute procedures provide routes for qualifying complaints and remedies. Community participation is therefore real but not identical to a veto, a Board vote or ownership of the root-zone change. A Policy Advisory Council may influence policy; it does not replace the registry operator as the contracting party.

Specification 11 adds Public Interest Commitments enforceable by ICANN and through the PICDRP. The .MUSIC commitments include authentication of registrants, non-discrimination against legitimate members of the global music community, consultation through a Policy Advisory Council, alignment of registration policies with the community purpose, and proactive and reactive enforcement with appeals mechanisms. These are not a retrospective award of CPE points. They are prospective contractual duties attached to operation. executed Registry Agreement

Specification 12 makes the operational design more concrete. It sets community eligibility, music-related name-selection and content/use restrictions. It requires validation of email addresses and telephone numbers, describes proactive and reactive enforcement, calls for random compliance checks and repeat-offender monitoring, and provides for registry lock followed by termination if non-compliance is not cured within a reasonable period. It also says policies and processes will be reviewed with the Policy Advisory Council and presented publicly for community feedback. executed Registry Agreement

These provisions create a different kind of institutional power from CPE. The evaluator’s score was a one-time allocation test. Specification 12 governs continuing admission, use and enforcement inside the delegated namespace. A person or organisation may support the idea of a music community yet still be denied a registration under eligibility rules. A registrant may enter and later face lock or termination for non-compliance. The operator’s authority is therefore both enabling and exclusionary, bounded by contract, applicable law and dispute procedures.

Enforceability should also be stated precisely. The agreement says the specific PICs are enforceable by ICANN and through the PICDRP, and it binds the operator to RRDRP outcomes; the contract contemplates remedies that can include termination in applicable post-delegation procedures. But access to a named procedure is not an automatic remedy for every disappointed registrant. Standing, evidential thresholds, the subject matter of the complaint and the governing procedure still determine whether a claim can be heard and what relief can follow. executed Registry Agreement

The agreement therefore did something the 2016 evaluation could not. It converted selected registration, verification, consultation and enforcement promises into obligations enforceable against the operator. It did not declare that the provider had mis-scored Community Establishment. The legal source of the obligations was consent to the 2021 contract, not a retroactive CPE victory.

Contract did not equal root access

The 13 October 2021 readiness report shows the separate operational gate. It marks “Readiness Confirmed” and records successful background screening, DNS stability review, registry-services review, financial review and technical and operational review. It also records public-comment consideration, no objection filed against DotMusic’s own application, no consensus GAC advice that the string should not be approved, and an accountability mechanism that did not result in a determination barring contracting. delegation-readiness report

The final page adds two conditions that a signed contract alone could not satisfy: a Registry Agreement had been executed, and pre-delegation testing had been completed. The checklist then confirms that the evaluation was consistent with ICANN’s procedures and that the process provided stakeholder input. Whatever one thinks of the breadth of those institutional assertions, the document’s operative function was clear: it certified that ICANN regarded all applicable new-gTLD programme phases as complete for delegation. delegation-readiness report

IANA’s report then checked that the proposed sponsoring organisation matched the contracted party, that contacts confirmed their details and responsibilities, that the technical configuration met minimum root-zone requirements and that other procedural checks were complete. The report identifies DotMusic as the proposed manager and says the new-gTLD application process was complete. The IANA functions were provided by Public Technical Identifiers, an ICANN affiliate. IANA delegation report

The dates should not be collapsed. The readiness report is dated 13 October 2021 PST. The root-zone database records the registration date as 14 October. The delegation report was published on 29 October. Readiness, root registration and publication were closely connected but distinct acts. The IANA page, last updated 6 May 2026, continues to name DotMusic as the sponsoring organisation.

This sequence allocates final power with unusual clarity. ICANN and DotMusic could sign the agreement, but the contract itself made designation conditional on delegation approvals. ICANN’s programme function certified readiness. IANA/PTI checked the contracted party, contacts, technical configuration and procedural completion and administered the root-zone step. DotMusic could supply information and technical capability; it could not unilaterally insert .MUSIC into the root.

The reconstructed chain of authority

Gate Governing record Decision power What the decision did What it did not do
Entry into contention Application system and Module 4 ICANN programme administration Placed eight identical-string applications in one set Select the operator
Community priority Module 4 and CPE report Outsourced CPE provider Scored DotMusic 10 of 16; no priority Terminate the application
Reconsideration ICANN Bylaws, BAMC recommendation and Board resolution BAMC recommended; Board decided Tested qualifying policy and procedural claims; denied relief Conduct a de novo CPE or award priority
Process review Board mandate and FTI scopes FTI investigated; Board accepted findings Tested communications, consistency and research provenance Re-score DotMusic
Contention clearance Module 4, rival exits and ICANN status determination Remaining applicants controlled voluntary exits or self-resolution; any auction would follow programme procedures; ICANN recorded the result Confirmed that no rival still blocked contracting Reveal private terms or the exact mechanism mix
Application changes ICANN change-request process DotMusic proposed; ICANN approved Altered specified application questions and PIC material Create a Registry Agreement
Contracting 4 May 2021 Registry Agreement ICANN and DotMusic Designated the operator subject to delegation; made commitments enforceable Put .MUSIC in the root
Delegation Readiness and IANA processes ICANN programme function and IANA/PTI Confirmed programme and technical completion and registered the TLD Rewrite the failed CPE result
Continuing operation Registry Agreement, Specifications 11 and 12, dispute procedures DotMusic operates and enforces; ICANN oversees contract; eligible complainants may invoke procedures Governs admission, use, compliance and remedies Give every community participant equal control

The table also shows why there was no single moment at which “ICANN” simply chose DotMusic. Different components of the ICANN system performed different functions, and private applicants retained leverage between them. The CPE provider could deny priority but not sign the registry contract. The Board could deny reconsideration but did not operate the registry. Rival applicants could block progression by remaining in contention but could not delegate the string. IANA/PTI could implement the final root-zone step only after contracting and readiness.

Counterfactuals that test the explanation

The first counterfactual is the simplest. If a failed CPE automatically terminated a community application, the story would have ended in February 2016. DotMusic could not have remained in contention, obtained approved application changes, signed a Registry Agreement or passed delegation readiness. Module 4 and the CPE report expressly preserve other routes, so the termination theory is incompatible with the governing record. 2016 CPE report

Second, if even one direct rival had remained unresolved, the string would still have had more than one surviving claimant. ICANN could not coherently have answered “Yes” to the readiness question about contention resolution. The later certification therefore proves clearance of the set, even though it does not reveal the mechanism or any private terms associated with it. delegation-readiness report

Third, if the agreement had been executed but delegation testing or procedural checks had failed, DotMusic would have held a contractual designation subject to unmet conditions, not an operating top-level domain. Section 1.1 and the contract’s delegation deadline make that distinction express. The October readiness and IANA records are therefore independent evidence, not ceremonial repetitions of the contract. executed Registry Agreement

Fourth, a successful reconsideration request could have produced corrective action affecting the process or evaluation. The actual Board resolution did not. The later outcome cannot be attributed to a remedy that was never ordered. DotMusic reached the root because the application survived, contention was later cleared, ICANN approved changes, the parties contracted and delegation checks were completed—not because Resolution 2019.03.14.12 concealed a reversal. 14 March 2019 Board resolution

A bounded conclusion

DotMusic’s route to .MUSIC is a case about sequential authority. The 10-point score mattered because it denied a powerful priority right. The reconsideration process mattered because it exposed the limits of ICANN’s internal review: extensive participation and an institutional investigation did not produce a merits re-score. Rival applicants mattered because the application could not advance until their competing claims ceased to block it. The 2021 contract mattered because it transformed selected community promises into enforceable obligations.

IANA/PTI mattered because neither a live application nor a signed agreement was itself a root-zone delegation.

The unresolved parts are also substantive. The current application page has not been publicly reconciled with the failed CPE report. The reviewed public record proves contention clearance but not the precise mechanism, any payment or any auction structure. Some 2020 application changes are described without complete public detail. The post-2021 compliance record requires continued audit; the absence of a notice in the present source set would not prove that no notice or dispute exists.

The defensible institutional lesson is narrower than a victory narrative. Losing community priority can leave an application alive. Review can be available without producing a remedy. Contracting can impose community duties without rewriting the evaluation that preceded it. Delegation can confirm operational readiness without deciding the merits of an old score. Each gate requires its own authority, record and consequence—and none should be allowed to impersonate another.