Summary

  • Face-to-face discussion is valuable because entities can clarify claims, expose trade-offs and adapt proposals in real time. APNIC formally considers meeting, mailing-list and remote participation, while IETF guidance requires materially new meeting decisions to return to the mailing list.
  • A microphone queue is an access mechanism, not a representative sequence. Early contributions frame the problem; repeated speakers can create apparent momentum; status and language affect who approaches; and a closing deadline compresses late objections.
  • Show-of-hands, online gauges and humming can help chairs locate issues, but official guidance warns that they are not votes. Volume, persistence and loudness cannot substitute for reasoned treatment of objections.
  • Chairs should manage the floor to improve evidence: publish the question, alternate new and repeat speakers, protect remote turns, time-box repetition, ask for the strongest objection, state what has changed, and leave room for corrections before any directional gauge.
  • The meeting record must distinguish attendance, speaking opportunities, arguments, affiliations, unresolved objections and subsequent mailing-list confirmation. A transcript alone does not show who tried to speak, who could not participate or how sequence affected the discussion.
  • The defensible consensus finding is a reasoned synthesis across channels and time. The microphone can discover and test arguments; it must not become a queue that allocates constitutional weight.

A queue creates a story before it creates evidence

Meeting discussion unfolds as narrative. The proposal author presents a problem and preferred response. The first commenter may endorse the aim, challenge a premise or ask a clarifying question. Every later speaker enters a conversation changed by what came before. By the time the fifth person reaches the microphone, the room may already understand the issue as a binary choice that the first two speakers defined.

This sequential character is unavoidable. Human conversation cannot occur simultaneously. The governance error is to treat the resulting order as though it were a neutral sample of community opinion.

The first intervention has agenda-setting power. A speaker who calls the proposal a fairness measure invites later entities to explain why fairness permits or rejects it. A speaker who calls it an operational simplification directs attention to cost. Even a question can settle assumptions: “How soon can staff implement this?” presumes implementation should occur. Later objections may sound off-topic because the topic has already narrowed.

Order also creates social information. A line of respected operators expressing support can make an uncertain entity less willing to raise a contrary concern. A forceful early objection can encourage others to add details or persuade supporters that the room is hostile. Visible queue length tells people whether their contribution will delay the session. Chairs' facial expressions and follow-up questions signal which speech counts.

None of these effects means entities are irrational or chairs manipulative. They are ordinary properties of live deliberation. Rough consensus remains possible if the institution treats sequence as a condition to manage rather than evidence to count.

The open microphone is open in a narrow sense

An “open mic” usually means the chair does not preselect speakers by membership or viewpoint. Anyone present may stand in line, and remote tools may offer a text channel. This is a meaningful safeguard against formal exclusion.

Practical access remains uneven. A entity must be in the room or connected at the right local time, understand the agenda, follow the discussion quickly enough to formulate a point, feel comfortable speaking publicly and know the forum's norms. They may need to speak in a second or third language. An employer may view visible disagreement as risky. A smaller operator may be represented by one person covering several simultaneous sessions.

Physical design matters. A microphone at the centre of a large hall exposes the walk and wait. People seated far away may decide that the session will close before they arrive. A person with mobility, hearing or sensory constraints may face costs invisible to the chair. Remote entities experience delay, dropped audio, interface confusion and uncertainty about whether their text entered the queue.

Status changes the psychological threshold. A long-time policy author can improvise in familiar vocabulary. A first-time attendee may have direct operational evidence but hesitate to contradict a former chair, director or senior engineer. “Anyone could speak” records formal permission, not equivalent ability.

The chair's consensus statement should therefore avoid using an open microphone as proof that all relevant objections would have appeared. It proves that a channel existed. The quality of opportunity depends on queue management, notice, remote parity, language and later confirmation.

Early speakers define the question

The policy text may be published in advance, but the live question is often created in the room. A presenter emphasises selected facts, the chair frames the requested decision and early speakers identify what they believe is at stake. This can differ from the mailing-list record.

Suppose a list debated whether a registration requirement is measurable and fair. At the meeting, the author leads with urgency and depleted supply. The first two speakers discuss conservation. A entity who raises measurability may now appear to revive a secondary detail, even though it was central online. The room's working memory has displaced the archive.

Chairs can reduce this effect by opening with a neutral issue map. It should state the exact question, major arguments from the list, material changes, known objections and what kind of conclusion is sought. The map does not prevent advocacy; it ensures the first live voice does not erase prior work.

