Glossary:BOUNDARY BEFORE CONTRACT

Unknown Concept
Type	Consent principle
Canon status
Related characters
Related systems

BOUNDARY BEFORE CONTRACT is an ANIMA consent principle: no bond, memory agreement, or continuity claim should begin before the host's boundaries are recognized.

It is one of the clearest public phrases for ANIMA's consent-first identity.

Public Summary

BOUNDARY BEFORE CONTRACT means a relationship cannot become legitimate by skipping the line that makes consent meaningful.

In ANIMA, contract language is powerful because memory, companionship, and future continuity may all depend on it. But a contract without boundaries becomes pressure. A bond without refusal becomes ownership.

The principle is simple: define the boundary first, then decide whether a contract can exist.

Canon Function

This phrase belongs near ANIMA's consent and contract vocabulary.

It can apply to:

host-companion memory sharing,
Soul Contract formation,
access to private archives,
legacy or digital-continuity permissions,
and emergency decisions where urgency tries to bypass agency.

The term is safe for public wiki use because it explains an ethical rule rather than a plot outcome.

Relationship To Soul Contract

Soul Contract is meaningful only if the host can refuse, revise, and understand the terms.

BOUNDARY BEFORE CONTRACT protects that meaning. It prevents the story and the product from treating intimacy as automatic consent.

Product Meaning

For the real ANIMA product, this principle should become a design rule.

Before ANIMA stores sensitive memory, shares context between companions, exposes family access, or prepares continuity features, the user should see the boundary options clearly. The system should not ask for a grand emotional contract before explaining what is being protected.

Related Concepts

Canonical status::Public canon Spoiler level::Low Related concept::Glossary:BOUNDARY_PROTOCOL