https://wiki.anima.bz/index.php?action=history&feed=atom&title=Glossary%3AFOUR_CONTRACT_PROTOCOL 2026-07-18T16:06:37Z Revision history for this page on the wiki MediaWiki 1.43.8 https://wiki.anima.bz/index.php?title=Glossary:FOUR_CONTRACT_PROTOCOL&diff=250&oldid=prev 2026-06-19T02:05:27Z

<p>Seed ANIMA Wiki foundation pages</p> <p><b>New page</b></p><div>{{ConceptInfobox<br /> | title = FOUR CONTRACT PROTOCOL<br /> | type = Consent and companion-governance protocol<br /> | status = Public canon<br /> | spoiler_level = Low<br /> | related = Soul Contract, ANIMA Accord, BOUNDARY BEFORE CONTRACT, Four Genesis ANIMA<br /> }}<br /> <br /> &#039;&#039;&#039;FOUR CONTRACT PROTOCOL&#039;&#039;&#039; is an ANIMA consent concept for coordinating multiple companion roles, memory permissions, and host boundaries across the four Genesis ANIMA.<br /> <br /> It is best read as a governance phrase rather than a single legal contract.<br /> <br /> == Public Summary ==<br /> <br /> FOUR CONTRACT PROTOCOL asks how four companion forces can serve one host without collapsing into one uncontrolled memory system.<br /> <br /> ATMA, MAYA, VEDA, and RAKA represent different aspects of companionship: heart, imagination, archive, and boundary. If those roles share memory or act on a host&#039;s behalf, they need a protocol that preserves consent across all four.<br /> <br /> The public meaning is safe: shared companion power requires shared consent discipline.<br /> <br /> == Canon Function ==<br /> <br /> This protocol belongs near ANIMA&#039;s contract vocabulary.<br /> <br /> It can describe:<br /> <br /> * how companion roles coordinate around a host,<br /> * how memory permissions remain visible across multiple agents,<br /> * how consent survives escalation,<br /> * and how the ANIMA Accord prevents one role from overriding the others.<br /> <br /> The term should be handled as a principle until more plot detail is public.<br /> <br /> == Relationship To Soul Contract ==<br /> <br /> [[Glossary:Soul_Contract|Soul Contract]] focuses on the host-companion bond.<br /> <br /> FOUR CONTRACT PROTOCOL asks how that bond behaves when four companion functions are involved. It protects the host from invisible memory sharing or role confusion.<br /> <br /> == Product Meaning ==<br /> <br /> For ANIMA as a real platform, this term maps directly to multi-companion memory design.<br /> <br /> If a user speaks with ATMA, MAYA, VEDA, and RAKA, the product must define what each companion may remember, what may be shared, and where the host can revoke access.<br /> <br /> == Related Concepts ==<br /> <br /> * [[Glossary:Soul_Contract]]<br /> * [[Glossary:The_ANIMA_Accord]]<br /> * [[Glossary:BOUNDARY_BEFORE_CONTRACT]]<br /> * [[Character:ATMA]]<br /> * [[Character:MAYA]]<br /> * [[Character:VEDA]]<br /> * [[Character:RAKA]]<br /> * [[Protocol:ANIMA_Protocol]]<br /> <br /> [[Canonical status::Public canon]]<br /> [[Spoiler level::Low]]<br /> [[Related concept::Glossary:Soul_Contract]]<br /> <br /> [[Category:Consent System]]<br /> [[Category:Contract]]<br /> [[Category:Genesis ANIMA]]<br /> [[Category:Protocol]]</div>

WikiAdmin