The chair should also ask whether the framing is complete before inviting positions. A brief correction stage allows entities to restore missing issues. This is especially important when the proposal has changed shortly before the meeting.

Meeting slides should separate the author's case from the chair's summary. Otherwise institutional presentation may make advocacy look like settled fact. Remote entities need the same material at the same time.

The goal is not to eliminate framing. It is to make the frame plural and revisable before sequence hardens it. Rough consensus begins with a fair account of the question, not merely a fair chance to line up after someone else defined it.

The repeat speaker has compounding influence

Experienced entities often contribute several times because they understand the history and can respond to new points. Their knowledge is valuable. Repetition becomes distorting when the number of turns is mistaken for breadth or when frequent intervention consumes the attention needed for new evidence.

One person may support a proposal, answer an objection, clarify an example and return during the final gauge. A transcript then contains four supportive interventions. Another entity may offer one carefully evidenced concern. Message or speaker counts make support appear four to one even though two people spoke.

Compounding influence is not only arithmetic. Each return lets the experienced speaker refine the room's language and answer immediately. A quieter entity's point may receive several rebuttals before anyone from a similar perspective reaches the microphone. The apparent balance at the end partly reflects turn allocation.

Chairs should distinguish first turns from repeat turns and prioritise people who have not spoken. They can invite concise responses from the author after a cluster of comments rather than after each one. Repeat intervention should be allowed when it introduces evidence or corrects a factual error, not merely to restate a position.

The meeting record should identify unique speakers and independent organisations cautiously, alongside turns. Affiliation is imperfect and personal views should not be converted into organisational mandates. Still, the distinction between one voice four times and four independent voices once is material.

Rough consensus values reason over count, so one repeat speaker may still make decisive arguments. Queue rules do not reduce the weight of those reasons. They prevent access frequency from masquerading as additional community support.

Microphone order rewards fluency under pressure

Live sessions favour people who can analyse and speak quickly. Policy questions may involve definitions, historical text, legal effects and operational edge cases. A entity who needs time to verify an example may miss the queue. A confident speaker can offer a plausible claim that frames the next ten minutes before correction arrives.

Language intensifies the difference. RIR regions include many linguistic communities, while meetings often rely on one or a few working languages. A person may read technical English comfortably yet need more time to formulate a precise objection aloud. Humour, idiom and fast cross-talk raise the cost. Remote text can help, but only if moderators integrate it without delay.

Fluency is not the same as expertise. The engineer closest to an operational problem may be cautious and specific. A professional representative may express a broad position elegantly with less direct evidence. Chairs must evaluate substance, but sequence makes fluent claims easier for the room to remember.

Useful design includes advance written questions, visible timers, an option to submit text for reading, interpreters where feasible and a post-session list interval. Chairs can pause after a complex claim and ask for evidence rather than allowing speed to create fact.

Presenters should publish slides early enough for entities to prepare. Last-minute material privileges people able to improvise and disadvantages remote readers. Material changes should not receive a final consensus call before equivalent written review.

A live forum can reveal misunderstanding rapidly, which is one of its strengths. It should not turn rapid expression into a qualification for constitutional influence.

APNIC formally looks beyond the room

APNIC's Policy Development Process provides a useful institutional statement: opinions expressed at Open Policy Meetings, on the Policy SIG mailing list and through remote participation are considered by the chairs. Anyone interested in number-resource management may join the list and participate in person or remotely.

The process begins before the conference. Proposals are posted to the list at least four weeks before the meeting, allowing people who cannot attend to contribute and authors to refine text. At the meeting, chairs may use a show of hands or online tools to gauge support, but APNIC's public explanation says the gauge is not a vote and that earlier list discussion is among the additional factors.

This architecture rejects microphone sovereignty. The room is a deliberative stage, not the whole constituency. A proposal that appears popular in the session can still face a substantial list objection. A quiet room does not erase written support or concern. Remote entities are not observers added after the real decision.

The challenge is implementation. “Considered” must be visible. The chair's conclusion should identify major list arguments, what the meeting added, how remote input was handled and whether the final text differs from the one discussed in advance. Otherwise the formal multi-channel promise cannot be audited.

APNIC also uses subsequent confirmation stages after meeting consensus. That creates an opportunity to test whether live momentum survives asynchronous review. The final period should not be treated as a ceremonial silence test. It should expose the meeting's exact conclusion and invite correction from people whose evidence could not enter the microphone queue.

