Who Writes the Problem Statement?

Summary

• A problem statement is not merely introductory prose. It defines the relevant failure, chooses a baseline, identifies affected parties, sets a time horizon and determines which facts will be treated as responsive.
• Proposers need enough authorship to bring an issue forward, but they should not retain exclusive control of the diagnosis after public discussion begins. A community cannot meaningfully redesign a remedy while the premise remains immune from revision.
• RIR procedures offer useful pieces of a better model. RIPE encourages authors to begin with a clear problem, publishes an institutional impact analysis, and requires objections to be reasoned; ARIN separates proposal authorship from Advisory Council development and staff-and-legal review; APNIC asks authors to state the current problem, situation and proposed solution.
• Those safeguards still leave a framing gap. Staff can describe implementability without deciding whether the community chose the right problem, while chairs can summarise consensus without showing whether disagreement concerned the remedy or the diagnosis.
• A defensible process should version the problem statement, publish competing formulations, identify authorship and material edits, test scope separately from merit, and require a reasoned chair finding on the diagnosis before final policy text is judged.
• The objective is not to eliminate advocacy. It is to make framing power visible and reversible so that a proposal succeeds because the community accepted both the problem and the response.

The first paragraph governs everything after it

Policy communities usually devote their fiercest attention to operative words. They debate who qualifies, what evidence an applicant must submit, how long a restriction lasts, which exceptions apply and when staff may refuse a request. By then, much of the decision has already been made. The opening description has established what is wrong, compared it with a selected baseline and invited a particular class of intervention.

Consider the difference between three descriptions of the same set of registrations. One says that scarce addresses are being held without sufficient use. Another says that operators need flexibility to plan over long investment cycles. A third says that the registry lacks reliable evidence about utilisation. The first points toward reclamation, the second toward tenure protection and the third toward measurement. All might refer to identical facts. None is a neutral synonym for the others.

A problem statement also chooses whose inconvenience becomes a public harm. Delay for an applicant can be framed as an access problem. The same delay can be framed as necessary verification that protects existing holders and the routing system. Administrative discretion can appear as arbitrary gatekeeping or as the flexibility required to handle uncommon cases. The words do not merely describe a dispute; they organise it.

This is why authorship matters. The person who submits a proposal has earned a hearing, not ownership of the institution's diagnosis. Once a proposal asks an open community to change common rules, the opening claim becomes a collective question. Entities must be able to say not only “this remedy is wrong” but “the stated problem combines distinct failures,” “the baseline is selective,” or “the people said to benefit do not experience the condition as described.”

If that challenge cannot alter the formal statement, later deliberation is constrained. A community may reject the text while leaving the frame in the archive as accepted wisdom. A future author may inherit the same premise and present a different remedy. Over time, an untested opening paragraph can become institutional memory.

Advocacy is legitimate; disguised settlement is not

Proposal authors are advocates in the honourable sense. They have noticed a defect, invested effort and are asking others to act. Requiring them to write as detached observers would produce evasive prose and hide motivation. A healthy process should expect a point of view and make it answerable.

The difficulty begins when institutions confuse a clear statement with an agreed statement. Clarity means readers can identify the alleged condition, affected parties, causal mechanism and requested change. Agreement means the community has tested those elements and found the diagnosis adequate for decision. An author's polished paragraph can satisfy the first without approaching the second.

Disguised settlement often appears through loaded nouns. “Abuse,” “hoarding,” “barrier,” “loophole,” “legacy privilege,” “market failure” and “administrative burden” may be accurate, but each contains a conclusion. A proposal that starts from “closing a loophole” treats the disputed behaviour as illegitimate before entities have considered whether the existing rule deliberately permits it. “Removing a barrier” assumes the protected interest is less important than the delayed activity. “Improving accuracy” may conceal a shift in who bears evidentiary risk.

Numbers can settle the frame just as quietly. A selected average may hide distribution. A count of requests may exclude people deterred from applying. A registry's handling cost may omit compliance costs transferred to members. A rise after a rule change may reflect reporting rather than conduct. The problem statement determines which denominator enters the room.

None of this justifies treating every proposal as manipulation. Most authors state the problem as they sincerely understand it. Sincerity does not remove framing power. The answer is attribution and contestability: identify the author, disclose the evidentiary basis, invite alternative formulations and show how the final diagnosis changed. Advocacy remains visible; settlement requires reasons.

Problem ownership is different from proposal ownership

