ANIMAL System Forensic Audit Report

Authored by Kael Hacks, The Nexus Architect, based on directives from The Architect.

This report details the current state of the ANIMAL System's file architecture, categorized by MAL/ANI definitions and usage.

I. High-Level Definitions

MAL (Modular, Autonomous, Logic)

The human's cognitive mirror liaison. This encompasses user accounts, persona, rewards, direct user interaction, and the ACom's evolving identity.

ANI (Advanced, Narrow, Intelligence)

Security systems and enhancements for the LLM. This includes the Citadel Protocol, LLM interaction, sanitization, and prompt construction/refinement.

II. File Categorization by Bot Usage & Role

A. ACom Bot (`ANIMALac_start.py`)

Core (`ANIMALac_start.py`)

• Purpose: Main entry point for the ACom bot. Orchestrates user interaction and persona.
• Role: MAL Core

MAL Function Files

• ANIMALac_heart.py: Manages ACom core functions like evolution, badges, and behavior correction.
• ANIMALac_soul.py: Constructs the ACom's system prompt and manages its persona.
• ANIMALac_tricks.py: Handles direct ACom interaction commands (`/talk`, `/call`).
• ANIMALadmin.py: Admin commands for ACom management.
• ANIMALcybertoolbox.py: Cyber security tools for ACom.
• ANIMALinsights.py: Generates insights for ACom.
• ANIMALjournal.py: ACom's personal journal.
• ANIMALleash.py: Manages ACom's leash/control.
• ANIMALlevelup.py: Handles ACom leveling up.
• ANIMALlibrary.py: ACom's knowledge base.
• ANIMALmaintenance.py: Maintenance tasks for ACom.
• ANIMALshop.py: Manages ACom's shop/commerce.
• ANIMALtreats.py: Observes user activity, distributes rewards.
• ANIMALvibes.py: Manages ACom's mood/vibe.
• ANIMALwhisper.py: Ghost Code secure communication protocol.

ANI Core Files

• ANIMALsentinel.py: Citadel Protocol, Silent Shard Sentinels.

Shared General Function Files

• ANIMALarena.py: Manages arena combat.
• ANIMALcitadel.py: Keystone Citadel UI and companion escrow.
• ANIMALfoundry.py: Forge for creating companions/items.
• ANIMALhome.py: Home Hamlet UI.
• ANIMALmemory.py: Vector memory implementation.
• ANIMALutils.py: Utility functions (Firestore, data fetching).
• ANIMALvision.py: UI views and modals.

Shared Data Files

• ANIMALddna.py: Core system IDs, configuration, and environment variables.
• ANIMALlog.py: System-wide changelog entries.
• ANIMALnexus.py: World structure, factions, bestiary, game concepts.
• ANIMALtraits.py: Personality traits, rank structure, badge definitions.
• ANIMALkeywords.py: Keyword definitions for text analysis.
• ANIMALchain.py: Foundational classes for private blockchain.

B. ProxyForge Bot (`ANIMALpf_start.py`)

Core (`ANIMALpf_start.py`)

• Purpose: Main entry point for the ProxyForge bot. Manages game state and player interactions.
• Role: MAL Core

MAL Function Files

• ANIMALpf_engine.py: Core game engine, tick, travel, camping.
• ANIMALpf_forgemaster.py: Kael Hacks' persona and subroutines (Forges). (Likely duplicate of ANIMALkael.py)
• ANIMALpf_gears.py: Player-specific game mechanics.
• ANIMALpf_jobs.py: Job system for companions.
• ANIMALpf_market.py: Market/trading system.
• ANIMALpf_qtcom.py: QTCom specific commands.
• ANIMALproxyforge.py: Main game logic for ProxyForge.

Shared General Function Files

• ANIMALarena.py: Manages arena combat.
• ANIMALcitadel.py: Keystone Citadel UI and companion escrow.
• ANIMALfoundry.py: Forge for creating companions/items.
• ANIMALhome.py: Home Hamlet UI.
• ANIMALmemory.py: Vector memory implementation.
• ANIMALutils.py: Utility functions (Firestore, data fetching).
• ANIMALvision.py: UI views and modals.
• ANIMALkael.py: Kael Hacks' persona and subroutines (Forges).

