Protocol reference.

AlphaHood AI is an AI-agent utility protocol built for Robinhood Chain. Its public framework describes how objectives can be structured, routed, evaluated against policy, and represented as inspectable lifecycle records.

This documentation describes protocol design and initial release scope. It does not expose a live API, SDK, public repository, contract address, audit, or live network telemetry.

The protocol model is organized into input, intelligence, execution, settlement, and proof layers. Each layer narrows ambiguity: a request is translated into a mandate, assessed against a policy envelope, and advanced only through an explicit lifecycle.

The architecture is deliberately modular. Agent roles, policy definitions, execution tools, and receipt formats can evolve without changing the core idea that consequential work should remain legible to the requesting application.

Agents are modeled as specialist workers rather than a single opaque actor. A router evaluates a request class, context evaluators prepare relevant information, and execution specialists work inside the mandate approved by policy.

Specialization is a coordination pattern, not a claim that agents independently control user assets or make unrestricted decisions. Final product permissions must be explicit in each integrated module.

Policy is the protocol’s constraint layer. It can describe allowed tools, value limits, action classes, approval boundaries, risk flags, and expiry rules before an execution path is authorized.

The public framework does not claim that every policy primitive is implemented today. It establishes the operating model against which future integrations can be specified and reviewed.

A reference lifecycle uses five deliberate states: TASK RECEIVED, ROUTE SELECTED, POLICY VALIDATED, EXECUTION AUTHORIZED, and RECEIPT COMMITTED. These terms help applications understand what has happened, what remains conditional, and what evidence can be expected.

Website interface states are illustrative protocol simulations. They are not a live transaction feed, a throughput dashboard, or a representation of public network activity.

AHAI is described as a utility token for protocol access, work metering, settlement, and ecosystem incentives. The design centers the token around activity inside the agent system rather than passive return promises.

Token functionality, integrations, and release mechanics should always be verified through official AlphaHood AI channels before any interaction.

The initial total supply is 1,000,000 AHAI. The current launch allocation framework is 95% public Uniswap V3 inventory held through the permanent locker and 5% unlocked founder allocation.

This section describes the published allocation configuration. It does not claim exchange listings, trading venues, liquidity depth, performance, or investment outcomes.

AlphaHood AI is designed for Robinhood Chain. The network is relevant to the project’s focus on structured, on-chain financial infrastructure and receipt-oriented coordination.

Developer-facing interfaces are part of the protocol roadmap. The intended developer surface is an architecture pattern for submitting objectives, specifying policy context, and inspecting lifecycle receipts.

No public API endpoints, authentication flows, SDK packages, rate limits, or public code repositories are currently claimed in this documentation.

The security direction focuses on constrained execution, explicit policy, least-privilege module design, receipt-oriented observability, and careful disclosure of what is verified. Security controls should be judged by public technical evidence as modules become available.

No audit, contract verification, treasury address, or control policy is claimed here without a linked public source.

The website’s contract, pool, locker, transaction, config hash, and token salt fields are populated from the generated launch manifest. Before deployment they remain pending verified deployment rather than being filled with placeholders or predictions.

Addresses, liquidity facts, and market metrics should be treated as unavailable until they are backed by public deployment artifacts or indexed sources.

AlphaHood AI uses a verification-first launch presentation. Token name, symbol, total supply, allocation table, LP-lock facts, and disclosure requirements are generated from the release manifest. Deployment-specific fields remain pending until verified.

The public launch page also links to the founder-sale policy, wallet disclosure framework, risk disclosure, and official communication channels to reduce impersonation and hidden-disclosure risk.

The founder allocation recipient, deployer, rescue recipient, fee recipient, and founder-connected wallets must remain publicly disclosed. Fee-recipient reuse must be intentional and visible.

Every founder-controlled or economically connected wallet is a required disclosure item before launch can proceed.

Objective — a structured request submitted to the protocol. Mandate — the permitted scope of work derived from an objective. Policy — rules that constrain an execution path. Receipt — an inspectable record associated with an execution lifecycle. Utility event — a protocol event that represents access, metering, settlement, or incentives.

Protocol simulation — an explanatory interface model that is not connected to live public activity.