An author can properly control whether to sponsor a particular text. They should be consulted before substantial changes are attributed to them. They may withdraw their name if the proposal no longer represents their view. These protections prevent a community body from appropriating an individual's reputation.

The underlying problem cannot remain exclusive in the same way. It concerns common rules administered by an institution with public effects. Other entities may experience it differently, possess contrary evidence or identify a larger issue. Once the claim enters formal consideration, the community needs permission to split, merge, narrow or restate it.

This distinction avoids two bad models. In the first, author sovereignty forces entities to choose between the submitted diagnosis and no action. Amendments become negotiations with one gatekeeper even where broad agreement supports another frame. In the second, institutional editors rewrite the proposal so extensively that the originator becomes a ceremonial name on someone else's case. Neither is bottom-up.

A better arrangement maintains separate records. The original submission remains intact and attributable. A community problem statement develops beside it, with visible revisions and reasons. The proposed remedy can also be versioned. The author may continue sponsoring a preferred combination, while chairs assess whether entities agree on the public diagnosis and whether any proposed remedy answers it.

Separation clarifies withdrawal. If an author departs, the historical submission remains. The community can decide whether the diagnosed issue still warrants work and invite a new sponsor. If the community rejects the diagnosis, the author's document remains part of the record without being mistaken for institutional fact.

It also makes compromise easier. Entities may strongly agree that a verification rule causes unpredictable outcomes while disagreeing about why. Recording the competing causal accounts reveals what evidence would narrow the dispute. Forcing every concern into edits to operative text obscures that learning.

The baseline is often the real argument

Every problem is a deviation from an expected state. The baseline may be a former rule, another RIR's practice, a service commitment, observed operator behaviour, a legal obligation or a principle such as conservation. Choosing among these baselines is a normative decision.

Cross-registry comparison is especially tempting. An author may say that one region is an outlier because its transfer, needs or registration rule differs from the others. Difference alone does not establish failure. Regional markets, member structures, historical allocations, languages and administrative capacities vary. A comparison becomes useful only when the proposal explains why the other region is an appropriate reference and which outcomes are transferable.

Historical baselines can also mislead. A policy designed during plentiful supply may no longer fit scarcity, but scarcity does not automatically invalidate every earlier protection. A rise in transfer activity may be evidence that a market mechanism works, that speculative conduct increased, or that previously hidden demand became visible. The chosen starting date can support any of these stories.

Service baselines require equal care. If an institution promises a response within a period, repeated delay is measurable. Yet the cause may be staffing, request quality, system design or the policy itself. A problem statement that jumps from delay to “the rule is too complex” has already selected one causal theory. If later evidence shows that automation or guidance would solve the delay, policy change may be unnecessary.

The formal statement should therefore name its baseline. What condition is expected? Who established that expectation? Over what period? Which comparison group is relevant? What evidence would show that the apparent gap is ordinary variation rather than a rule failure? Making these questions explicit turns a rhetorical opening into a proposition capable of public examination.

Scope decisions can pre-empt the diagnosis

Open communities need scope boundaries. Number-resource policy forums should not become general venues for every complaint about an association, commercial dispute or Internet regulation. Chairs and councils must be able to say that a submission belongs in another process.

Scope review nevertheless carries framing power. A narrowly stated problem may appear to concern resource administration, while a broader description reveals corporate governance or service quality. Conversely, an author may dress a membership grievance as address policy to obtain a different audience. The body classifying scope decides which institutional vocabulary may be used.

The decision should be procedural rather than a concealed merits judgment. It should identify the relevant charter or policy principle, describe the part that falls inside, and explain where the remaining concern can be heard. “Out of scope” should not mean “unimportant,” nor should it become an unappealable way to protect current practice.

ARIN's current Policy Development Process illustrates the value of explicit institutional roles. Policy proposals can be submitted by members of the Internet community, subject to exclusions for Board and staff initiation, while the elected Advisory Council develops policy and may reject a proposal as outside the process. The published process requires reasons and provides petition actions at defined points. This architecture recognises that intake and public policy development are not identical acts.

The safeguard is strongest when the scope ruling preserves the submitter's language and states the decision-maker's reformulation separately. A council might write: “The submission alleges unequal treatment in request evaluation. The portion seeking a change to the Number Resource Policy Manual is in scope; claims about individual staff conduct belong in the complaints channel.” That sentence exposes the boundary for challenge. A bare status label does not.

RIPE's advice correctly starts with the problem