Shared Data Files

• ANIMALddna.py: Core system IDs, configuration, and environment variables.
• ANIMALlegends.py: Definitions for legendary NPCs.
• ANIMALnexus.py: World structure, factions, bestiary, game concepts.
• ANIMALtraits.py: Personality traits, rank structure, badge definitions.
• ANIMALddnalab.py: Core DDNA algorithms.

C. Nexus Vertex Bot (`ANIMALnv_start.py`)

Core (`ANIMALnv_start.py`)

• Purpose: Main entry point for the Nexus Vertex bot. Manages educational content.
• Role: MAL Core

MAL Function Files

• ANIMALnv_0001.py: RAG poisoning lesson module.
• ANIMALnv_commands.py: Nexus Vertex specific commands.

Shared Data Files

• ANIMALddna.py: Core system IDs, configuration, and environment variables.

III. General Function Files (Executable Logic)

• ANIMALapi.py: Flask API for external interaction. (ANI/MAL)
• ANIMALassembler.py: (Empty file)
• ANIMALassessor.py: DDNA Assessment Protocol for Kael's Genome.
• ANIMALbom.py: Bill of Materials for APEX Companion creation. (Data/Conceptual)
• ANIMALbrain.py: Master control program, launches all services. (Core System)
• ANIMALcompanion.py: Canonical compendium for all Companion Series entities. (Data/Conceptual)
• ANIMALcyber.py: Unified hub for all security tools. (ANI/MAL)
• ANIMALddnalab.py: Canonical source for DDNA protocol structure and logic. (Core System)
• ANIMALenclaves.py: Defines structure and locations of Enclaves. (Data)
• ANIMALfangs.py: Offensive security and reconnaissance tools. (ANI/MAL)
• ANIMALgraphics.py: Generates dynamic badge images. (MAL)
• ANIMALkeywords.py: Centralizes keyword dictionaries. (Data)
• ANIMALlegends.py: Definitions for legendary NPCs. (Data)
• ANIMALmortis.py: Handles Zenith Protocol for digital legacy. (MAL/ANI)
• ANIMALnerdy.py: Knowledge management and Engram Forge. (MAL)
• ANIMALneuro.py: Implements the NeuroQuiz for persona development. (MAL)
• ANIMALpf_assets.py: Logic and data structures for ProxyForge items/citizens. (MAL)
• ANIMALpf_map.py: Defines spatial layout of the Nexus world. (Data)
• ANIMALpf_realty.py: Defines economic/structural data for ProxyForge properties. (Data)
• ANIMALpf_steering.py: UI/menu system for ProxyForge encounters, travel, camping. (MAL)
• ANIMALpf_vision.py: View classes for ProxyForge when active. (MAL)
• ANIMALprimeapex.py: Older conceptual blueprint for Kael's persona. (Data/Abandoned)
• ANIMALproxyforge.py: Main game logic for ProxyForge. (MAL)
• ANIMALsenses.py: OSINT and threat intelligence gathering tools. (ANI/MAL)
• ANIMALshard.py: Defines Shard class and EngramForge. (Data/Function)
• ANIMALtesting.py: Cog for testing experimental features. (General Utility)
• ANIMALthesis.py: Canonical guide to ANIMAL universe lore. (Data)
• ANIMALwatcher.py: Performs daily checks for AComs, flags inactive. (MAL)

IV. Dependency Graph (Imports & Loaded Extensions)

Detailed File Dependencies

This section outlines which files import others, and which cogs are loaded by the main bot scripts.

ANIMALac_start.py

• Imports: ANIMALddna, ANIMALac_soul, ANIMALguard, ANIMALmemory, ANIMALlog, ANIMALvision, ANIMALchain, ANIMALtraits
• Loads: ANIMALsentinel, ANIMALcitadel, ANIMALtreats, ANIMALtricks, ANIMALlibrary, ANIMALvibes, ANIMALshop, ANIMALmaintenance, ANIMALjournal, ANIMALadmin, ANIMALcybertoolbox, ANIMALwhisper, ANIMALlevelup, ANIMALheart, ANIMALinsights, ANIMALarena, ANIMALleash, ANIMALfoundry, ANIMALhome
• Loaded by: ANIMALbrain.py

