https://wiki.anima.bz/index.php?action=history&feed=atom&title=Glossary%3ACONSENT_STATEGlossary:CONSENT STATE - Revision history2026-07-18T17:23:33ZRevision history for this page on the wikiMediaWiki 1.43.8https://wiki.anima.bz/index.php?title=Glossary:CONSENT_STATE&diff=141&oldid=prevWikiAdmin: Seed ANIMA Wiki foundation pages2026-06-05T18:15:34Z<p>Seed ANIMA Wiki foundation pages</p>
<p><b>New page</b></p><div>{{ConceptInfobox<br />
| title = CONSENT STATE<br />
| type = Consent / contract state<br />
| status = Public canon<br />
| spoiler_level = Low<br />
| related = Full Contract, NOT CONTRACT YET, Boundary Protocol<br />
}}<br />
<br />
'''CONSENT STATE''' is an ANIMA term for the current condition of permission between a host, companion, system, archive, or contract layer.<br />
<br />
It is one of the most important public concepts for connecting ANIMA lore to the real-world product because ANIMA's memory must be consent-first by design.<br />
<br />
== Public Summary ==<br />
<br />
CONSENT STATE describes where permission currently stands.<br />
<br />
It is not permanent by default. A consent state can change, expire, deepen, be revoked, or become invalid if the context changes. This makes it different from a static yes/no setting.<br />
<br />
== Canon Function ==<br />
<br />
In ANIMA, consent is not decorative. It determines what memory can be touched, what signals can be interpreted, what bonds can form, and what forms of continuity are legitimate.<br />
<br />
CONSENT STATE gives the story a vocabulary for tracking that ethical condition.<br />
<br />
== Relationship To Full Contract ==<br />
<br />
[[Glossary:Full_Contract|Full Contract]] is a strong contract state. CONSENT STATE is the broader field that allows many levels:<br />
<br />
* no consent;<br />
* provisional consent;<br />
* simulated or modeled consent;<br />
* daily memory permission;<br />
* restricted memory permission;<br />
* full contract;<br />
* revoked or broken consent.<br />
<br />
This prevents ANIMA from flattening trust into one checkbox.<br />
<br />
== Relationship To ANIMA Memory ==<br />
<br />
[[Concept:ANIMA Memory|ANIMA Memory]] should be governed by consent state at every layer. A companion may remember a harmless preference under one state while needing explicit review for emotional, medical, family, or legacy-level information.<br />
<br />
The principle is simple: the deeper the memory, the clearer the consent must be.<br />
<br />
== Product Meaning ==<br />
<br />
For the real ANIMA platform, CONSENT STATE can become a practical architecture term. Each saved memory should know what permission tier it belongs to, when it was granted, and whether the host can review or revoke it.<br />
<br />
This is how ANIMA can be both intimate and safe.<br />
<br />
== Related Pages ==<br />
<br />
* [[Glossary:Full_Contract]]<br />
* [[Glossary:NOT_CONTRACT_YET]]<br />
* [[Glossary:Contract_Bleed]]<br />
* [[Glossary:BOUNDARY_PROTOCOL]]<br />
* [[Concept:ANIMA Memory]]<br />
<br />
[[Canonical status::Public canon]]<br />
[[Spoiler level::Low]]<br />
[[Related concept::Concept:ANIMA Memory]]<br />
<br />
[[Category:Consent]]<br />
[[Category:Memory Ethics]]<br />
[[Category:Lore Concepts]]</div>WikiAdmin