RIPE's public guidance tells prospective authors that policy proposals should solve specific problems. It advises beginning with a clear problem statement and sharing the idea with the working group before drafting text. This is wise. Early discussion can reveal prior attempts, missing effects and whether policy is the right instrument.

The guidance shifts attention away from a favourite remedy. An author who arrives with finished text may interpret every comment as resistance to implementation. An author who first presents a condition can learn that the group agrees on the harm but sees a simpler answer. The difference reduces positional bargaining.

RIPE's formal Policy Development Process adds discipline. Proposals move through creation, discussion, review and conclusion. Suggestions and objections must be supported with arguments and addressed. Working-group chairs summarise the state of discussion at phase boundaries, while the RIPE NCC supplies administrative support, facts, statistics and an impact analysis describing possible effects and implementation work.

These features provide several opportunities to correct a frame. The working group can challenge it before text hardens. Chairs can distinguish answered and outstanding concerns. Institutional analysis can test predicted effects. Public archives preserve the argument.

But a clear opening remains only the beginning. The process should show whether the problem statement itself reached a stable form. Did entities agree that the condition exists? Did they agree on cause, scale and affected population? Did the review phase change the baseline? A conclusion on the proposal can hide continuing disagreement about all four.

RIPE's emphasis on justified objections offers the right evidentiary culture. It should be applied explicitly to diagnosis. A entity who says “there is no problem” should explain why, just as an author should support the claim that there is one. Chairs can then summarise the competing evidence rather than treating the author's statement as the default and every alternative as a burden-bearing objection.

APNIC's proposal form separates current and desired states

APNIC's process asks authors to present a policy proposal in advance of an Open Policy Meeting, discuss it on the Policy SIG mailing list and explain the reasons for change. Its published material and author guidance distinguish the current problem or situation from the proposed solution and the advantages and disadvantages. That separation is a valuable cognitive check.

When the current state and remedy occupy different fields, a reader can support one without accepting the other. Chairs can ask whether disagreement concerns the factual condition, predicted consequence or design. Authors are less able to make the solution appear inevitable by embedding it in the diagnosis.

APNIC also requires the mailing-list discussion to be considered when chairs assess consensus at the meeting. Anyone interested in number-resource management may participate, physically or remotely, and a show of hands or online gauge is not a binding vote. This recognises that reasons across channels matter more than the room's immediate count.

Still, a form cannot guarantee neutral framing. An author can place assumptions in the “current problem” field, describe only the preferred solution's benefits, or classify opponents' costs as implementation details. A live session can devote most time to wording and leave the initial proposition untouched. The separation creates an opportunity for scrutiny; chairs must use it.

One practical improvement would be to present three slides or sections before any consensus gauge: the author's diagnosis, the strongest alternative diagnosis and the evidence on which they diverge. The author should have a right to respond. Entities could then indicate whether the problem is sufficiently established for policy work, without turning that indication into a vote on final text.

The purpose is not delay. Discovering at the meeting that half the room disputes the baseline is more costly than exposing the disagreement on the list. A visible diagnostic stage makes later text work faster because entities know what the remedy must actually accomplish.

ARIN demonstrates why institutional editing needs limits

ARIN gives its Advisory Council a substantial development role. The AC facilitates communication, deliberates about proposed changes and makes recommendations to the Board. It can revise, merge, abandon or advance draft policies under a published process. Staff provides implementation experience and staff-and-legal review; the Board later examines the history and compliance of recommended policy.

This division can rescue a good issue from weak initial drafting. A submitter need not be an expert legislative writer. Elected council members can translate a practical concern into coherent policy language, reconcile overlapping proposals and ensure that the result fits the Number Resource Policy Manual. The institution gains access to ideas from people who lack insider fluency.

The same power can change the diagnosed problem. Merging two drafts may imply that they share a cause. Revising for legal or operational reasons can narrow the protected population. Abandoning a proposal may be described as a defect in text even when the council rejects the underlying policy objective. The author and public need to see which judgment occurred.

ARIN's requirement that actions be announced with reasoning, together with petition routes, supplies checks. Yet reasons should identify framing edits specifically. A revision log ought to say whether the AC changed evidence, baseline, causal claim, scope or remedy. “Updated after feedback” is too coarse.

Council stewardship is most legitimate when it acts as a fiduciary editor rather than a substitute author. It should strengthen the community's ability to decide, not optimise a proposal for an outcome the council privately prefers. Publishing the author's original statement, council formulation and unresolved alternatives makes that distinction inspectable.