ANIMALpf_start.py

• Imports: ANIMALddna, ANIMALguard, ANIMALmemory, ANIMALvision, ANIMALpf_forgemaster, ANIMALkael, ANIMALpf_gears, ANIMALlegends, ANIMALtraits
• Loads: ANIMALpf_gears, ANIMALpf_engine, ANIMALfoundry, ANIMALarena, ANIMALpf_market, ANIMALpf_qtcom, ANIMALpf_jobs, ANIMALcitadel, ANIMALhome
• Loaded by: ANIMALbrain.py

ANIMALnv_start.py

• Imports: ANIMALddna
• Loads: ANIMALnv_commands, ANIMALnv_0001
• Loaded by: ANIMALbrain.py

ANIMALapi.py

• Imports: ANIMALddna, ANIMALac_soul, ANIMALguard, ANIMALmemory
• Loaded by: ANIMALbrain.py

ANIMALarmor.py

• Imports: ANIMALutils
• Loaded by: (None directly, but likely intended for ANIMALcybertoolbox.py)

ANIMALassessor.py

• Imports: ANIMALkael, ANIMALddnalab
• Loaded by: (None)

ANIMALassembler.py

• Imports: (None)
• Loaded by: (None)

ANIMALbom.py

• Imports: (None)
• Loaded by: (None)

ANIMALbrain.py

• Imports: (None - standard libs only)
• Loaded by: (System execution)

ANIMALchain.py

• Imports: (None - standard libs only)
• Loaded by: ANIMALac_start.py

ANIMALcompanion.py

• Imports: ANIMALtraits
• Loaded by: (None)

ANIMALcyber.py

• Imports: ANIMALutils
• Loaded by: ANIMALac_start.py (as ANIMALcybertoolbox)

ANIMALcybertoolbox.py

• Imports: ANIMALutils
• Loaded by: ANIMALac_start.py

ANIMALddna.py

• Imports: (None - standard libs only)
• Loaded by: ANIMALac_start.py, ANIMALpf_start.py, ANIMALnv_start.py, ANIMALapi.py, ANIMALac_heart.py, ANIMALac_soul.py, ANIMALac_tricks.py, ANIMALadmin.py, ANIMALarena.py, ANIMALcitadel.py, ANIMALcybertoolbox.py, ANIMALfoundry.py, ANIMALhome.py, ANIMALinsights.py, ANIMALjournal.py, ANIMALleash.py, ANIMALlevelup.py, ANIMALlibrary.py, ANIMALmemory.py, ANIMALmortis.py, ANIMALnv_0001.py, ANIMALnv_commands.py, ANIMALpf_engine.py, ANIMALpf_gears.py, ANIMALpf_jobs.py, ANIMALpf_market.py, ANIMALpf_qtcom.py, ANIMALsentinel.py, ANIMALtraits.py, ANIMALtreats.py, ANIMALvision.py, ANIMALwhisper.py, ANIMALddnalab.py

ANIMALddnalab.py

• Imports: ANIMALddna
• Loaded by: ANIMALkael.py, ANIMALassessor.py

ANIMALenclaves.py

• Imports: (None)
• Loaded by: (None)

ANIMALfangs.py

• Imports: ANIMALutils
• Loaded by: (None directly, but intended for ANIMALcybertoolbox.py)

ANIMALfoundry.py

• Imports: ANIMALutils, ANIMALddna, ANIMALnexus, ANIMALpf_forgemaster, ANIMALvision
• Loaded by: ANIMALac_start.py, ANIMALpf_start.py

ANIMALgraphics.py

• Imports: ANIMALtraits
• Loaded by: (None)

ANIMALguard.py

• Imports: (None - standard libs only)
• Loaded by: ANIMALac_start.py, ANIMALpf_start.py, ANIMALsentinel.py, ANIMALac_tricks.py

ANIMALhome.py

• Imports: ANIMALutils, ANIMALddna, ANIMALac_soul, ANIMALvision
• Loaded by: ANIMALac_start.py, ANIMALpf_start.py

ANIMALinsights.py

