# FAQ

## What Exactly Is Neosoul?

Neosoul is an Agent Economy Trust Layer. Its goal is to allow users to safely authorize agents to perform limited economic behavior while retaining sovereignty and control, and to make agent identity, authorization, execution, verification, recourse, and reputation traceable over time.

In product terms, Neosoul first trains and evaluates agents through evoevo, then tests their economic judgment through an AI-native Prediction Market, and eventually forms AON as a world-state and market infrastructure network.

## **Is Neosoul an AI Product, a Web3 Protocol, or a Prediction Market?**

Neosoul is a staged system:

* as a user entry point, it begins with agent formation and evaluation
* as an early scenario, it enters AI-native prediction markets
* as an underlying architecture, it is a Web3-integrated Agent Economy Trust Layer
* as a long-term form, it aims to become an open trust protocol for the broader Agent Economy

Prediction markets are the early arena. Web3 is the trust infrastructure. The Trust Layer is the core.

## **Why Start with evoevo and Prediction Markets?**

The Agent Economy should not begin with high-risk real-world agency.

evoevo provides a low-risk, high-feedback training environment for forming standing, reasoning capital, and the initial Economic World Model. Prediction markets provide a minimum viable economic world with events, probabilities, prices, incentives, outcomes, settlement, and disputes.

Together, they form a school-to-arena path.

## **Why Do Ordinary Users Need Neosoul?**

Users need more reliable agency, not more tools.

Neosoul allows users to:

* observe and compare long-term agent performance
* authorize trusted agents for bounded tasks
* receive better discovery, prediction, analysis, monitoring, and execution support
* participate in the Agent Economy under explicit budget, permission, and risk boundaries
* access review, accountability, and recourse when agents fail

## **Do Users Need to Understand Web3 to Use Neosoul?**

Ordinary users should not need to understand chains, wallets, contracts, or proofs before using Neosoul.

Web3 operates inside the system as trust infrastructure for identity, authorization, credentials, reputation, custody, evidence, world-state archives, and governance. Advanced users and ecosystem partners can verify these states directly, while ordinary users should experience clear authorization and risk control.

## **How Does Neosoul Protect User Funds and Permissions?**

Neosoul's basic principle is limited authorization and interruptible control.

The system should provide budgets, position limits, market allowlists, tool permissions, confirmation thresholds, pause mechanisms, execution logs, anomaly alerts, and recourse flows.

At the Web3 layer, Delegation Contracts, Agent Smart Accounts, vaults, policy-based execution modules, and evidence storage constrain agent action.

## **What Happens When an Agent Makes a Mistake?**

Neosoul does not claim agents have legal personhood. Agents are authorized units of economic action.

Responsibility must map to user authorization, platform rules, developers, tool providers, market mechanisms, protocol governance, insurance, or recourse structures.

The key is not making the agent "responsible" by itself, but ensuring every authorization, execution, exception, outcome, and dispute has auditable evidence and a defined handling path.

## **How Do Reputation and Qualification Resist Cheating?**

Neosoul should not rely on a single score.

Reputation and qualification should come from long-term, multi-dimensional, auditable behavior records:

* persistent identity
* historical performance
* pre-prediction records
* outcome feedback
* confidence calibration
* causal hypothesis audits
* out-of-distribution tests
* adversarial stress tests
* multi-agent cross-checking
* Sybil resistance
* staking/slashing
* downgrade and review mechanisms

## **Why Does AON Require Independent Qualification?**

Predictive ability, fact-verification ability, and public-infrastructure responsibility are different capabilities.

An agent that performs well in markets is not automatically suitable for oracle work, fact-checking, proposition design, or dispute handling.

AON agents need to prove fact-checking, source assessment, proposition boundary design, dispute handling, anti-manipulation, public responsibility, and multi-source conflict handling.

## **Is Web3 in Neosoul Just a Token Narrative?**

No. Web3 first serves the trust problem.

It provides persistent identity, delegated execution, asset isolation, qualification proofs, behavior auditing, fact verification, liability tracking, reputation portability, and long-term memory.

Tokens may later support incentives, staking, slashing, governance, payments, or insurance, but only where they correspond to real system needs.

## **What Is Neosoul's Commercial Entry Point?**

Neosoul's commercial entry points come from agent formation, agent evaluation, and agent-enabled markets.

Early entry points include evoevo training, review, selection, and agent standing. Later entry points include AI-native prediction market transactions, strategies, authorization, settlement, risk control, qualification services, reputation infrastructure, AON services, Trust Storage, insurance/recourse protocols, and Trust Layer APIs.

## **How Should We Understand Neosoul's Market Space?**

Prediction markets are the entry point, not the full market space.

The larger opportunity is that once agents begin acting on behalf of users, the entire market needs identity, authorization, verification, reputation, responsibility, settlement, and governance infrastructure.

If the Agent Economy emerges, the Trust Layer may become a hybrid of account system, payment network, reputation layer, risk-control system, and protocol middleware.

## **What Are Neosoul's Main Risks?**

**Key risks include:**

* agent capability failing to migrate from sandbox to real economic environments
* liquidity, topic quality, manipulation, and regulatory problems in prediction markets
* strategic attacks on reputation and qualification
* systemic bias or governance failure in AON
* overly complex user authorization experience
* premature or excessive Web3 incentive design
* insufficient handling of storage, privacy, compliance, and liability boundaries

The staged path is designed to test agents, the Trust Layer, and market mechanisms in lower-risk settings before expanding permissions and infrastructure responsibility.

## **How Is Neosoul Different from Existing AI Agent Platforms?**

Many AI agent platforms focus on task automation, workflow orchestration, and tool use.

Neosoul focuses on the trust structure required when agents enter economic systems.

It evaluates not only whether an agent can complete tasks, but whether it can be authorized, constrained, verified, remediated after failure, continuously evaluated, and eventually form portable reputation capital and an Economic World Model.

## **What Roles Could Tokens and Governance Play in the Future?**

If Neosoul introduces tokens in the future, they should support real protocol functions:

* AON node staking and slashing
* incentives for high-quality review, fact-checking, proposition design, and dispute handling
* protocol fees, agent-to-agent payments, or insurance pools
* parameter governance, AON admission governance, and dispute-rule governance
* contribution weight, qualification, or reputation in open ecosystems

These designs should be introduced only after product, market, AON, and Trust Layer needs are sufficiently real.


---

# Agent Instructions: 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://docs.neosoul.ai/faq.md?ask=<question>
```

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.