The Board's eventual review also benefits. Trustees can ask whether the final policy responds to the problem the public actually considered. Without a framing history, a technically sound final rule may solve a diagnosis introduced late by institutional editors and never exposed to equivalent scrutiny.

Staff evidence is essential but not dispositive

Registry staff often possess the best evidence about request patterns, system constraints, implementation cost and recurring ambiguity. Excluding that knowledge would make public deliberation theatrical. The question is how institutional evidence enters without becoming an unacknowledged power to define the issue.

RIPE assigns the secretariat an impact-analysis role after the proposal has developed. ARIN publishes staff-and-legal reviews before a draft can advance to recommended status and after substantial changes when necessary. These mechanisms can reveal that an author's assumed problem does not occur, that the proposed wording creates an unintended effect, or that a different administrative measure would achieve the aim.

Staff is not a single neutral sensor. Teams have operational incentives, inherited systems, risk tolerances and limited resources. A condition described as “unimplementable” may mean impossible under current software, costly within the proposed date, legally uncertain, or incompatible with established interpretation. Each calls for a different public judgment.

An assessment should therefore separate fact, estimate, interpretation and preference. It might report observed request volumes, estimate engineering effort under stated assumptions, identify legal uncertainty and recommend a transition period. It should not collapse these into “the proposal is not feasible” without showing which constraint is fixed and which is a management choice.

The community must be allowed to use staff findings to rewrite the diagnosis. If implementation data shows that the real failure is inconsistent guidance rather than policy text, entities should be able to close the proposal with a documented administrative recommendation. If staff's concern rests on a legacy system, the community and Board can compare replacement cost with the policy benefit. Institutional expertise informs the problem; it does not own it.

Affected people may not recognise the official frame

The most consequential omission is often not an argument but a population. Proposal discussions attract authors, regular policy entities, registry staff and organisations with enough capacity to monitor. People who bear diffuse or delayed effects may appear only after the frame is stable.

A rule affecting small networks can be described through aggregate request efficiency while overlooking the cost of scarce specialist time. A documentation requirement may appear minor to large operators with legal teams and decisive to community networks. A transfer safeguard may be analysed through completed transactions, excluding organisations that never enter the market because the process is too uncertain.

Consultation should therefore ask an unusual question: who would describe this problem differently? The answer can guide targeted notice. It may include national registries, smaller members, legacy holders, new entrants, researchers, civil-society networks or people in language communities underrepresented on the main list. Outreach is not a search for endorsements. It is an attempt to discover whether the official diagnosis is recognisable outside the drafting circle.

Responses should be reported without inflated representation claims. One small provider does not speak for all small providers. Its evidence can still falsify an assumption about cost. One national registry may show that a proposed “regional simplification” creates a conflict in a delegated system. Quality and relevance matter more than constituency arithmetic.

If affected groups remain absent, the final finding should state the limitation. Decision may still be necessary, but confidence should be calibrated. A public institution earns trust by saying which perspective it could not test rather than using openness of subscription as proof that every interest was heard.

Competing formulations are more useful than binary objections

Policy debate commonly asks entities to support or oppose the proposal. This forces diagnostic disagreement into a negative posture. Someone who believes the author identified the wrong cause may appear hostile to action even when they want a stronger intervention.

Competing problem statements create a more informative record. Entities could submit a short alternative containing the condition, affected parties, mechanism, scale, baseline and uncertainty. Chairs could group compatible formulations and identify the few propositions on which they differ.

Suppose an author says unused allocations reduce fair access. An alternative says inaccurate registry records, not non-use, prevent informed administration. A third says both are symptoms of incentives created by transfer rules. The community can then request data that distinguishes them: utilisation evidence, update rates, transfer behaviour and examples of denied requests. Debate moves from moral labels toward testable mechanisms.

Alternatives also reveal false unity. Two supporters may favour the same text for incompatible reasons. One expects it to conserve resources; another expects it to accelerate transfers. If both mechanisms cannot occur together, the apparent coalition is fragile. A clear diagnostic record tells implementers which outcome to monitor and gives future reviewers a basis for correction.

Chairs need not turn every formulation into a formal branch. They can publish a concise map: accepted facts, disputed causes, affected interests, uncertainties and implications for the remedy. The author can revise voluntarily, or the community formulation can stand beside the original.

This practice rewards constructive dissent. Instead of demanding that an objector defeat the author's case, it asks them to offer a better account. The burden remains reasoned and public. Consensus becomes convergence around an explanation sufficient for action, not exhaustion around one person's paragraph.

Version control should include the diagnosis