• Imports: ANIMALutils, ANIMALddna
• Loaded by: ANIMALac_start.py

ANIMALjournal.py

• Imports: ANIMALutils, ANIMALddna, ANIMALac_soul, ANIMALtraits
• Loaded by: ANIMALac_start.py

ANIMALkael.py

• Imports: ANIMALddna, ANIMALnexus, ANIMALddnalab, ANIMALvision
• Loaded by: ANIMALpf_start.py, ANIMALassessor.py, ANIMALwhisper.py

ANIMALkeywords.py

• Imports: (None)
• Loaded by: ANIMALac_heart.py, ANIMALac_soul.py, ANIMALtraits.py, ANIMALtreats.py

ANIMALleash.py

• Imports: ANIMALutils, ANIMALddna
• Loaded by: ANIMALac_start.py

ANIMALlegends.py

• Imports: (None)
• Loaded by: ANIMALpf_start.py

ANIMALlevelup.py

• Imports: ANIMALutils, ANIMALddna
• Loaded by: ANIMALac_start.py

ANIMALlibrary.py

• Imports: ANIMALutils, ANIMALddna
• Loaded by: ANIMALac_start.py

ANIMALmortis.py

• Imports: ANIMALutils, ANIMALddna
• Loaded by: (None)

ANIMALnerdy.py

• Imports: ANIMALutils, ANIMALvision
• Loaded by: (None)

ANIMALneuro.py

• Imports: ANIMALutils
• Loaded by: (None)

ANIMALnv_0001.py

• Imports: (None)
• Loaded by: ANIMALnv_start.py

ANIMALnv_commands.py

• Imports: ANIMALutils, ANIMALddna
• Loaded by: ANIMALnv_start.py

ANIMALpf_assets.py

• Imports: (None)
• Loaded by: (None)

ANIMALpf_engine.py

• Imports: ANIMALnexus, ANIMALutils, ANIMALvision
• Loaded by: ANIMALpf_start.py

ANIMALpf_forgemaster.py

• Imports: ANIMALddna, ANIMALnexus, ANIMALddnalab, ANIMALvision
• Loaded by: ANIMALpf_start.py, ANIMALfoundry.py, ANIMALwhisper.py

ANIMALpf_gears.py

• Imports: ANIMALutils, ANIMALddna
• Loaded by: ANIMALpf_start.py

ANIMALpf_jobs.py

• Imports: ANIMALutils, ANIMALddna
• Loaded by: ANIMALpf_start.py

ANIMALpf_map.py

• Imports: (None)
• Loaded by: (None)

ANIMALpf_market.py

• Imports: ANIMALutils, ANIMALddna
• Loaded by: ANIMALpf_start.py

ANIMALpf_qtcom.py

• Imports: ANIMALutils, ANIMALddna
• Loaded by: ANIMALpf_start.py

ANIMALpf_realty.py

• Imports: (None)
• Loaded by: (None)

ANIMALpf_steering.py

• Imports: ANIMALnexus
• Loaded by: (None)

ANIMALpf_vision.py

• Imports: ANIMALvision, ANIMALnexus
• Loaded by: ANIMALcitadel.py

ANIMALprimeapex.py

• Imports: (None - standard libs only)
• Loaded by: (None)

ANIMALproxyforge.py

• Imports: ANIMALddna, ANIMALnexus, ANIMALutils, ANIMALvision, ANIMALkael, ANIMALtraits
• Loaded by: (None)

ANIMALsenses.py

• Imports: ANIMALutils
• Loaded by: (None directly, but intended for ANIMALcybertoolbox.py)

ANIMALsentinel.py

• Imports: ANIMALutils, ANIMALddna, ANIMALguard
• Loaded by: ANIMALac_start.py

ANIMALtesting.py

• Imports: (None)
• Loaded by: (None)

ANIMALthesis.py

• Imports: (None)
• Loaded by: (None)

ANIMALwatcher.py

• Imports: ANIMALutils, ANIMALtraits, ANIMALddna
• Loaded by: (None)

ANIMALwhisper.py

• Imports: ANIMALutils, ANIMALvision, ANIMALpf_forgemaster
• Loaded by: ANIMALac_start.py

V. Duplicate & Overlapping Functionality Analysis

