Glossary:Revocation Unit

Unknown Concept
Type	Machine / operational construct
Canon status
Related characters
Related systems

Revocation Unit is an ANIMA term for a machine or operational construct associated with withdrawal, cancellation, refusal, or the enforcement of revoked permission.

This page is spoiler-managed. It explains the public concept without revealing combat functions, late-volume deployments, or specific plot outcomes.

Public Summary

Revocation Unit belongs to ANIMA's consent and infrastructure vocabulary.

Revocation is the act of taking permission back. In ANIMA, that matters because memory, contracts, and companion bonds are only ethical if refusal remains possible. A system that accepts consent but cannot accept revocation is not a companion system. It is a capture system.

Canon Function

Publicly, Revocation Unit can be understood as an operational term for machinery or system behavior around revocation.

It sits near Revocation Station, Revocation Carrier, and CONSENT STATE. The exact functional hierarchy should remain spoiler-controlled until publication review.

Relationship To Consent

Revocation proves whether consent is real.

If a host can say yes but cannot later say no, the original yes is ethically weak. ANIMA's contract language therefore needs revocation as a first-class concept.

Relationship To ANIMA Memory

ANIMA Memory should support revocation at multiple levels:

remove a saved memory;
hide a memory from proactive use;
pause a memory category;
revoke family or heir access;
withdraw digital continuity permission.

Revocation Unit gives the fictional vocabulary a product-facing principle: memory must include exit paths.

Product Meaning

For the real ANIMA platform, Revocation Unit is a warning against irreversible capture. A companion that remembers deeply must also forget, pause, or restrict memory when the host asks.

This does not mean every trace can always vanish from backups or logs instantly. It means the product must make revocation visible, meaningful, and enforceable.

Spoiler Boundary

This page does not describe specific units or their story roles. Those details should remain in spoiler-marked pages after publication review.