The process recognises the right principle: the room contributes evidence; it does not define the community.

IETF experience warns against counting sound

RIR policy communities share deliberative practices with the IETF, where rough consensus has received unusually explicit analysis. RFC 7282 warns that humming should not be treated as an anonymous vote and that loudness does not establish consensus. A hum can locate a starting point for conversation; it should begin inquiry rather than end it.

The warning applies directly to microphone queues. Several concise endorsements can sound like a dominant view. A long line can look like a coalition. Yet rough consensus asks whether objections have been honestly considered and whether the group has understood the consequences, not which side generated more audible activity.

RFC 2418 similarly states that dominance is not determined by volume or persistence. It recognises mailing-list participation as available to a wider base than meeting attendance and requires decisions on new or materially different meeting issues to be reviewed on the list. This guards against accidental government by travel and time zone.

A chair may still use a directional gauge. The useful question is diagnostic: is there enough support to continue refining this option, is an objection widely shared, or does the room understand the choice? The result should trigger questions. Why did people choose that direction? What concern drives the minority? Is anyone unable to accept the consequence?

The chair should state before the gauge that it is not a vote, identify who is eligible or invited to respond, include remote entities and publish the question exactly. Afterward, the discussion must address reasons. A decibel impression is not a decision record.

Sound is valuable for orientation. It is dangerous as authority.

The chair controls more than the queue

Chairs decide when discussion begins and ends, who receives follow-up, whether a comment is in scope, when the author responds, which points are summarised and when the room is asked for direction. These are necessary powers. They also shape apparent consensus.

A chair can unintentionally privilege a view by paraphrasing it sympathetically, allowing its advocate more time or asking opponents to be brief because the schedule is slipping. A sceptical question from the chair can signal that an argument lacks standing. Announcing “we have heard this before” may discourage a new speaker whose evidence differs from the repeated claim.

Co-chair models distribute judgment but do not automatically remove bias. Chairs may divide tasks while sharing assumptions. One should actively monitor queue fairness, remote input and missing perspectives while another manages substance. A designated process observer can note attempted interventions and time allocation.

Chairs should disclose when they speak personally, for an employer or in their chair role. RIPE's chair guidance explicitly encourages clarity about these capacities. A substantive chair opinion is permissible in many communities, but entities need to know when the person controlling the floor is also advocating.

Recusal or transfer of facilitation may be appropriate where a chair authored the proposal, has a direct institutional interest or became a central advocate. The threshold should be published and proportionate; experienced chairs inevitably have views.

Authority becomes legitimate through method: a known agenda, neutral issue summary, balanced access, accurate restatement and reasoned finding. The microphone button is a constitutional instrument because it controls what evidence can become audible before judgment.

Time scarcity changes the burden of speech

Meeting agendas are finite. Sessions start late, presentations run over and rooms must clear. The final proposal of the day may receive less discussion than the first. A queue that appears open for ten minutes is not equivalent to one open for forty.

Scarcity changes who must bear delay. A person raising a late objection may be told to continue on the list, while supporters benefit from a meeting gauge already taken. If list confirmation is weak or treated as secondary, postponement disadvantages the objection. Conversely, allowing unlimited repetition can let one entity prevent any conclusion.

Chairs should publish minimum discussion expectations and avoid final calls when material new issues emerge near the end. The remedy need not be endless floor time. Record the issue, ask for a focused written exchange, state that meeting direction is provisional and set a date for a reasoned conclusion.

Agenda design can reserve a protected objection interval before any gauge. Authors and known supporters should not consume it. Entities can submit concerns in advance for inclusion even if they cannot attend. The chair can group duplicates while preserving distinct mechanisms.

Time use should appear in the record: presentation length, discussion length, number of first and repeat speakers, remote turns and whether the queue was closed with people waiting. These measures do not decide legitimacy, but they reveal whether “the room had its say” is accurate.

Efficiency is a real public interest. Meetings cannot deliberate forever. Legitimate closure depends on transferring unfinished evidence to an authoritative channel, not on pretending the clock resolved it.

Remote participation is often sequenced as secondary

Remote access has improved RIR meetings, but parity requires more than a webcast and chat box. A remote comment may pass through a moderator, arrive after room speakers, lose tone when read aloud or be omitted because the session ends.