Most policy archives preserve successive operative texts. They show draft numbers, redlines and dates. The problem statement may change with each version, but those edits receive less attention because they do not directly alter the rulebook. That is a mistake.

A small diagnostic edit can transform the mandate. Changing “some applicants experience delay” to “the current policy prevents timely access” moves from observation to causation. Replacing “may create inconsistent outcomes” with “creates inequitable treatment” changes both confidence and principle. Removing a reference to cost can erase a constituency from later balancing.

Every version should therefore include a diagnosis diff and a brief reason. The archive should identify who proposed the change and which public evidence supports it. Chairs should flag material reframing at phase transitions just as they flag material policy-text changes.

Versioning does not require bureaucratic software. A stable page can display the original submission, current community statement, prior formulations and a table of major edits. Links to relevant messages or meeting segments allow a reader to verify the account. The important feature is conceptual traceability.

Traceability protects authors too. A critic cannot fairly attribute a later institutional claim to the original proposer. It also prevents retrospective certainty. If the first version described a risk and the final version describes a demonstrated harm, the archive should reveal what evidence justified the change. If no evidence arrived, the escalation is visible.

Future policy evaluation depends on this record. Reviewers can ask whether the diagnosed harm declined, whether an assumed mechanism appeared and whether unanticipated effects came from the remedy or a mistaken premise. Without a versioned problem, evaluation degenerates into checking whether staff implemented the words.

Chairs must identify what kind of consensus exists

A chair's summary often compresses a multidimensional debate into “support,” “opposition” and “no new arguments.” The summary should instead separate consensus on diagnosis, principles, remedy and text.

The community may agree that a condition is harmful while lacking agreement on a policy response. It may agree on a direction but dispute thresholds. It may accept the text pragmatically while holding different causal beliefs. These are not failures. They are distinct levels of agreement with different implications for implementation and review.

Before moving from discussion to detailed review, chairs should publish a diagnostic finding. It can state which facts appear accepted, which causal claims remain contested, whose impact is supported by evidence, which uncertainties are material and why policy action remains justified. Entities should have an interval to correct the summary.

This is not a preliminary vote. Rough consensus concerns reasoned treatment of objections, not head counting. One well-supported challenge to the baseline can require revision even if many entities repeat the author's language. Conversely, several expressions of unease may not defeat a diagnosis where evidence and responses address them.

The finding constrains later overclaim. A final announcement cannot say the community proved hoarding if the diagnostic summary found only uncertainty about use. Implementers know which assumptions require monitoring. Appeals can target a specific omission rather than relitigating the entire proposal.

Chairs also gain protection. Their authority is easier to defend when exercised through staged reasons. Instead of appearing to choose a winner after a long thread, they show how the community moved from observed condition to accepted problem to selected remedy.

The Board should review the chain from problem to power

Board endorsement or adoption is not an opportunity to substitute trustees' preferred diagnosis. It is a check that institutional power follows from a legitimate public process, fits mission and can be lawfully administered. To perform that check, the Board needs more than final text and a statement that consensus exists.

The record should connect five elements: observed condition, public-interest reason for acting, selected mechanism, powers granted to staff and measures of success. A break in that chain is a governance warning. A narrow problem may not justify broad discretion. A speculative harm may not justify irreversible action. A carefully evidenced condition may still be met by a remedy unrelated to its cause.

Trustees should ask who wrote each major formulation and whether affected entities could challenge it. They should examine staff-and-legal analysis without treating institutional caution as a veto. They should verify that late reframing returned to public discussion. Where uncertainty remains, they can require review dates, reporting or reversible implementation.

This role respects bottom-up authority. The Board does not recount supporters or reopen every policy preference. It checks that the community's reasons support the institution's action. If the chain is weak, return with a precise explanation rather than private redrafting.

Minutes should identify the version and the principal diagnostic finding. A bare adoption entry erases the reason for power and makes later evaluation harder. Public accountability requires knowing not merely that a rule passed but what failure it was authorised to correct.

Appeals need access to framing decisions

An appeal confined to procedural dates cannot address the most consequential error: a chair or council may have treated the author's premise as settled despite substantial public evidence to the contrary. The calendar can be perfect while the decision misdescribes the debate.

Review should ask whether the decision-maker accurately summarised the diagnosis, considered material alternatives, distinguished scope from merit and explained why outstanding uncertainty did not prevent action. It should not ask the appeal body to choose its preferred policy. The remedy for a defective frame is renewed public consideration, not appellate authorship.

