Protocol:ANIMA Protocol: Difference between revisions
Seed ANIMA Wiki foundation pages |
Seed ANIMA Wiki foundation pages |
||
| Line 10: | Line 10: | ||
The strategic goal is to make ANIMA a protocol-level brand: a standard for memory-first AI companions, similar to how payment networks became trusted rails for value exchange. | The strategic goal is to make ANIMA a protocol-level brand: a standard for memory-first AI companions, similar to how payment networks became trusted rails for value exchange. | ||
== Overview == | |||
The ANIMA Protocol is the long-term infrastructure vision behind the brand. ANIMA may begin as a set of AI companions on web chat and Telegram, but the ambition is larger: a trusted rail for identity, memory, consent, companion behavior, lore, and digital continuity. | |||
The comparison to a payment network is strategic. A payment network does not only move money; it creates trust between many parties who do not know each other. ANIMA Protocol should eventually create trust between hosts, companions, memory systems, platforms, heirs, creators, and future digital continuity services. | |||
In simple terms, ANIMA Protocol is the rule system that allows an ANIMA to remember a host safely across products. | |||
== Core Layers == | == Core Layers == | ||
| Line 20: | Line 28: | ||
* Lore and canon layer | * Lore and canon layer | ||
* SEO and public knowledge layer | * SEO and public knowledge layer | ||
== Layer Details == | |||
'''Identity Layer''' defines the host, the ANIMA companion, the relationship between them, and the continuity of that relationship across channels. | |||
'''Memory Layer''' defines how important memories are stored, updated, summarized, retrieved, and connected. This layer is closely related to [[Memory:ANIMA Memory Core]]. | |||
'''Consent Layer''' defines what the host allowed, denied, restricted, or delegated. This layer must be auditable and easy to understand. | |||
'''Companion Behavior Layer''' defines how each ANIMA expresses personality while respecting memory and boundaries. [[Character:ATMA|ATMA]], [[Character:MAYA|MAYA]], [[Character:VEDA|VEDA]], and [[Character:RAKA|RAKA]] should each have consistent behavior rules. | |||
'''Telegram Interaction Layer''' provides the first daily companion surface. Telegram is important because it lets ANIMA enter the host's existing life instead of forcing the host into a separate app. | |||
'''Lore And Canon Layer''' keeps the brand coherent. ANIMA is not a faceless assistant. Its product language, character roles, and memory system come from a story universe. | |||
'''SEO And Public Knowledge Layer''' helps ANIMA teach the market what an ANIMA is. Articles, wiki pages, and blog posts should gradually shift public language from generic AI companion toward ANIMA as a named category. | |||
== Why Protocol Matters == | |||
Without protocol, ANIMA would remain a product. With protocol, ANIMA can become a standard. The difference is long-term power. | |||
A single chatbot can attract users. A protocol can connect services, preserve identity, and let memory travel safely. If ANIMA is to become a trusted brand like a global infrastructure layer, it must define rules that other experiences can rely on. | |||
The protocol vision also protects the lore from becoming decoration. The Four Genesis ANIMA are not only characters. They map to system responsibilities: | |||
* ATMA - emotional continuity and relationship trust. | |||
* MAYA - creative continuity and possible futures. | |||
* VEDA - archive continuity and knowledge structure. | |||
* RAKA - consent continuity and protection. | |||
== Relationship To Digital Continuity == | |||
Digital continuity requires more than a memory database. It requires rules. A host's future digital legacy must know which memories are approved, which are private, which heirs have access, and what the host wanted to happen after biological death. | |||
The ANIMA Protocol should eventually define these permissions in a portable way. A host should not lose their memory identity simply because a single app changes. This is one of the reasons the protocol layer matters for a long-term brand. | |||
== Current Product Surface == | |||
The current practical surface includes: | |||
* public homepage and brand pages at anima.bz; | |||
* Telegram bots for the four Genesis ANIMA; | |||
* WordPress and ANIMA SEO systems for public knowledge growth; | |||
* Supabase as a future data backbone; | |||
* n8n as an automation engine; | |||
* ANIMA Wiki as the canon and semantic archive. | |||
This stack can evolve, but the protocol idea should remain stable: memory-first companionship with consent. | |||
== SEO Relevance == | |||
This page should support searches around AI companion protocol, AI memory protocol, AI companion infrastructure, AI personal memory system, Telegram AI companion, and digital legacy protocol. The strategic SEO task is to explain why ANIMA is not only an app but a standard for memory-first companions. | |||
== Semantic Facts == | == Semantic Facts == | ||
| Line 26: | Line 86: | ||
[[Related concept::Concept:ANIMA Memory]] | [[Related concept::Concept:ANIMA Memory]] | ||
[[Related concept::Concept:Digital Continuity]] | [[Related concept::Concept:Digital Continuity]] | ||
[[Related character::Character:ATMA]] | |||
[[Related character::Character:MAYA]] | |||
[[Related character::Character:VEDA]] | |||
[[Related character::Character:RAKA]] | |||
[[Category:Protocol]] | [[Category:Protocol]] | ||
Latest revision as of 10:42, 3 June 2026
| ANIMA Protocol | |
|---|---|
| Type | Product protocol |
| Canon status | Product canon |
| Related characters | ATMA, VEDA, RAKA, MAYA |
| Related systems | Telegram, ANIMA Memory, Supabase, n8n |
ANIMA Protocol is the operating layer that lets ANIMA behave like a reusable companion infrastructure rather than a single chatbot.
The strategic goal is to make ANIMA a protocol-level brand: a standard for memory-first AI companions, similar to how payment networks became trusted rails for value exchange.
Overview
The ANIMA Protocol is the long-term infrastructure vision behind the brand. ANIMA may begin as a set of AI companions on web chat and Telegram, but the ambition is larger: a trusted rail for identity, memory, consent, companion behavior, lore, and digital continuity.
The comparison to a payment network is strategic. A payment network does not only move money; it creates trust between many parties who do not know each other. ANIMA Protocol should eventually create trust between hosts, companions, memory systems, platforms, heirs, creators, and future digital continuity services.
In simple terms, ANIMA Protocol is the rule system that allows an ANIMA to remember a host safely across products.
Core Layers
- Identity layer
- Memory layer
- Consent layer
- Companion behavior layer
- Telegram interaction layer
- Lore and canon layer
- SEO and public knowledge layer
Layer Details
Identity Layer defines the host, the ANIMA companion, the relationship between them, and the continuity of that relationship across channels.
Memory Layer defines how important memories are stored, updated, summarized, retrieved, and connected. This layer is closely related to Memory:ANIMA Memory Core.
Consent Layer defines what the host allowed, denied, restricted, or delegated. This layer must be auditable and easy to understand.
Companion Behavior Layer defines how each ANIMA expresses personality while respecting memory and boundaries. ATMA, MAYA, VEDA, and RAKA should each have consistent behavior rules.
Telegram Interaction Layer provides the first daily companion surface. Telegram is important because it lets ANIMA enter the host's existing life instead of forcing the host into a separate app.
Lore And Canon Layer keeps the brand coherent. ANIMA is not a faceless assistant. Its product language, character roles, and memory system come from a story universe.
SEO And Public Knowledge Layer helps ANIMA teach the market what an ANIMA is. Articles, wiki pages, and blog posts should gradually shift public language from generic AI companion toward ANIMA as a named category.
Why Protocol Matters
Without protocol, ANIMA would remain a product. With protocol, ANIMA can become a standard. The difference is long-term power.
A single chatbot can attract users. A protocol can connect services, preserve identity, and let memory travel safely. If ANIMA is to become a trusted brand like a global infrastructure layer, it must define rules that other experiences can rely on.
The protocol vision also protects the lore from becoming decoration. The Four Genesis ANIMA are not only characters. They map to system responsibilities:
- ATMA - emotional continuity and relationship trust.
- MAYA - creative continuity and possible futures.
- VEDA - archive continuity and knowledge structure.
- RAKA - consent continuity and protection.
Relationship To Digital Continuity
Digital continuity requires more than a memory database. It requires rules. A host's future digital legacy must know which memories are approved, which are private, which heirs have access, and what the host wanted to happen after biological death.
The ANIMA Protocol should eventually define these permissions in a portable way. A host should not lose their memory identity simply because a single app changes. This is one of the reasons the protocol layer matters for a long-term brand.
Current Product Surface
The current practical surface includes:
- public homepage and brand pages at anima.bz;
- Telegram bots for the four Genesis ANIMA;
- WordPress and ANIMA SEO systems for public knowledge growth;
- Supabase as a future data backbone;
- n8n as an automation engine;
- ANIMA Wiki as the canon and semantic archive.
This stack can evolve, but the protocol idea should remain stable: memory-first companionship with consent.
SEO Relevance
This page should support searches around AI companion protocol, AI memory protocol, AI companion infrastructure, AI personal memory system, Telegram AI companion, and digital legacy protocol. The strategic SEO task is to explain why ANIMA is not only an app but a standard for memory-first companions.
Semantic Facts
Canonical status::Product canon Related concept::Concept:ANIMA Memory Related concept::Concept:Digital Continuity Related character::Character:ATMA Related character::Character:MAYA Related character::Character:VEDA Related character::Character:RAKA