TLWS · sovereignty · threshold
Revocation
Preserve the ability to withdraw prior permission, authorization, access, or delegation when conditions or willingness change.
provisional guidebook entry · version 0.1
Essence
Revocation protects Sovereignty across time.
Consent is not always permanent.
Conditions may change.
Information may change.
Relationships may change.
The participant may change.
Revocation allows a sovereign being to say:
I authorized this before. I no longer authorize it now.
Revocation may apply to:
- access
- permissions
- agreements
- delegated authority
- participation
- information sharing
- roles
- or relational expectations.
It does not automatically erase legitimate responsibilities already created by prior actions.
It changes what is authorized going forward.
Signal
The reading may involve:
- outdated Consent
- permissions that continue by inertia
- access that no longer fits current conditions
- delegated authority that should return
- or an agreement that requires renegotiation.
The card asks:
What permission is still operating because it was once given rather than because it remains chosen?
Coherent expression
Revocation is coherent when:
- the participant possesses legitimate authority to withdraw permission
- the change is communicated clearly enough
- existing obligations are distinguished from future authorization
- consequences are handled proportionately
- and the withdrawal does not require pretending the original Consent never existed.
Coherent Revocation allows the present to update the past without falsifying it.
Restoration
Identify the original authorization.
Ask:
- What was originally consented to?
- Was that permission time-limited or conditional?
- What has changed?
- Does the participant still choose it?
- What access should end?
- What delegated authority should return?
- What responsibilities survive the revocation?
- What practical action is required to make withdrawal real?
Restore Revocation by creating a functional path from:
previous yes
to:
present no.
Inquiry
What prior permission, access, agreement, or authority needs to be reconsidered under present conditions?
Diagnostic field
Four ways the principle can lose coherence.
Permanent Permission
Past authorization is treated as indefinitely binding even after:
- circumstances change
- willingness changes
- scope expands
- new information appears
- or the original agreement no longer matches the present field.
What access or permission is continuing only because no mechanism exists to update it?
Unstable Authorization
Permission is withdrawn so unpredictably or repeatedly that no reliable shared structure can form.
Examples include:
- revoking agreements whenever discomfort arises
- removing necessary authorization without communication
- using access as leverage
- or changing terms so frequently that participation becomes impossible to stabilize.
Revocation becomes volatility.
Is this withdrawal restoring sovereignty, or making all commitment structurally unreliable?
Revocation Without Actual Release
A system claims permission can be withdrawn while retaining practical control after withdrawal.
Examples include:
- access technically revoked but data retained and used
- delegation formally ended while authority continues informally
- relationship ended while expectations of access remain
- or permissions removed on paper but not in practice.
Revocation becomes symbolic rather than real.
What actually stops after permission is withdrawn?
Revoking What Cannot Be Retroactively Unmade
Revocation is applied as though it can erase:
- completed actions
- consequences already created
- obligations already incurred
- or history itself.
Sovereignty governs present and future authorization but cannot always undo prior reality.
What can be withdrawn now, and what consequence of the prior agreement still legitimately remains?
Reading lenses
How this card enters different questions.
Relationships
Ask whether access, expectations, permissions, or commitments still reflect present willingness rather than past agreement alone.
Decisions
Determine whether a previous commitment remains active or needs to be revised under new conditions.
Restoration
Return control over authorization to the person or field from which it originated.
System relationships
Connections across the TLWS field.
Cross-suit dependencies
- truth
- Revocation may become necessary when new information changes the meaning of earlier Consent.
- love
- Love must permit another's willingness to change without treating changed Consent as betrayal.
- wisdom
- Wisdom evaluates timing, consequence, and what obligations remain after authorization changes.
Cross-card relations
- ConsentRevocation
- Revocation updates prior Consent.
- RefusalRevocation
- Refusal prevents authorization; Revocation withdraws it after the fact.
- RevocationBoundary
- Boundary changes when authorization changes.
- RevocationExit
- Withdrawal of particular permissions may precede full departure.
- RevocationResponsibility
- Ending future authorization does not necessarily erase previously assumed obligations.
- RevocationCorrection
- New Truth may require changing an earlier agreement.
Visual motifs and artwork direction
- a luminous bridge retracting cleanly from one side,
- a key returning to its original holder,
- a previously active sigil dimming without destruction,
- an open gate closing by the choice of the one who opened it,
- threads disconnecting at deliberate junctions,
- delegated light returning from an outer node to its source.