31.1Expression and endorsement
Asking and endorsing are distinct acts even when they concern the same policy. A person can ask whether a policy will work without supporting its adoption. "Would later hours help?" seeks an assessment of effects; it does not commit the asker to adopting later hours, nor does it delegate any authority to decide. The work of this section is to keep the record of such an inquiry separate from records of preference and permission.
The invented interface does exactly this: it records a submitted question, a recorded endorsement, and an explicit delegation in separate fields. That separation is necessary for any later reading of what occurred. If a single undifferentiated message count were used instead, the act recorded would remain unmarked. Separation is not sufficient by itself, however. The reader must still take each field as registering the act named in it, and the same string of words may appear in more than one field; shared text need not imply shared preference. What differs is the encoding, and the task each encoding fixes: a question requests an assessment, while a proposal puts an option forward for support.
The same discipline applies to ranking, deliberating, and authorizing. Ranking orders options; deliberating offers reasons; authorizing permits action. Asking supplies none of these, although one person may perform several at once. A question is therefore neither sufficient for endorsement nor required before one. Nor is endorsement an inevitable later stage of inquiry: an open question may remain open indefinitely without acquiring any preference attached to it.
A count of participation must accordingly name what it compares — messages submitted, recorded endorsers, or explicit delegators. These tallies take different inputs and measure different things, so a larger figure in one register says nothing by itself about the others.
The interface introduced above keeps three records apart: a submitted question, a recorded endorsement, and an explicit delegation. The question "Would later hours help?" is entered as a question. If the tally counts it as an endorsement of later hours, the tally has imported a preference that the submitted words do not carry. The same holds for delegation: nothing in the question appoints a representative.
That is a claim about the record, not about the person's mind. The asker may privately favor later hours, oppose them, or hold no settled view; the interface records none of these. The narrower point is that the submitted text is not sufficient evidence of an endorsement. Endorsement is not necessary for holding a preference, and holding a preference is not sufficient for having endorsed: endorsement is a further act that the interface must capture if it is to report endorsement at all.
The counting rule also changes what its output compares. A tally of endorsements that mixes questions with affirmations no longer compares participants' affirmative positions on one prompt; it compares two kinds of speech act under a single label. To test an encoding, hold the task and the submitted texts fixed — say, the task of identifying who endorses adoption — and vary only the rule that maps texts to records. Any difference in the tally then belongs to the encoding.
A conditional qualification: suppose a submitted question openly urged later hours. Its wording may then express a position, so a rule that reads it as endorsement is tracking its content rather than supplementing it. Whether that is so depends on what the words commit the speaker to, judged case by case. Even then, expressing a view and authorizing an action remain distinct acts that the records should not collapse.
31.2Preference and intensity
A ranking places options in an order under a given question. The order says that, relative to that question, A ranks above B; it says nothing further about how much. This is a matter of what the elicited item compares: the rank is ordinal, fixing the direction of preference, not its magnitude. Two respondents can therefore yield identical orders while differing radically in intensity—one mildly preferring A, the other treating B as unacceptable. The coincidence of ranks is compatible with both cases; equal preference strength is neither entailed nor made likely by it. In the stipulated case, two respondents both rank A above B and give no intensity scale. Their matching orders establish only the shared direction of preference.
Care is needed on a sufficiency point. A rank is sufficient to establish that the respondent placed A above B under the question asked. It is not sufficient to establish that the respondent endorses any broader option, accepts the framing of the question, or would prefer A over B under a different question. Nor does the rank establish that the preference is stable, decisive, or reflective; these are separate properties that the order does not measure. Strong intensity is possible, then, but not inevitable: an order might accompany a slight or an overwhelming preference, and no reading of the rank alone decides which.
The converse inference also fails: equal intensity, if it is to be claimed, requires comparison of magnitude on a common basis, and the matching orders supply no such comparison. The rank's evidential reach ends at ordinal direction. Any design that treats a shared order as a shared intensity would add to the submitted expression a preference the submitted expression does not contain.
Suppose the two respondents who give the same order must be distinguished for a decision that weighs degrees of support. The rank alone cannot do that work, so the interface has to ask something further. A rating with stated anchors asks where an option falls on a fixed scale. A tradeoff question asks what concession would restore indifference between two options. A fixed budget of points asks how support divides when it cannot exceed that budget. Each is a separate elicitation, and each names a different quantity: position on a scale, a concession that balances two options, or a share of a constrained allowance.
Comparisons must hold the question, the option set, and the elicitation fixed. Numbers drawn from different instruments do not compare cleanly, because the instruments record different things. Conditional supposition: if both respondents rate A at 7 and B at 3 under the same anchored scale, the difference compares the two options' reported positions on that scale. It does not show that one person's support is proportionally greater than another's, or that the two use the scale alike. That risk is possible rather than inevitable, but it bounds the claim the numbers support.
Elicitation of this kind is necessary for any statement about strength, and it is not sufficient for comparing strength between people. Conversely, it is unnecessary when the downstream decision consumes only order: a rule that counts first preferences consults just the ordering, so collecting degrees of support adds burden without changing the result of that rule. Whether intensity should be elicited therefore depends on what the later step compares, not on the rank format itself. For the stipulated pair, the shared order leaves strength undetermined; supplying the further question is what could resolve it.
31.3Reasons and recommendations
A reason advances an assessment; a recommendation selects an option for support. The two acts can come apart. A contributor may hold that a consideration bears on an option without concluding that the option should be chosen. That is not a hesitation over wording but a judgment about inferential strength: the consideration may be relevant yet insufficient, outweighed by other considerations, or too weakly weighted to settle anything. Relevance does not supply sufficiency; and since a recommendation can be offered without any stated reason, a reason is not a necessary condition for recommendation either.
The distinction between reason and recommendation narrows what an interface may infer from a submission. If a person attaches a reason to an option, the warranted record is that the author takes the consideration to bear on that option. It does not establish that the author ranks the option first, would authorize it, or even prefers it to the alternatives. Nor does an accumulation of reasons establish a count of supporters: one author may contribute several considerations, while several authors may each stop short of recommending anything. What accumulates is argument around an option, not commitment to it.
The constructive implication is to keep reasons and recommendations as separate records joined only by an explicit transition. If the interface later invites the contributor to recommend the option, that invitation should elicit a fresh answer, because the earlier reason does not predetermine it. Conditional on such an elicitation, both acts can be recorded, and the reason remains visible as the author's ground without having been silently converted into a recommendation. Reasons may then be grouped under an option to show the considerations in play, while recommendations are tallied or ranked as distinct acts.
A reason can bear on an option without settling what the contributor wants done. Suppose someone notes that a proposed measure would reach a neglected area: that observation speaks to the option's merits, but it does not yet say "adopt this." The intermediate position is stable and legitimate — relevant information supplied, commitment withheld. An editor who records every reason as a recommendation erases that position, and with it the distinction between supplying grounds and taking a stand.
The conversion is not a neutral recoding. Providing a reason is not sufficient for recommending the option; recommending is not necessary for the reason to count. What the editor adds is an attribution of commitment that the contributor did not make. Downstream, anything that treats recommendations as preferences — endorsement counts, rankings, delegation triggers — then inherits the unwarranted commitment. The error is systematic rather than occasional, because the practice targets precisely those contributions that stopped short of a choice.
There is a scope limit worth stating. If the contributor separately authorizes the move, or if the interface marks the conversion as an editorial inference that the contributor can accept or correct, the intermediate position is preserved rather than erased. What remains impermissible is a silent upgrade from reason to recommendation. Even where reasons and recommendations are filed separately, care is needed when comparing them: two contributors may draw on the same reason while recommending different outcomes. A measure of shared text or cited ground compares textual overlap, not agreement in preference.
These are design claims about a hypothetical interface, not reports of observed behavior. Their application is accordingly narrow: they specify which fields a record must keep apart, and they do not establish how often contributors in any particular setting offer reasons without recommendations.
31.4Consent to represent
Permission to represent another person can be divided into narrower permissions that the interface should not silently merge. Consent to quote a statement allows the words to be reproduced as evidence of what was said; it does not make those words a standing endorsement of a later summary. Assent to a reformulation is different again: the speaker accepts that particular restatement, not every nearby paraphrase that preserves the apparent point. Delegation to decide is also distinct. It may authorize a choice within a defined question and period without permitting the delegate to attribute personal endorsement to the delegator.
The invented case shows the separation without collapsing the entries. The submitted question, “Would later hours help?”, records that someone asked for consideration. It does not itself record endorsement of longer hours, and it does not authorize anyone to settle the matter. A recorded endorsement can stand alongside that question, as can an explicit delegation, but neither follows from the others. The inference concerns necessary and sufficient conditions: endorsement is not sufficient for delegated authority; delegation is not sufficient for permission to quote or to alter a speaker’s words. Equally, asking the question is not by itself a denial of endorsement. The record is simply silent on that point, and the interface should keep the silence visible rather than convert it into an inferred position.
A further test concerns scope. If, as a supposition, the delegation is limited to answering the submitted question, then it does not decide whether the speaker assents to a reformulation of the statement, and that assent does not enlarge the delegation. The permissions therefore answer different authorization questions. Treating one as evidence of another makes a possible arrangement look inevitable. What must be established is which particular permission was given, for what material, and for what purpose.
Suppose the hypothetical record keeps three things apart: a submitted question, a recorded endorsement, and an explicit delegation. The question "Would later hours help?" contributes only the first. That it might lead someone to endorse later hours, or to want a delegate to choose, is possible; neither follows. Treating the question as endorsement or delegation mistakes a possible consequence for an inevitable one.
Now consider a single control that can carry several meanings. Combining asking, endorsing, and delegating is not wrong in itself; it is legitimate when the combined meaning is stated and the record shows what was combined. Two records may then be compared only after holding fixed the task and the inputs. If one encoding preserves the three permissions separately and another merges them into one act, a count of acts is not a count of the same thing: the merged encoding compares fewer categories, not more agreement.
The shared control is therefore neither necessary nor sufficient for combined consent. It is not sufficient, because the same control might record only a question. It is not necessary, because separate controls could still support an intentional combination if that combination is declared. What matters is whether the record makes the combined meaning explicit, and whether a reader can tell which permission each participant gave.
Scope follows the permission actually recorded: a question covers its subject, an endorsement covers the stated proposition, and a delegation covers the decision the delegate is empowered to make. Applied back to the question about later hours, the safe inference is narrow: the participant asked, and nothing more. Any endorsement or delegation must appear as its own record, so the distinction survives even when the same topic recurs across contributions.
31.5Abstention and uncertainty
Four states often travel under one blank. No response records an absent entry. Lack of knowledge reports that the person could not answer the question asked. Indifference says the available alternatives make no difference to the person. Abstention is deliberate withholding by someone who could have answered. Only abstention is a choice about participation; the others concern information, preference content, or record completeness.
Separating them requires an elicitation that keeps them apart: a distinct abstain control, or a later field naming the state, attached to the same question and the same alternatives. An empty field cannot supply that evidence. Nor is a named entry sufficient by itself. If abstain was the default or a catch-all, selection records the label chosen, not the motive the label suggests. The converse error also appears: absence of a reported preference is not sufficient for indifference, which requires that alternatives were recognized and found equivalent in some relevant respect.
Naming precedes arithmetic. The interface storing only "no response" yields counts of records in that state, not counts of abstentions. A percentage compares those records to a chosen denominator — entries, invitees, eligible persons — and each denominator answers a different question. Collapsed categories cannot be split retrospectively by renaming.
Comparing encodings fixes the task: same question, same alternatives, same population, same moment of elicitation. Any difference then reflects how answers were recorded. Without that hold, a shift may show only that one interface offered abstention as an explicit option. Supposing hypothetically that both encodings were run side by side, indifference would still not turn a blank into agreement with every alternative.
When the interface stores only "no response," the record has not yet earned a richer label. Nonresponse is compatible with several motives: the person may not have seen the prompt, may lack the knowledge the prompt assumes, may be indifferent, or may be deliberately withholding participation. Each of these is a possible explanation; none is inevitable from silence alone. Nor is abstention a sufficient reading: abstention implies a relation to a choice one could have made, which the bare record does not establish. So the ambiguity must be retained rather than resolved by a convenient default.
Suppose, as a design condition, that the system later adds an explicit "prefer not to answer" option alongside "I don't know" and "no opinion." Then and only then can the recorded categories be compared as named quantities. Even here, the labels distinguish responses to the same prompt; they do not measure willingness to participate in some wider process, and they cannot be combined into a rate of "engagement" without first fixing what the denominator counts. A percentage of abstentions is a comparison between an explicitly marked category and a defined population of elicited persons; it is not a measure of the motive behind silence elsewhere in the record. The same caution applies when silence is aggregated across prompts or periods: the combined figure compares unlike absences unless each was recorded under the same elicitation. Naming the quantity before counting it is therefore a prerequisite, not a refinement.
The practical consequence is a limit on inference rather than a ban on design. Silence may later be reinterpreted if supplementary evidence arrives — a follow-up prompt, a stated reason, or a context that makes one motive salient. What the interface cannot do is retroactively convert the stored absence into that motive on the strength of convenience. Until the record supports the distinction, the honest entry is the unresolved one.
31.6Useful hybrid interactions
A hybrid process earns its name only if its stages remain distinguishable after collection. One useful arrangement gathers open questions first and later issues a separate invitation to state a preference. The invented interface illustrates the point by storing three distinct entries: a submitted question, a recorded endorsement, and an explicit delegation. Asking "Would later hours help?" may generate exactly the first entry and nothing else. The wording of the question, and the act of submitting it, carry no endorsement and no delegation; those are additional acts, each requiring its own elicitation and its own record.
What must be true for this separation to hold? Keeping the acts in separate fields is necessary but not sufficient. The downstream comparison must also treat like with like. A count of submitted questions measures something different from a count of endorsements or a count of delegations, even when all three are filed under participation and even when one person supplies all three. Any comparison between two encodings is meaningful only after the task and inputs are fixed: ask both systems to record the same acts, and then let the encodings differ. Otherwise a difference between interfaces may merely reflect that one stored a prompt while the other stored a commitment.
The second step qualifies the first. An explicitly separate preference judgment can be collected only where the interface actually invited one, and only if the invitation is not silently folded back into the question stage. Conditional on such a merge — if any response to a question were also read as a preference signal — the hybrid would collapse into a single ambiguous record, and the system could not report which entry expressed endorsement or which authorized another person to act. The remedy is architectural rather than interpretive: keep the records apart at the moment of elicitation so that later aggregation has distinct acts to compare. Applied here, that rule keeps the question, the endorsement, and the delegation in separate records across both stages.
Suppose the interface that recorded "Would later hours help?" later records a vote for extended hours. That sequence admits several histories of participation, and the vote does not settle which occurred. The question asked for consideration; unless a later act of endorsement was separately captured, it remains a question. Endorsement requires a recorded endorsement, so a subsequent vote by some participants is not sufficient to supply that record for the earlier submission. Shared text across stages does not merge the acts: the wording may be common while the recorded preference is not.
The same discipline applies to delegation. An explicit delegation names a delegate and a scope; the question names neither. If the questioner later delegates, that is a new record, not a reinterpretation of the earlier one. The interface's three fields — submitted question, recorded endorsement, explicit delegation — are therefore not redundant: they answer who raised an issue, who backed a proposal, and who may act for whom. The order of records constrains what later stages may claim, but it does not by itself convert one kind of record into another.
The later vote also says nothing about those who did not take part. Silence is compatible with objection, unawareness, inability to appear, or agreement; acceptance is possible, not inevitable. Inferring consent from non-response would be a distinct design with its own failure conditions, not a consequence of the question-and-vote sequence. The uncertainty attaches to that particular inference: the vote recorded judgments from those who voted, and no more.
Before reading any total, fix the inputs being compared. Submissions, contributors, endorsements and delegations count records of different acts, taken at different moments and under different permissions. Holding the displayed figure constant while changing which records enter the count changes what the figure reports, so an apparently identical number may no longer answer the question being asked of it.
31.7What the displayed total means
A single number at the top of a participation interface seems to answer "how much participation was there?" It answers only "how many of what the system stored?" Three candidates are easy to confuse. A count of submissions tallies entries: if one person sends four messages and another sends none, the total rises by four. A count of contributors tallies distinct people who submitted at least once; the same activity then registers as one. A count of recorded endorsements tallies affirmative marks on one item, and one person may record several or none. Each counts a different act, so naming the act comes before reading the figure: a busy thread and broad agreement are separate quantities, and growth in one is not evidence of the other.
The case of a store that holds only "no response" shows the limit. From those records alone, absence cannot be resolved into lack of knowledge, refusal, indifference, or abstention. Whatever is counted, the unrecorded remain in a residual category that the data does not name. A percentage would not close the gap, since the choice of who belongs in its base is precisely what the records leave open.
The three counts can also be compared only under a fixed comparison. Suppose one encoding records a single response per person per item and another records endorsements per item. If the task and the set of people and items are held constant, any difference reflects the encoding; change the task or the population and the two figures no longer answer the same question. Finally, the sufficiency of a record is narrow. A recorded endorsement is sufficient to place that person among the endorsers of that item. It is not necessary for acceptance that one be recorded, since silence is not refusal, and a record alone does not establish deliberation or authorization.
Several totals may appear beside one another, and each can be correct in its own terms: submissions, distinct contributors, and recorded endorsements answer different questions about the same participation. The discipline is to attach the label where the number is displayed, not to decide afterwards which reading supports the argument. Their values may diverge whenever one person submits more than once or when endorsement is recorded independently of submission; such divergence is a property of the tally and is not itself evidence that any figure is wrong. Nor is divergence inevitable: the totals coincide under stricter conditions, such as one submission per contributor carrying exactly one recorded endorsement.
A proportion places a further demand. It commits the reporter to a numerator and a denominator drawn from the same population at the same point in the process, with the numerator a subset of the denominator; without that relation the ratio has no scope. It is possible for a proportion to be arithmetically well formed and still answer a question that was never posed, as when the denominator silently shifts from those invited to those who responded. Naming the count first constrains what the denominator may contain.
Naming, however, is necessary rather than sufficient for setting one figure against another. Two labelled totals can be compared only when the task put to participants and the material counted are held the same; what may then differ is the way answers are recorded, and that difference is what the comparison reports.
The interface that stores only "no response" shows why the order matters. Lack of knowledge, refusal, indifference and abstention leave the same trace in its record. Nothing there distinguishes them, so treating "no response" as a refusal or as an abstention requires additional evidence. A denominator therefore cannot be built by subtracting a class of non-participation that the data never recorded.