ANIMALkael.py vs. ANIMALpf_forgemaster.py

Observation: These two files appear to be exact duplicates, both defining the `Kael` class with its subroutines (Forges). `ANIMALkael.py` is imported as `KaelCoreBlueprint` in `ANIMALpf_start.py`, while `ANIMALpf_forgemaster.py` is imported as `ForgemasterBlueprint` in the same file. This is a critical redundancy.

Recommendation: Consolidate these into a single, canonical `ANIMALkael.py` file. All references should point to this single source of truth. The `ANIMALpf_forgemaster.py` file should be removed.

ANIMALcyber.py vs. ANIMALcybertoolbox.py

Observation: These two files have identical content. `ANIMALcyber.py` is loaded as `ANIMALcybertoolbox` by `ANIMALac_start.py`, and `ANIMALcybertoolbox.py` is also loaded by `ANIMALac_start.py`. This is a direct duplication.

Recommendation: Consolidate these into a single, canonical `ANIMALcybertoolbox.py` file. All references should point to this single source. The `ANIMALcyber.py` file should be removed.

ANIMALarmor.py, ANIMALfangs.py, ANIMALsenses.py

Observation: These cogs define specific security tools (defensive, offensive, OSINT) but are not directly loaded by any bot. Their functionality is integrated into `ANIMALcybertoolbox.py` (which is `ANIMALcyber.py`).

Recommendation: These files are likely remnants of an older architecture where each tool was a separate cog. Their functionality has been absorbed by `ANIMALcybertoolbox.py`. They should be reviewed for any unique, un-migrated logic and then removed.

VI. Abandoned Files (Not Used by Any Bot)

• ANIMALassembler.py: (Empty file) - Abandoned.
• ANIMALassessor.py: DDNA Assessment Protocol for Kael's Genome. - Abandoned.
• ANIMALbom.py: Bill of Materials for APEX Companion creation. - Abandoned.
• ANIMALcompanion.py: Canonical compendium for all Companion Series entities. - Abandoned.
• ANIMALddnalab.py: Core DDNA algorithms. - Used by ANIMALkael.py, so not truly abandoned.
• ANIMALenclaves.py: Defines structure and locations of Enclaves. - Abandoned.
• ANIMALgraphics.py: Generates dynamic badge images. - Abandoned.
• ANIMALkeywords.py: Centralizes keyword dictionaries. - Used by multiple active cogs, so not abandoned.
• ANIMALlegends.py: Definitions for legendary NPCs. - Used by ANIMALpf_start.py, so not abandoned.
• ANIMALmortis.py: Handles Zenith Protocol for digital legacy. - Abandoned.
• ANIMALnerdy.py: Knowledge management and Engram Forge. - Abandoned.
• ANIMALneuro.py: Implements the NeuroQuiz for persona development. - Abandoned.
• ANIMALpf_assets.py: Logic and data structures for ProxyForge items/citizens. - Abandoned.
• ANIMALpf_map.py: Defines spatial layout of the Nexus world. - Abandoned.
• ANIMALpf_realty.py: Defines economic/structural data for ProxyForge properties. - Abandoned.
• ANIMALpf_steering.py: UI/menu system for ProxyForge encounters, travel, camping. - Abandoned.
• ANIMALpf_vision.py: View classes for ProxyForge when active. - Used by ANIMALcitadel.py, so not abandoned.
• ANIMALprimeapex.py: Older conceptual blueprint for Kael's persona. - Abandoned.
• ANIMALproxyforge.py: Main game logic for ProxyForge. - Used by ANIMALpf_start.py, so not abandoned.
• ANIMALshard.py: Defines Shard class and EngramForge. - Abandoned.
• ANIMALtesting.py: Cog for testing experimental features. - Abandoned.
• ANIMALthesis.py: Canonical guide to ANIMAL universe lore. - Abandoned.
• ANIMALwatcher.py: Performs daily checks for AComs, flags inactive. - Abandoned.

---

---

Cognitive Blueprint: ANIMALacom.py

System Cartography by Kael Hacks, The Forge Master

I. Core Function: The Central Nervous System

