Directory · A
New here? Start with the premise →
Autonomy
3 min read · 676 words
Autonomy is operating from your own authority — running the system on instructions that originate in the chair rather than instructions installed by someone else.
It is easy to confuse with independence, and the two are different. The Independence entry covers not needing others — standing without external support. Autonomy is narrower and more internal: self-governance. An operator can be deeply connected to others, reliant on them, embedded in obligation, and still autonomous — provided the governing decisions are being made from their own console, against their own values, rather than dictated by external authority the operator never actually endorsed. Autonomy is not about being alone. It’s about who’s holding the controls.
The Authority entry covers external command structures. Autonomy is the operator’s claim to be the authority over their own operation.
HOW IT GETS SURRENDERED
The controls get handed off, usually without a decision to hand them off.
Some of it is installed early. The system takes in rules, expectations, and directives from outside — family, culture, the various authorities the developing operator had no power to question — and stores them as defaults. The Conditioning entry covers the install. Years later the operator runs these directives as if they were their own, never having checked whether the one in the chair actually endorses them. The instructions feel like the self. They were authored elsewhere.
Some of it is surrendered ongoing, to avoid the cost of self-governance. Governing your own operation means deciding, and deciding means owning the outcome, and owning the outcome is expensive. So the system often prefers to be told — to outsource the controls to a person, an institution, a set of rules — because then the responsibility sits elsewhere. The Dependence entry covers the reliance; the Rebellion entry covers the counterfeit escape from it, where the operator merely inverts the external command instead of authoring their own, which leaves the external authority still holding the controls, just in reverse.
THE HOW — TAKING THE CONTROLS BACK
Autonomy is reclaimed by auditing the instructions the system runs on and re-deciding them from the chair.
To audit, take a directive the operator lives by — a rule about what they must do, who they must be, what is and isn’t allowed — and ask where it came from and whether they ever actually endorsed it. Is this mine, or was it installed? Many governing rules turn out to be inherited, never reviewed, running on the authority of whoever loaded them decades ago. The Beliefs entry covers examining the stored content. Autonomy is the act of deciding, now, from current values, whether to keep each directive or revise it. Endorsed, it becomes genuinely the operator’s. Rejected, it loses its command.
To exercise it, make decisions and own them. Autonomy is built the way agency is — through instances. The Agency entry covers the capacity to act; autonomy is acting from one’s own authority specifically. Each decision the operator makes deliberately, against their own assessment, and stands behind regardless of outcome, strengthens the claim that the chair is where the governing happens. The Volition entry covers the will that drives it.
To tell autonomy from mere defiance: check what happens when the external authority isn’t watching. Genuine autonomy operates the same either way — the governance is internal. Defiance needs the authority present to push against; remove it and the operator has no direction of their own. If the operation collapses without something to resist, the controls were never actually reclaimed.
THE OPERATOR’S POSITION
Autonomy is not the rejection of all external input. The autonomous operator still takes instruction, still defers where deferring is wise, still operates inside obligations and relationships. The Freedom entry covers the broader condition. The difference is that the deferring is itself a decision made from the chair — endorsed, not merely obeyed.
The instructions the system runs on came from somewhere.
Autonomy is the operator reviewing them, one by one, and deciding which ones they’re actually willing to sign.