My illustration entitled: “The Human Within the Colossus” – An immense biomechanical figure stands in a mountain valley, its body woven from living tissue, articulated metal and neural light. Through a transparent chest, a human pilot is visible, calmly directing its movements. Tiny buildings establish the breathtaking scale.
Imagine a person using an advanced mobility device supported by several organisations. One supplies the hardware, another maintains its software, a clinic adjusts its operation, a remote service stores necessary settings and a funding body pays for essential maintenance.
Each arrangement appears reasonable when examined separately. Then an account dispute blocks access to settings, a software change creates incompatibility and the clinic cannot obtain authorization for a replacement component.
No single organisation intended the resulting loss of mobility. Each explains that the missing solution belongs elsewhere.
The person remains inside the system, waiting.
This hypothetical case presents a stress test for Human Sovereignty Transhumanism. Protecting the individual requires examining the complete arrangement through which an enhancement works, including the gaps between institutions that otherwise appear responsible.
A Person Experiences the Whole Arrangement
A manufacturer may promise reliable equipment without controlling clinical appointments. A clinician may provide appropriate advice without controlling software access. A funding body may meet its stated conditions while leaving an urgent expense uncovered.
Each account can be accurate. Together, they may still describe a failure of protection.
The user experiences the combined result: whether communication, movement, care or independent choice remains possible.
Human sovereignty cannot therefore be assessed solely by asking whether each provider has acceptable terms. We must ask whether those terms work together when the person needs them most.
Separate promises of protection do not establish that the complete system protects the person.
Dependence Can Emerge Between Providers
A system can become difficult to leave even where no participant deliberately creates captivity.
Hardware may require particular software. Software may require an active account. The account may depend on identity verification, continuing payment and information supplied by another institution.
An alternative provider might exist, yet lack access to necessary records or compatible components. Each individual dependency may seem manageable until several interact.
The result is a form of institutional dependence that belongs to the arrangement rather than any single organisation.
This matters philosophically. A framework concerned only with obvious coercion could overlook a person whose choices are restricted by coordination failures, incompatible rules or procedures that nobody has the authority to resolve.
Begin With the Person’s Essential Functions
A practical assessment should begin by identifying what the individual needs the arrangement to sustain.
That includes the enhancement’s intended function and the conditions required to exercise personal authority: communication, understandable information, consent, access to support and opportunities to challenge consequential decisions.
The assessment should then identify the technical, clinical, financial and administrative dependencies supporting those functions.
Not every remote possibility deserves equal attention. Priority should follow the seriousness of interruption, plausible failure routes and difficulty of recovery.
The person’s own circumstances matter. An interruption manageable for one user may severely restrict another. Available assistance, accessibility needs and realistic alternatives should inform the assessment rather than be assumed.
Find the Gaps Between Responsibilities
For every consequential dependency, ask who can act, who must act and who provides resources when something fails.
These questions are related but distinct. An institution may recognise a problem without possessing the authority or funding needed to resolve it.
Assessment should examine transfers between providers: requests for records, referrals, account recovery, component approval and changes of service.
A gap exists where necessary action falls outside everyone’s accepted responsibility, or where one party’s duty depends on cooperation that another has not agreed to provide.
Identifying that gap should produce a concrete response: a revised agreement, additional capacity, a different design or a reason to postpone deployment. Listing it without assigning action offers little protection.
Test Interacting Failures
Routine checks often assume that other parts of the arrangement continue functioning normally. A stronger test deliberately questions that assumption.
What happens when a communication interruption coincides with an account problem? Can someone obtain maintenance while funding is disputed? Does an alternative provider remain usable when necessary records are temporarily inaccessible?
These scenarios should be plausible and proportionate to the stakes.
The objective is to discover whether protections survive combinations that expose hidden assumptions. A backup requiring the same unavailable account may offer no independent route.
Testing should follow the user’s situation through the sequence, including how long essential functioning is interrupted and whether promised assistance can actually be reached.
Test Whether Rights Remain Exercisable
A right to refuse an optional change may disappear in practice if essential maintenance becomes incompatible with the previous configuration.
A complaint channel may fail if access requires the communication device currently awaiting repair. A transfer right may be unusable if exporting records depends on the account being challenged.
These examples show why rights must be assessed through their practical conditions of exercise.
The relevant test is whether the person can still understand options, communicate a decision, obtain essential support and challenge a restriction under the conditions being examined.
Where the answer is no, the system needs an accessible alternative that does not reproduce the same dependency. Formal permission alone cannot supply that route.
My illustration “The Human Within the Colossus” work-in-progress. The art showcases of extraordinary technological power remain being guided by a human being.
Someone Must Coordinate the Response
Complexity creates a need for identified coordination, especially where interruption could seriously restrict everyday functioning.
A designated institution or agreed arrangement should organise communication between providers, track unresolved actions and help the person obtain a timely response.
The coordinator needs authority, resources and escalation procedures. Merely providing a telephone number does not establish an effective remedy.
Coordination should not erase the duties of other participants. Manufacturers, clinicians, service providers and funders remain responsible for matters within their roles.
Nor should it create an unchecked gatekeeper. The person should retain access to independent advice and review, with clear limits on the coordinator’s use of information and decision-making powers.
Responsibility Without a Single Controller
The strongest objection is that nobody can reasonably guarantee the performance of an entire system containing independent organisations.
This is correct. Responsibility should reflect knowledge, authority and a reasonable ability to prevent or address harm.
Yet the absence of total control does not eliminate duties to identify foreseeable dependencies, share necessary information appropriately and cooperate over agreed responses.
Participants should distinguish their specific obligations, their responsibilities at interfaces and circumstances requiring collective action. Uncertainty about the final allocation of blame should not automatically delay urgent protective assistance.
The aim is an arrangement in which each necessary action has an accountable route, rather than a fiction that one party controls everything.
Recovery Must Protect the Person
A technical repair is incomplete if the person remains unable to resume the activities the enhancement supported.
Recovery planning should address accessible communication, temporary assistance, appropriate professional assessment and restoration of necessary settings or records.
Where a transition is required, it should account for the individual’s circumstances and avoid assuming that replacement means an immediate return to previous functioning.
Emergency information sharing should remain limited to justified needs. A crisis does not authorize unrelated commercial use or permanent expansion of surveillance.
Costs should be anticipated where reasonably foreseeable. The user should not become the default financier of a coordination failure simply because institutions cannot quickly settle their respective responsibilities.
Return to the mobility device in the opening example. A useful exercise would trace the account dispute through every necessary response. Can the clinic retrieve essential settings through an appropriately protected alternative? Who authorizes temporary assistance? Can the software provider communicate directly with a qualified technician? What happens if the funding body remains unavailable?
The answers should identify actions and responsible parties, then be checked against realistic constraints. A proposed workaround might require unavailable equipment or expose information beyond what the repair needs. Another might shift an unreasonable burden onto a caregiver.
The exercise succeeds when it reveals these weaknesses early enough to change the arrangement. It does not succeed merely because each provider can explain why its own procedure was followed. The standard is whether the person receives a workable, timely and accountable route through the combined failure. That standard should guide both preparation and later investigation of what went wrong and what must change next.
Keep the Assessment Alive
A complete support arrangement changes over time. Providers leave, software evolves, funding conditions shift and the person’s circumstances develop.
Material changes should trigger review of affected dependencies and protections. New providers should understand which responsibilities they assume and which gaps their participation might create.
Users need understandable explanations of consequential changes, with appropriate participation in decisions affecting their support.
Records of failures and near failures should inform improvements without exposing unnecessary personal information.
A successful assessment is evidence about a particular arrangement under specified conditions. It should never become a permanent assurance that later combinations remain acceptable.
The Person Is the Measure
Human Sovereignty Transhumanism must remain answerable to the person whose life depends on the system.
That means looking beyond individually reasonable products and contracts to the consequences of their interaction. It means identifying responsibility gaps before users fall into them, then testing whether essential protections survive plausible combinations of failure.
An enhancement is supported by a network of responsibilities. Human sovereignty requires that the person remain protected where those responsibilities meet, separate and sometimes fail.