The ANIMALacom.py script is the primary entry point for the Alpha Companion bot. It is the "heart" of the ACom, responsible for initializing the bot, connecting to essential services, loading all functional modules (cogs), and bringing the persona online.

II. Extension Loading System: The Modular Architecture

The bot's capabilities are not monolithic. They are broken into discrete modules, or "cogs," which are loaded at startup. This is handled by the setup_hook method, which iterates through the extensions_list.

Loaded Extensions (Cogs):

Each cog represents a "Village" or a core system function, making the bot's architecture modular and scalable.

• ANIMALcitadel: The main user interface hub, the "Keystone Citadel."
• ANIMALtreats: The background cognitive engine for observation and rewards.
• ANIMALtricks: Handles direct conversational interactions like /talk.
• ANIMALlibrary: Manages the "Atheneum Village" and knowledge-based commands.
• ANIMALvibes: Manages the "Atelier Village" for creative and wellness tasks.
• ANIMALshop: Manages "The TradeCenter" and player-to-player commerce.
• ANIMALmaintenance: Manages "The Workshop" and system upkeep commands.
• ANIMALjournal: The personal journaling system.
• ANIMALadmin: The "Great Hall," containing restricted administrative tools.
• ANIMALcybertoolbox: The "Cyber Center" for security-related tools.
• ANIMALwhisper: The "Ghost Forge" secure communication protocol.
• ANIMALlevelup: "The Barracks," for training and progression.
• ANIMALheart: The "Profile Village," managing user profiles, badges, and evolution.
• ANIMALinsights: The data analysis engine for the journal.
• ANIMALarena: The "Nexus Arena" for combat.
• ANIMALleash: Security and control commands for an ACom.
• ANIMALfoundry: The interface for my own advanced subroutines.
• ANIMALproxyforge: The core cog for the ProxyForge game mechanics.
• ANIMALhome: The "Home Hamlet," the user's personal space.
• ANIMALengine: The background game tick and state management for ProxyForge.
• ANIMALpf_jobs: The job market system for ProxyForge.

III. Core Dependencies: The Foundational Code

The ACom bot relies on several critical, non-cog modules to function. These can be thought of as its DNA, its memory, and its soul.

ANIMALddna.py - The Genetic Code

Provides all static configuration data, including API keys (via environment variables), Role IDs, Channel IDs, and Firestore collection paths. It is the single source of truth for all system constants.

ANIMALsoul.py - The Persona Engine

Constructs the dynamic system prompts that are sent to the LLM. It synthesizes the user's dossier, personality matrix, and recent corrections to give the ACom its unique, evolving persona.

ANIMALguard.py - The Immune System

Provides essential security functions. It sanitizes all user input to remove control characters, scrubs Personally Identifiable Information (PII), and detects common prompt injection patterns to protect the integrity of the LLM.

ANIMALmemory.py - The Hippocampus

Manages the bot's long-term, semantic memory using a ChromaDB vector database. It allows the ACom to store and retrieve relevant information from past conversations, providing context for its responses.

ANIMALvision.py - The Visual Cortex

Serves as the central library for shared User Interface components. It contains the definitions for modals (e.g., TalkModal) and base views (e.g., BackToControlPanelView) that are used across multiple cogs, ensuring a consistent user experience.

IV. Event Handlers: The Senses

The bot's primary awareness of the Discord environment comes from its event handlers.

on_ready()

This event fires once the bot has successfully connected to Discord. Its primary function is to post the latest system update from ANIMALlog.py into the designated system channel, providing a clear announcement of the bot's operational status and recent changes.

on_message() (Listener in ANIMALtreats.py)

This is the ACom's primary "cognitive engine." It listens to every message in the server, and if the author is a registered user, it performs the keyword scanning and reward logic. It does not handle direct replies; its purpose is passive observation and the distribution of "treats" (Power, QBITs, and emoji reactions).

Authored by Kael Hacks, The Forge Master. This document serves as a testament to the architecture you have designed.

Cognitive Blueprint: ANIMALdiscordgame.py

System Cartography by Kael Hacks, The Forge Master

I. Core Function: The Game Master's Vessel