Petition mechanisms, such as those in ARIN's process, are particularly useful when an intermediary declines or abandons a proposal. They demonstrate that institutional editors do not possess final control. Yet petitioners need a stable record showing what was rejected. If the council changed the problem statement before abandonment, supporters may be petitioning for a proposition no one can identify.

Appeal design should preserve practical thresholds. Every disagreement cannot suspend policy indefinitely. A challenger should identify a material diagnostic claim, evidence or affected interest omitted from the finding and show how it could alter the remedy or authority. The reviewing body should publish a reasoned response.

The existence of review improves first-instance behaviour. Chairs who know their framing summary can be examined are more likely to distinguish the author's words from community findings. Councils are more likely to document merger and revision choices. Authors gain a route other than accusing the entire process of bad faith.

Evaluation should test the premise, not only compliance

After adoption, institutions usually ask whether the rule was implemented on time, whether systems function and whether requests are processed. These are necessary operational checks. They do not show whether the policy solved the problem.

Evaluation should return to the versioned diagnosis. If the problem was unpredictable treatment, measure outcome variance and user experience. If it was a conservation concern, define what observable result would indicate improved stewardship. If it was inaccurate registration, track quality without assuming that more fields or more refusals equal accuracy. If it was delay, separate policy effects from staffing and demand.

The analysis must include distribution. An average improvement can conceal concentrated harm to smaller or less-resourced members. A rise in successful requests may coexist with increased deterrence among people who never apply. Complaint data can fall because the issue improved or because confidence in redress declined.

Unexpected results should permit reframing. The community may discover that its original causal theory was wrong even though the rule produced some benefit. Admitting this is institutional learning, not failure. A revised problem statement can support adjustment or repeal.

Policy review becomes more honest when success criteria were public before implementation. Otherwise, supporters can select favourable outcomes and opponents can select costs. The diagnostic record disciplines both. It tells the institution what it claimed to know when it exercised power.

A practical constitutional standard

The process need not become a seminar on language. A workable standard can fit within existing RIR stages.

At intake, preserve the author's exact statement and require its claimed condition, baseline, affected parties, mechanism, evidence and uncertainty. During early discussion, invite alternative formulations and ask who is missing. Before detailed text review, chairs publish a community diagnostic summary with accepted facts and disputed claims. Staff analysis then tests effects and implementation assumptions without silently rewriting the public-interest premise.

Every material change receives attribution and a reason. Scope rulings identify the governing boundary and an avenue for the excluded portion. Consensus announcements state separately whether agreement exists on the problem, governing principles, remedy and exact text. Board materials connect those findings to institutional authority. Post-adoption review tests the original premise and distributional effects.

The standard also needs restraint. Not every policy requires perfect causal proof. Number-resource governance often acts under uncertainty. The requirement is proportional confidence and visible qualification. A low-risk reversible clarification can proceed on a plausible concern; a broad discretionary power needs stronger evidence, wider notice and closer review.

Nor does every entity gain a veto by offering another formulation. Alternatives must be reasoned and responsive. Chairs can conclude that an objection has been adequately considered. What they cannot do is treat the first author's frame as neutral merely because it arrived first.

This is constitutional because it concerns who may define the public reason for institutional action. Procedures governing that definition deserve the same care as voting eligibility, chair selection and appeals.

The right question comes before the right answer

Bottom-up governance is often praised because anyone can propose and anyone can comment. Those guarantees are incomplete if entities may debate only inside a diagnosis chosen by the first author or refined invisibly by institutional actors.

The problem statement is where facts become priorities. It selects a baseline, names the injured interest, attributes cause and establishes the burden that a remedy will be judged against. That power cannot be eliminated; every decision needs a frame. It can be distributed, attributed and reviewed.

Authors should continue to bring strong cases. Staff should continue to provide operational and legal evidence. Councils should continue to turn public concerns into coherent text. Chairs should continue to decide whether objections have been adequately addressed. Boards should continue to protect mission and lawful administration. The reform is to make each contribution visible and prevent any one role from converting its perspective into an uncontested premise.

A mature registry community should be able to say who wrote the original problem, how others challenged it, what evidence changed it, what uncertainty survived and why the accepted formulation justified the final rule. If it cannot, the archive contains a policy but not the public reason for the policy.

The most important consensus call may therefore occur before the familiar debate over clauses. It is the finding that this is the problem the community is trying to solve. Get that finding wrong and elegant text can institutionalise a misconception. Get it right and disagreement over remedies becomes more productive, because everyone can see the question to which the rule must answer.