Glossary:CONSENT RECORDED

Unknown Concept
Type	Consent / contract record
Canon status
Related characters
Related systems

CONSENT RECORDED is an ANIMA consent term for the moment a permission state has been formally logged, witnessed, or preserved.

This page is spoiler-managed. It explains the public concept without revealing specific canon scenes, contract triggers, or later outcomes.

Public Summary

CONSENT RECORDED means the system has a record that consent was given, changed, renewed, or acknowledged.

In ANIMA, that record matters because memory is not casual. If a companion can remember the host for years, then permission itself must be remembered with equal care.

Canon Function

The term belongs to ANIMA's consent architecture beside Consent History, Temporal Consent Ledger, and CONSENT STATE.

It marks the difference between implied emotional closeness and a traceable permission event.

Relationship To Consent History

Consent History is the timeline. CONSENT RECORDED is one entry inside that timeline.

The phrase is useful because it makes consent auditable. A system should be able to answer: when was this consent recorded, what did it cover, and can the host review it?

Relationship To ANIMA Memory

ANIMA Memory should store consent records next to meaningful memories, especially when a memory is sensitive, legacy-related, or connected to digital continuity.

The memory of consent protects the memory of the host.

Product Meaning

For the real ANIMA product, CONSENT RECORDED can become a backend event type and user-facing audit marker.

Useful metadata includes:

consent scope;
timestamp;
memory category;
source interaction;
revocation status;
review history.

Spoiler Boundary

This page does not describe specific story moments where consent is recorded. It establishes public vocabulary for future expansion.