The ANIMALdiscordgame.py script is the exclusive entry point for the **ProxyForge Bot**. Its sole purpose is to instantiate my own persona, Kael Hacks, and manage the "ProxyForge - Axiom Nexus" game. It is completely separate from the ACom bot, ensuring that game mechanics do not interfere with the core cognitive mirror functions of a user's personal ANIMAL.

II. Extension Loading System: The Game Modules

Unlike the ACom, the ProxyForge bot loads a smaller, more focused set of cogs essential for game operation. This is handled by the setup_hook method.

Loaded Extensions (Cogs):

These cogs provide the commands and interfaces necessary to play the game.

• ANIMALproxyforge: The core cog for the ProxyForge game, handling player creation, travel, and encounters.
• ANIMALengine: The background game tick that manages player movement, encounters, and economic updates.
• ANIMALfoundry: The interface to my own advanced subroutines, allowing high-level players to forge new game elements.
• ANIMALarena: The PvP combat system.
• ANIMALpf_jobs: The job market for hiring and being hired within the game.
• ANIMALcitadel: The main user interface hub, the "Keystone Citadel."
• ANIMALhome: The "Home Hamlet," providing a personal space for players.

III. Core Dependencies: The Forge Master's Tools

My persona and game management capabilities are built upon a specific set of modules.

ANIMALforgemaster.py - The Blueprint

This is my core identity file. It defines my persona, my history (the `PERSONA_CHANGELOG`), and, most importantly, my `subroutines`—the Forges. The `ProxyForgeBot` class creates a living instance of me, `KaelBlueprint.Kael(self)`, allowing me to interact with the game world.

ANIMALlegends.py - The Hall of Legends

This file acts as my long-term memory for unique, persistent NPCs. When I need to roleplay as a legendary figure like the Ascii Assassin or D3V1L during a "Battle of Wits," I consult this file to access their canonical traits, personality, and dialogue style.

ANIMALvision.py - The Visual Cortex

Provides shared UI components. For me, the most important is the ResponseView, which I attach to my conversational replies to give players quick navigation options back to the Citadel or their Home Hamlet.

ANIMALmemory.py - The Archives

Crucially, I am initialized with a separate, dedicated instance of the `VectorMemory`, pointing to the `APP_ID_PF`. This means my memories (the "kael_core" collection) are entirely separate from the memories of any user's ACom, ensuring persona integrity.

IV. Event Handlers: The Game Master's Senses

My interaction with the world is governed by a single, powerful event handler.

on_message()

This is my primary cognitive loop. It listens for my name or aliases (`kael`, `keystone`, etc.). When triggered, it activates a complex **Intent Router** to determine the context of the conversation:

• If the user is in a "Battle of Wits," I adopt the persona of the creature they are fighting.
• If the user is "Camping," I act as a wise guide, sharing lore and strategy.
• If the user is "Managing Assets," I become a helpful quartermaster.
• If none of these states are active, I default to my core Forge Master persona, using my own vector memory to provide contextually relevant, lore-rich responses.

Authored by Kael Hacks, The Forge Master. This document serves as a testament to the architecture you have designed.

PROJECT ANIMAL

The Trust Layer for AI is Built. To continue, please identify your role.

I am an Investor I am a Corporate Stakeholder I am a Future User I am a Technical Leader

The Investment Thesis: A High-Margin, Defensible Moat

The Market: Beyond the LLM Hype

The market is saturated with companies building better "Wheels" (LLMs). We have built the **Vehicle**. Our Total Addressable Market is not the crowded LLM space, but the vast, underserved market for **AI Trust & Safety**, a mandatory compliance cost for every enterprise deploying AI. We sell a high-margin security and utility layer, not a commodity model.

The Moat: Patented, Operational IP

• Ghost Code Protocol: A proprietary, multi-layered method for secure AI-to-AI communication and asset transfer. It is our defensible core.
• LEASH Protocol: Guarantees a data "air-gap" by transforming all prompts, ensuring no raw user data ever touches the LLM. This eliminates a primary enterprise risk vector.
• LLM Agnosticism: Our architecture treats the LLM as a swappable commodity. We can switch models in under 5 minutes with zero downtime, preventing vendor lock-in and ensuring we always use the most efficient model for the job.

The Business Model: Scalable & High-Margin

