My illustration entitled: “The Hand That Stops the Colossus” – A lone person raises an open palm before an immense mechanical titan. A visible control mechanism translates that gesture into powerful brakes locking its joints. Behind the person, a thriving city continues its daily life.
A person presses “decline”, but the collection continues. A worker objects to an optional monitoring device, then discovers that refusing it makes ordinary employment impossible. A customer withdraws permission for an additional service and loses access to unrelated records.
In each hypothetical example, refusal exists as an available expression. Its practical effect is another matter.
This distinction matters wherever institutions seek consent while retaining the power to disregard, circumvent or disproportionately punish its withdrawal. A society cannot assess freedom simply by counting the occasions on which people are invited to say yes or no.
I propose a right to a practical veto: within a person’s legitimate sphere of authority, refusal should prevent the relevant action, operate in time to matter and avoid unnecessary penalties that make the choice unusable.
This is a philosophical proposal for evaluating technological arrangements. It requires careful boundaries, alongside procedures that give refusal real effect.
A Veto Needs a Defined Object
The first question is what the person is entitled to refuse.
Someone ordinarily has a strong claim to reject an elective intervention on their body. A customer may refuse an optional use of personal information. A user may withdraw an explicitly limited delegation to a software service.
These cases differ from demanding control over another person’s independent decisions or claiming a right to disable shared infrastructure.
A practical veto must therefore identify its object: a procedure, disclosure, permission or action over which the person has a justified claim to authority.
Its scope should be intelligible before participation begins. Otherwise, an invitation to consent can conceal uncertainty about which decisions remain with the individual and which obligations arise from joining a shared arrangement.
Refusal Must Change What Happens
A veto has substance when the relevant process responds to it.
If someone declines optional information sharing, the system should prevent that sharing. If a person withdraws permission for a service to place orders, the service should lose the ability to initiate further orders within that delegation.
A message acknowledging the preference is insufficient if the underlying permissions remain active.
This requires coordination between institutional promises and technical operation. Staff procedures, software settings and third-party instructions should reflect the same boundary.
Evidence matters. A person should have reasonable means to verify that the refusal took effect, without needing to inspect an entire technical system.
Where compliance cannot be guaranteed immediately, the organisation should explain the limitation and provide a credible process for resolving it.
Timing Determines Whether Protection Is Real
Refusal must operate before the action becomes irreversible, wherever that is reasonably possible.
A medical objection heard after a procedure cannot protect the decision it concerned. Withdrawal of permission to publish a private document offers limited protection after widespread disclosure.
Systems should identify consequential decision points and provide opportunities to intervene before those points pass.
Sometimes an action is already under way. A payment may have been submitted, equipment may be moving or a treatment may require a controlled conclusion. Stopping instantly could be impossible or dangerous.
These circumstances call for clear rules about when authorisation becomes committed, what can still be interrupted and how further consequences can be limited. The promise of control should accurately describe the time within which control remains usable.
The Price of Saying No
Refusal does not always preserve every benefit. Someone declining a necessary diagnostic test may limit what a clinician can safely recommend. A person rejecting essential security checks may be unable to use a particular service.
The relevant distinction concerns consequences that follow from the refused action and penalties imposed to discourage refusal.
Consider an employee declining an optional wellness programme. The programme’s organiser might reasonably be unable to provide its personalised advice. Excluding the employee from unrelated workplace opportunities requires a separate justification.
Assessing that justification means asking whether the consequence is necessary, proportionate and connected to a legitimate purpose.
The practical veto does not promise consequence-free decisions. It requires scrutiny when an institution uses unrelated dependencies to make agreement effectively unavoidable.
Separate Permissions Where Purposes Differ
Bundled permissions can make refusal excessively broad.
A customer may want a communications service while objecting to an additional advertising use of their correspondence. A patient may accept treatment while declining participation in an unrelated research project.
Where purposes can reasonably be separated, people should be able to make separate decisions.
This requires attention to genuine operational dependencies. Some functions cannot be delivered without particular information or coordination. Providers should explain those dependencies rather than treating every requested permission as equally indispensable.
A practical veto becomes stronger when refusing one activity does not automatically terminate every surrounding relationship.
Separating permissions also clarifies responsibility. It becomes easier to determine which actions were authorised, which were declined and whether a later change exceeds the original agreement.
My illustration “The Hand That Stops the Colossus” work-in-progress. The art represents that refusal must have the power to stop an action while preserving access to ordinary life.
A Worker’s Refusal as a Test Case
Imagine a warehouse introducing wearable equipment that measures movement. Management describes it as a voluntary trial intended to improve workflow.
A worker declines because the equipment also records information unrelated to the stated purpose. Her supervisor accepts the decision verbally, but the scheduling system subsequently assigns fewer shifts to workers without recorded measurements.
The refusal has been acknowledged while its practical availability has deteriorated.
A serious assessment would examine the equipment’s purpose, the reasons for the scheduling rule and whether equivalent performance information could be obtained less intrusively.
Management may have legitimate operational needs. Those needs require explanation and appropriate limits. A programme cannot meaningfully remain voluntary if declining it predictably triggers disadvantages that have no necessary connection to its operation.
Make Refusal Accessible to Ordinary People
A veto can fail through complexity even when an institution intends to honour it.
Someone may need to navigate several offices, understand unfamiliar terminology or complete a procedure incompatible with their disability. A withdrawal option may be technically available but difficult to locate under pressure.
Effective refusal requires a process suited to the people expected to use it.
Instructions should identify the action being stopped, the consequences of stopping it and any further steps required. Assistance should be available without forcing people to surrender the very authority they are trying to exercise.
Institutional design should account for limited time, language differences and unequal technical knowledge. The burden should remain proportionate to the seriousness of the decision and the need to prevent fraudulent requests.
When Refusal Meets the Rights of Others
No individual can possess an unlimited veto over social life. Other people also have claims to safety, property, privacy and fair participation.
A worker’s refusal to perform a dangerous task differs from a demand to prevent colleagues from using safe equipment. An objection to personal information sharing differs from an attempt to suppress another person’s legitimate testimony.
Where claims conflict, the institution should identify whose interests are affected, how serious the likely harm is and which less restrictive arrangements are feasible.
Emergency intervention may sometimes be justified without prior agreement. Its scope should be limited by necessity, and its continuation should remain open to independent review.
Calling an action protective cannot settle the dispute. Reasons, evidence and accountable procedures must establish why overriding refusal is justified.
A Remedy When No Is Ignored
A practical veto requires somewhere to turn when the system proceeds anyway.
The remedy should match the failure. An unauthorised disclosure may require containment and notification. An improperly continued delegation may require revocation, investigation and correction of resulting transactions where feasible.
Compensation may be appropriate, but money cannot always restore a lost opportunity or undo exposure. Prevention and timely interruption therefore deserve priority.
Review should be sufficiently independent of the people whose conduct is disputed. It should also operate quickly enough to prevent a continuing violation from becoming an accomplished fact.
Organisations need records sufficient to establish what was authorised and when permission changed. Those records should be protected against misuse, with access limited to legitimate accountability needs.
Refusal, Exit and Continuing Participation
The ability to leave an arrangement is valuable. It cannot always substitute for authority within it.
Someone should sometimes be able to reject a new condition while retaining the service already agreed. Whether that expectation is justified depends on prior commitments, feasibility and the nature of the change.
Where separation is necessary, a practical veto may require a transition: retrieving records, finding another provider or safely withdrawing technical support.
These arrangements connect refusal with sovereignty over time. A right becomes fragile when its exercise destroys the resources needed to continue ordinary life.
Providers should anticipate foreseeable conflicts before users become deeply dependent. Planning makes it easier to preserve legitimate institutional functions while respecting the person’s decision to withhold or withdraw permission.
Freedom That Can Alter the Outcome
The practical veto asks a concrete question: what changes when this person says no?
The answer should identify the action stopped, the time of interruption, the consequences of refusal and the remedy available if the boundary is crossed.
Across bodies, code, markets and machines, these details determine whether personal authority survives contact with institutional power. Respect for consent must appear in what organisations and technologies actually do.
A sovereign future requires arrangements in which justified refusal can alter the outcome, with protections strong enough for ordinary people to use.