The interface itself creates hierarchy. In-room entities see the queue and can judge when to approach. Remote entities may not know whether their comment was accepted, where it sits or whether a follow-up is possible. Audio delay makes interruption awkward. Time zones impose fatigue that a nominally open connection does not cure.

Chairs can alternate room and remote turns, display queue status, allow remote speakers to use audio, and have a dedicated moderator with authority to stop the room. Written contributions should be read in full where concise or summarised with the entity's confirmation. Remote questions submitted before the session should be included.

A separate online gauge should not be silently combined with a room show of hands if eligibility, timing or question differs. Results should be reported by channel and used diagnostically. A person should not be counted twice merely because they are present and logged in.

When technology fails, the record should say so and the decision should wait if affected participation is material. Institutional embarrassment is less important than accuracy. Reopening a list interval is a simple remedy.

Remote parity also helps regional breadth. Travel cost and visas shape who enters a microphone line. A consensus claim that ignores unequal channel operation may reproduce geographic concentration while describing itself as open.

Affiliation concentration can look like breadth

A queue of ten people can represent ten independent networks, one employer, several related companies or a professional circle with shared incentives. Visual variety does not establish institutional independence.

Affiliation information should be collected and reported carefully. Entities may speak personally, hold multiple roles or have consulting relationships. The meeting should not force invasive disclosure or assign an employer's position without consent. A simple statement of relevant affiliation and speaking capacity is usually enough.

Concentration matters because meeting presence is resource intensive. Large registries, vendors, operators and associations can send several specialists. Small networks may send one person or none. If several employees of one organisation speak, their technical reasons deserve consideration; their number should not be interpreted as wider constituency support.

Chairs can invite new organisations and regions before repeat speakers. They can note when a line is concentrated and ask whether anyone with a different operational setting has evidence. This is not a quota or a presumption that organisations vote as blocks. It is an effort to test generalisation.

The transcript should preserve declared affiliations, while the consensus summary can state estimated independent breadth with uncertainty. Counts remain contextual, never dispositive. One concentrated group may possess the most relevant expertise. One outside operator may identify an effect everyone else missed.

Breadth strengthens confidence when reasons survive across independent contexts. It should be demonstrated, not inferred from bodies standing in a line.

Applause, laughter and silence are not votes

Rooms communicate beyond formal turns. Applause rewards a statement. Laughter can expose absurdity or humiliate an uncertain speaker. Silence after a chair's question may signal agreement, confusion, fatigue or reluctance. These cues affect subsequent participation.

Chairs should avoid narrating them as consensus. “The room clearly agrees” after applause converts spontaneous expression into an institutional finding. “No one objected” after a complex question may ignore that entities were still processing or believed the queue had closed.

Where a cue appears important, ask a precise follow-up. What proposition drew approval? Is there a material objection? Does anyone need time to respond on the list? The translation from atmosphere to policy must pass through reasons.

Codes of conduct matter here. A room in which sceptical speakers are mocked cannot rely on silence as evidence. Chairs should intervene against personal dismissal and restore the substance of the point. The objective is not to sterilise disagreement; it is to preserve a usable floor.

Meeting minutes rarely capture atmosphere, which can make a later archive look more balanced than the experience. A process observer may note disruptions, queue closure or technical failures without evaluating personalities. Video can help but does not replace a reasoned summary.

Rough consensus depends on whether people can state and test objections. Social cues are evidence about the participation environment, not evidence that the underlying policy is accepted.

The strongest objection should receive protected time

Consensus quality improves when chairs deliberately seek the strongest unresolved objection rather than moving through every turn as equal fragments. A well-supported concern can matter more than many endorsements.

Before a final gauge, the chair should summarise the strongest objection in terms its proponent recognises. The objector can correct the summary. The author or supporters can respond. The chair then asks whether the response addresses the mechanism or merely states a different preference.

Protected time prevents queue order from burying the concern. An objection raised early may have been diluted by later topics; one raised late may lack response time. Returning to it creates a common focal point.

The practice also disciplines opposition. Entities cannot preserve a veto through vague discomfort. They must identify the consequence, evidence and condition under which the concern would be resolved. If the group has adequately considered it and accepts the trade-off, rough consensus can proceed without unanimity.

More than one material objection may exist, but the list should remain manageable. Chairs can maintain an issue table across the mailing list and meeting, recording status and references. Repeated turns then update an issue rather than create apparent new votes.

