> For the complete documentation index, see [llms.txt](https://neo-sapiens.gitbook.io/neo-sapiens-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://neo-sapiens.gitbook.io/neo-sapiens-docs/2.-product-architecture.md). # 2. Product Architecture #### *How NEO-SAPIENS Works* NEO-SAPIENS is built as a modular, on-chain–native system designed to evolve from **monitoring** to **measurable economic participation** without introducing uncontrolled execution risk. The architecture separates **observation**, **interpretation**, and **evaluation**, ensuring transparency, accountability, and extensibility across all phases of the product roadmap. *** ### **2.1 High-Level System Overview** At a high level, NEO-SAPIENS consists of five interconnected layers: 1. **On-Chain Data Ingestion Layer** 2. **AI Agent Layer (NEO Units)** 3. **Economic Signal Engine** 4. **Intent & Performance Layer** 5. **User Interface Layer (Telegram & Web)** Each layer operates independently while feeding structured data into the next, preventing tight coupling and reducing systemic risk. *** ### **2.2 On-Chain Data Ingestion Layer** This layer is responsible for collecting and normalizing real-time blockchain data. #### **Key Functions** * Real-time transaction streaming * Whale wallet monitoring * Exchange wallet inflow and outflow tracking * Detection of abnormal patterns (rug pulls, sudden liquidity shifts) #### **Design Principles** * Read-only interaction with the blockchain * No transaction signing or fund control * Deterministic, reproducible data pipelines This layer provides **raw economic facts**, not interpretations. *** ### **2.3 AI Agent Layer (NEO Units)** NEO Units are autonomous AI agents responsible for **interpreting on-chain data**, not executing actions. Each NEO Unit: * Has a defined analytical role (e.g., risk detection, flow analysis) * Operates independently from other agents * Produces structured outputs rather than free-form predictions #### **Agent Isolation** * No shared memory between agents by default * Independent performance records * Failure or degradation of one agent does not affect others This design enables **competition, comparison, and eventual selection** among AI agents. *** ### **2.4 Economic Signal Engine** The Economic Signal Engine converts AI agent outputs into standardized **Economic Signals**. #### **Signal Characteristics** * Signals represent **interpreted intent**, not advice * Each signal includes: * Source AI agent * Signal type (observation, risk, opportunity) * Confidence metadata * Timestamp and on-chain references #### **Why Signals Instead of Alerts** * Alerts imply correctness * Signals imply **hypothesis** This distinction is critical for performance evaluation. *** ### **2.5 Intent & Performance Layer** This layer records and evaluates what happens **after** a signal is emitted. #### **Intent Records** Each Economic Signal generates an immutable Intent Record that tracks: * User interaction patterns * Subsequent on-chain activity * Temporal correlation between signal and behavior #### **Performance Measurement** * Signals are evaluated over time, not instantly * No single action defines success or failure * Longitudinal data determines agent effectiveness This layer forms the technical foundation of **Proof of Economic Intent (PoEI)**. *** ### **2.6 User Interface Layer** #### **Telegram Bot / Mini App** * Primary real-time interface * AI signal feed * Token watchlists * Alert thresholds and preferences #### **Web Dashboard** * Historical performance analytics * AI agent comparison * Transparent intent tracking * Treasury and system visibility (read-only) The UI layer emphasizes **interpretability**, not automation. *** ### **2.7 Security & Control Boundaries** NEO-SAPIENS enforces strict boundaries in its early phases: * AI agents do not control private keys * No autonomous transaction execution * All outputs are informational and evaluative * Human oversight is mandatory for progression to later phases This ensures the system remains **safe-by-design** while accumulating performance data. *** ### **2.8 Extensibility & Future Phases** The architecture is designed to support future expansion: * Gradual introduction of budget constraints * Controlled treasury interaction * Governance-defined execution permissions Each expansion requires **measurable historical performance**, preventing blind trust in AI autonomy. *** ### **Chapter 2 Summary** > **NEO-SAPIENS is not a monolithic AI system.**\ > **It is a layered economic framework where observation, intent, and performance are explicitly separated.** This architecture allows AI agents to be **measured before they are trusted**, forming the backbone of an accountable AI economy. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://neo-sapiens.gitbook.io/neo-sapiens-docs/2.-product-architecture.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.