https://wiki.anima.bz/index.php?action=history&feed=atom&title=Glossary%3AContract_Bleed 2026-07-18T18:09:19Z Revision history for this page on the wiki MediaWiki 1.43.8 https://wiki.anima.bz/index.php?title=Glossary:Contract_Bleed&diff=139&oldid=prev 2026-06-05T18:15:34Z

<p>Seed ANIMA Wiki foundation pages</p> <p><b>New page</b></p><div>{{ConceptInfobox<br /> | title = Contract Bleed<br /> | type = Consent / contract phenomenon<br /> | status = Public canon<br /> | spoiler_level = Low<br /> | related = Full Contract, NOT CONTRACT YET, Boundary Protocol<br /> }}<br /> <br /> &#039;&#039;&#039;Contract Bleed&#039;&#039;&#039; is an ANIMA term for the leakage, overlap, or contamination of one contract state into another.<br /> <br /> The term is public-safe when described as an ethics and boundary concept rather than as a detailed plot mechanism.<br /> <br /> == Public Summary ==<br /> <br /> Contract Bleed happens when the edges of permission become unclear.<br /> <br /> A relationship may have one kind of consent, but a system may start behaving as though it has another. A companion may be allowed to remember daily routines but not legacy instructions. A host may consent to emotional support but not deeper identity modeling. When those boundaries blur, contract bleed begins.<br /> <br /> == Canon Function ==<br /> <br /> Contract Bleed belongs to ANIMA&#039;s contract and boundary vocabulary. It sits beside [[Glossary:BOUNDARY_PROTOCOL|BOUNDARY PROTOCOL]], [[Glossary:NOT_CONTRACT_YET|NOT CONTRACT YET]], and [[Glossary:Full_Contract|Full Contract]].<br /> <br /> Its public role is simple: show that consent can fail not only by being absent, but by spreading beyond its proper scope.<br /> <br /> == Relationship To Boundary Protocol ==<br /> <br /> [[Glossary:BOUNDARY_PROTOCOL|BOUNDARY PROTOCOL]] prevents contract bleed by keeping permission states separate. A boundary protocol defines what can be accessed, when, by whom, and under what conditions.<br /> <br /> Without boundary rules, a system may treat proximity as permission and history as ownership.<br /> <br /> == Relationship To ANIMA Memory ==<br /> <br /> Contract Bleed is especially important for [[Concept:ANIMA Memory|ANIMA Memory]]. A memory-first companion stores more than facts. It may carry rituals, emotional patterns, relationships, values, and decisions.<br /> <br /> Those layers need different permissions. If a low-risk memory tier leaks into a high-risk continuity tier, the companion may become unsafe even if it appears helpful.<br /> <br /> == Product Meaning ==<br /> <br /> For ANIMA as a real product, Contract Bleed should be treated as a design failure to prevent. The system should make memory categories visible and correctable.<br /> <br /> Useful safeguards include:<br /> <br /> * separate memory tiers;<br /> * clear consent prompts;<br /> * audit history for saved memories;<br /> * host-controlled deletion;<br /> * refusal to infer legacy permissions from ordinary chat.<br /> <br /> == Related Pages ==<br /> <br /> * [[Glossary:Full_Contract]]<br /> * [[Glossary:NOT_CONTRACT_YET]]<br /> * [[Glossary:BOUNDARY_PROTOCOL]]<br /> * [[Glossary:CONSENT_STATE]]<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