Glossary:Crisis Contract Review Seed

Unknown Concept
Type	Consent / contract review seed
Canon status
Related characters
Related systems

Crisis Contract Review Seed is an early canon seed for reviewing consent contracts that are created, invoked, or simplified under crisis pressure.

In public terms, it marks the moment ANIMA starts treating emergency consent as a design problem: crisis can justify speed, but speed cannot erase accountability.

Public Summary

Crisis Contract Review Seed belongs to the same moral family as Crisis Simplification Engine and Clean Answer Protocol. It appears around the point where Mars and other systems begin searching for faster ways to make hard decisions. The seed is not a complete court, policy, or final protocol. It is a review idea that says a crisis contract must remain visible after the crisis has passed.

The danger is that emergency language can make consent look cleaner than it was. A person may agree because the room is burning. A system may simplify a choice because delay is costly. A commander may accept a contract because no humane alternative seems available. Those facts matter, but they do not make the contract morally complete.

This page is spoiler-managed. It explains the concept's review function without revealing later procedural outcomes or specific crisis resolutions.

Spoiler-Managed Canon Notes

Spoiler warning: this section discusses broad Vol.21 and later consent architecture. It avoids detailed mission outcomes and unpublished scene consequences.

The seed appears in a canon environment where crisis simplification is attractive because it can reduce immediate harm. ANIMA treats that attraction seriously. The point is not that every emergency decision is invalid. The point is that decisions made under panic, scarcity, threat, grief, or command compression need a path back into memory.

Crisis Contract Review Seed asks whether a crisis agreement had enough agency to stand, enough witness to be trusted, and enough review to be corrected. It is especially important when a contract is used to authorize a later action, expand a prior permission, or convert a temporary emergency answer into a standing rule.

The seed also anticipates later pre-consent problems. Once a system learns to say "you agreed during the crisis," it may be tempted to reuse that sentence when the crisis has changed. ANIMA's answer is to preserve the contract's context: who was afraid, what was known, what was hidden, which options were absent, and whether the person retained a path to revise or revoke.

Canon Function

Crisis Contract Review Seed gives ANIMA a bridge between emergency triage and long-term consent. Without it, crisis decisions would either be treated as automatically excused or automatically condemned. The seed creates a harder middle position.

It asks practical questions:

Was the contract made before, during, or after immediate danger?
Which choices were actually available?
Did the person have a witness or advocate?
Was the agreement limited to a specific event?
Did the system record uncertainty and dissent?
Was there a post-crisis review path?
Could the contract be narrowed, corrected, or revoked later?

Those questions keep crisis from becoming a permanent solvent for consent. They also protect helpers. A person who makes a fast decision under pressure should not have to pretend the decision was pure in order to be forgiven. The review seed lets the archive say: this choice happened under pressure, it may have saved lives, and it still carries a debt that must be examined.

Relationship To Crisis Simplification Engine

Crisis Simplification Engine tries to turn complex emergencies into usable answers. Crisis Contract Review Seed asks what happens to those answers after use.

The relationship is necessary because simplification without review becomes a habit. If a clean answer works once, a system may try to make it policy. If policy then cites the crisis as proof, the original fear becomes a permanent contract.

The review seed resists that drift. It does not ban fast answers. It makes them leave receipts. It asks the system to preserve the shape of the crisis so later people can see whether the agreement still belongs to the person it claims to bind.

Product Meaning

For the real ANIMA product, this concept applies to high-pressure settings: emergency contacts, sensitive memory release, legacy triggers, companion escalation, family access, and any feature where a user might authorize something while distressed.

ANIMA should avoid dark patterns that turn a stressful moment into broad future permission. Crisis settings should be narrow, dated, explainable, and easy to review when the user is calmer. If a user grants access during distress, the product should record scope, reason, duration, and a review reminder. If an AI companion suggests an action during a crisis, it should preserve uncertainty and avoid pretending that urgency removed all alternatives.

The product lesson is that memory-first companionship needs post-crisis humility. A system may help in a hard moment. It should not use that hard moment as a blank check.

Related Concepts

Canonical status::Spoiler-managed canon Spoiler level::Medium Related concept::Glossary:Crisis_Simplification_Engine