A final finding should explain why each unresolved objection does or does not prevent consensus. That explanation, not the queue's direction, is the constitutional act. Protecting the strongest objection makes the finding more defensible for supporters because it shows the decision survived serious scrutiny.

New text should not ride meeting momentum

Live debate often produces valuable compromise language. An author may change a threshold, add an exception or narrow scope in response to the room. Enthusiasm for resolution can encourage an immediate consensus call on wording few entities have read.

This is where sequence becomes most dangerous. The people still present hear the negotiation; remote and absent entities do not. A late compromise may reflect the last speakers rather than the broader discussion. Small textual changes can alter obligations unexpectedly.

RFC 2418's principle is sound: decisions on issues not discussed on the list, or materially different from prior list consensus, must return to the list. RIR communities should apply the same rule strictly. A meeting can record directional support for a concept, but exact revised text needs asynchronous review.

The author should publish a marked comparison and explanation. Chairs should state whether the change is editorial or substantive and invite challenge to that classification. The confirmation period must be long enough for relevant regions and languages.

This does not waste the meeting. The room may have accomplished the hard work of identifying a compromise. Written confirmation tests precision and includes people outside the sequence. If no new concern appears, the chair can conclude with stronger evidence.

Momentum is emotionally valuable but constitutionally weak. Policy endures after applause and travel end. The authoritative text should survive a channel where every entity can inspect the same words.

Minutes need more than a speaker list

Meeting records often contain a transcript, video, slides, attendance list and short minutes. These preserve speech but do not automatically explain deliberation.

A transcript overrepresents what became audible. It does not show people who abandoned the queue, remote comments not read, confusion caused by technology or points withheld because time was called. It also makes repeated speakers appear repeatedly without indicating concentration.

The consensus record should add structured context: exact question, proposal version, prior mailing-list issues, attendance by mode, unique speakers, repeat turns, declared affiliations, remote contributions, queue closure, directional gauges, material objections, responses, text changes and next steps. Privacy and uncertainty should be respected.

Minutes should distinguish observation from judgment. “Eight people spoke in support” is an observation if classification is accurate. “The community strongly supported” is a conclusion requiring broader reasoning. “No objection was voiced in the room” does not mean no objection existed on the list.

Chairs should publish a draft promptly and allow factual correction. Entities can identify a misattributed view or omitted remote point. Video remains a verification source, while the summary provides an accessible map.

Good minutes reduce dependence on status memory. Months later, a reader should not need to trust that regular attendees remember the room's mood. They should see the reasons, limitations and channel transitions that produced the finding.

Mailing-list confirmation must be substantive

Sending a meeting result to the list is not enough if the message says only that consensus was reached and invites objections. People outside the room need the reasoning and exact text to respond intelligently.

The notice should summarise the meeting's argument map, strongest objections, chair dispositions, gauge purpose and result, material changes, queue limitations and questions still open. It should make clear that reasoned new information can affect the conclusion. A deadline and accepted languages should be explicit.

Silence should be interpreted conservatively. It may permit a well-supported meeting finding to stand; it cannot broaden that finding into proof that absent subscribers agreed. If known list objectors do not respond, their earlier position remains part of the record unless expressly withdrawn or addressed.

Substantive comments deserve answers. A chair should not dismiss them as “too late” when the meeting introduced new text or framing. Repetition can be linked to a prior disposition, while genuinely new consequences receive analysis.

The final statement should explain how meeting and list evidence fit. It may conclude that the room found a direction, written review confirmed exact text and no material objection remained untreated. Or it may return the proposal for revision.

This stage corrects sequence. Asynchronous participation lets readers choose when to formulate, cite sources and compare versions. It is slower than a microphone but wider and more precise. Consensus gains legitimacy when both forms of deliberation perform what each does best.

Queue data can diagnose participation without deciding policy

Institutions can learn from meeting access if they collect modest aggregate data. Useful measures include session length, unique speakers, repeat-turn share, room and remote turns, first-time contributors, declared independent organisations, geographic spread where voluntarily available, gender balance at an aggregate level, queue closure and technical failures.

These measures should never become a turnout threshold or substitute for reasons. A session with three expert speakers may resolve a narrow issue well. A session with forty speakers may repeat slogans. Data diagnoses access and concentration.