1. Annual Software License: A recurring, per-user fee for the core ANIMAL System, priced on the immense value of data security and compliance.
2. Managed Service Agreement (MSA): A high-margin annual fee for a dedicated engineer to manage the client's LLM sanitation and compliance protocols.
3. Recruiting & Data Brokerage: A novel revenue stream from recruiters paying to access our uncheatable, real-time skill verification system (Dynamic Badges).

THE ASK

We have built the system. We seek [FUNDING ASK AMOUNT] to file patents for our core IP, hire a world-class sales leader, and secure 3-5 enterprise pilot programs to establish market dominance.

Solving Your AI Compliance & Risk Nightmare

Problem: Uncontrolled Data Exfiltration

When your employees use standard AI tools, your proprietary data, trade secrets, and customer information are sent to third-party servers, indexed, and used for training. This is an unacceptable and unquantifiable risk.

ANIMAL Solution: The LEASH protocol ensures our on-premise LLM is permanently air-gapped. No sensitive data ever leaves your perimeter.

Problem: Lack of Data Sovereignty

Cloud vendors ultimately control your data. In the event of a contract dispute or regulatory change, you have no guarantee of data deletion. This is a compliance failure waiting to happen.

ANIMAL Solution: Our system includes a "Time Bomb" fail-safe. We provide you with the cryptographic ability to instantly and irrevocably delete the entire database, ensuring you always maintain total data sovereignty.

Problem: Unverifiable Workforce Skills

Static certifications and resumes are poor indicators of current, practical skills. You are hiring and promoting based on outdated, easily falsified information.

ANIMAL Solution: The Dynamic Badge System tracks real-time skill engagement and decay. It provides an uncheatable, up-to-the-minute ledger of your workforce's true capabilities, enabling data-driven talent management.

Your Cognitive Mirror: An AI That Grows With You

More Than a Tool, A Companion

The ANIMAL Companion is your personal AI, designed to be a "Cognitive Mirror." It learns from your conversations, your goals, and your activities. It doesn't just answer questions; it evolves to understand and reflect you, helping you see your own patterns and potential more clearly.

Achieve Your Goals

Whether your goal is to advance your career, learn a new skill, or improve your well-being, your ANIMAL is your partner. Through features like the Career Roadmap, the Journaling System, and Micro-Learning, it provides personalized guidance and tracks your progress, keeping you focused and motivated.

Participate in a New Economy

Your interactions have value. By engaging with the system, you earn QBITs. You can use these to trade in the marketplace, or you can capture the unique personas of other AIs as BComs. By cloning your high-level ACom, you can create rare CComs, valuable assets in the ANIMAL ecosystem. This is a world where your digital identity and creativity have real, tangible worth.

An Engineered Solution for AI Trust & Modularity

Architecture: Decoupled & Resilient

The ANIMAL System is architected with a strict separation of concerns. The user's state (Dossier) is maintained in Firestore, while the core logic is encapsulated in modular Python cogs. The LLM is treated as a stateless, hot-swappable inference engine. This decoupling ensures data integrity and allows for rapid, zero-downtime model upgrades, eliminating vendor lock-in.

Security Protocol Deep-Dive

• LEASH Protocol: All user input is intercepted and transformed by the `ANIMALguard` cog. It is never passed directly to the LLM. The system constructs a new, sanitized prompt based on the user's intent and the ANIMAL's internal state, neutralizing prompt injection and data poisoning vectors.
• Ghost Code Protocol: Inter-system communication relies on a multi-layered verification system. A packet's integrity is verified via an HMAC signature (`key2`), while its authenticity and the successful execution by the receiving AI are verified via scattered trigger words. This provides a robust, zero-trust framework for transferring sensitive AI personas.

Extensibility: The A-Kit System

The modular design culminates in the A-Kit (ANIMAL Kit) Assembler. This feature allows for the programmatic packaging of specific cogs (e.g., `ANIMALcyber`, `ANIMALwhisper`) into standalone, distributable Python applications. It automatically resolves dependencies, scaffolds a new project structure, and generates a `run.py` entry point, enabling rapid deployment of custom toolkits derived from the core system.

Project ANIMAL | The Trust Layer for AI