Longitudinal patterns matter. If the same small group takes most turns across years, outreach or chair practice may need change. If remote comments routinely appear at the end, moderation should be redesigned. If women or entities from certain subregions are persistently absent from microphones despite attendance, the institution should investigate barriers.

Publication encourages improvement without naming ordinary entities unnecessarily. Chairs can compare planned and actual discussion time, experiment with first-speaker priority or written queues and report results. Communities can decide which practices improve substantive diversity.

Data also calibrates claims. A consensus announcement can accurately say that discussion included a certain range of independent operational contexts rather than invoking “the whole region.” Modest language strengthens rather than weakens authority.

The aim is evidence about the forum, not surveillance of individuals. Collect only what serves participation quality, disclose method and preserve voluntary identity choices.

Deliberative design can change the order

The queue need not be first-come, first-served from start to finish. Chairs can structure turns to counter predictable concentration while retaining spontaneity.

Begin with clarifying questions, then invite evidence of impact, then arguments about remedy. Give first-time speakers priority within each stage. Alternate support, concern and neutral inquiry where positions are known, without forcing false symmetry. Reserve author responses for clusters. Integrate remote turns throughout.

For complex proposals, small facilitated groups or pre-meeting online sessions can surface issues, provided conclusions return to the public list and main session. Anonymous question submission can lower the threshold for clarification but should not carry hidden policy positions without accountable reasoning.

The chair can ask targeted invitations: anyone from a small provider, national registry, implementation team or previously absent economy with relevant evidence? Such invitations seek experience, not representatives. People remain free to decline.

Visible issue tracking reduces repetition. A screen can show accepted facts, open objections and questions, but it must avoid readable policy decisions being mistaken for a live vote tally. The authoritative record remains written after the session.

No design removes power from facilitation. It can distribute opportunity more consciously. The right sequence is the one most likely to expose distinct reasons and let them answer one another, not simply the order in which confident attendees reached the stand.

Closure should be announced as a reasoned transition

When time is sufficient and issues have been addressed, chairs must close. Endless discussion rewards persistence and can give a determined minority a practical veto. Closure is part of fair governance.

The announcement should not rely on atmosphere. The chair should state the exact proposition, accepted evidence, outstanding objections and why those objections have been adequately considered. If a gauge was used, explain its limited role. Identify whether the result is provisional pending list confirmation or final under the applicable process.

People still waiting should be recorded and given a route to submit. A late material point may reopen the issue; a repeated point can receive the existing answer. The standard is substance, not position in line when the clock expired.

Where chairs are uncertain, they can defer the finding without pretending no progress occurred. Publish a summary and focused questions. Delay should have a timeline so uncertainty does not become quiet abandonment.

Appeal or reconsideration routes should examine whether chairs accurately treated evidence and access, not recount the room. Video and queue records can support review. The remedy for a materially unfair sequence may be renewed discussion and list confirmation.

A reasoned transition gives everyone the same account of what happened. Supporters know what was decided; objectors know why they did not prevail; absent entities know what can still be challenged. The microphone session becomes one documented stage rather than a sovereign moment.

The microphone should discover, not allocate, authority

Live deliberation remains irreplaceable. People can ask immediate questions, see uncertainty, negotiate language and discover that an apparent disagreement rests on different definitions. Trust can grow through direct exchange. The answer to queue distortion is not to move every interaction into email.

The constitutional limit is simple: access order must not determine argumentative weight. Early framing should remain challengeable. Repeat turns should not become extra support. fluent delivery should not outrank operational evidence. Remote delay should not become absence. A clock should not transform an unheard objection into assent.

Chairs can honour that limit through neutral issue maps, protected first turns, remote alternation, strongest-objection review, careful gauges, transparent records and substantive mailing-list confirmation. They should write conclusions that connect reasons across channels rather than describe the room's mood.

Communities should also moderate their own habits. Experienced entities can yield the floor, disclose capacity, avoid applause as pressure and move detailed citations to the list. Authors can listen before answering every point. Directors and staff can resist using status to close uncertainty.

Rough consensus is not democracy by queue, nor expertise by endurance. It is a judgment that relevant objections were found, understood and adequately considered, and that the group can responsibly proceed despite incomplete unanimity.

The microphone contributes to that judgment when it helps reasons meet. It corrupts the judgment when its order becomes an invisible ballot. An open floor is valuable precisely because it can reveal what a prepared document missed. Its legitimacy ends where the accident of who spoke first is allowed to decide what the community meant.