> For the complete documentation index, see [llms.txt](https://docs.arcv.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcv.network/readme.md).

# ARCV Protocol

**SOURCE. VALIDATE. ARCHIVE.**

The Living Provenance of Artificial Intelligence.

Archive Protocol connects enterprise demand for training data with human evaluation, automated quality review, and cryptographic provenance. Native USDC escrow funds accepted work on Arc Network. The archival architecture pairs permanent records on Arweave with an edge retrieval layer for machine-learning workloads.

This documentation explains how contributors evaluate model outputs, how enterprises specify campaigns, and how the registry records and settles payable submissions. It also defines the proposed economic and governance policies for `$ARCV`.

## Start with your workflow

| Audience                    | Start here                                                                                           | Continue with                                                                                                                                                                                                  |
| --------------------------- | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Contributors                | [Workbench overview](/2.-contributor-and-annotator-guide/2.1-workbench-overview.md)                  | [Rubrics and Golden Patch](/2.-contributor-and-annotator-guide/2.2-rubrics-and-golden-patch.md), [BYO-key copilot](/2.-contributor-and-annotator-guide/2.3-byo-key-copilot.md)                                 |
| Enterprise evaluation teams | [Bounty creation](/3.-enterprise-and-frontier-ai-labs/3.1-bounty-creation.md)                        | [Custom schemas](/3.-enterprise-and-frontier-ai-labs/3.2-custom-schemas.md), [verified dataloaders](/3.-enterprise-and-frontier-ai-labs/3.3-provenance-and-dataloaders.md)                                     |
| Validator operators         | [Structural gateway](/4.-the-4-stage-verification-engine/4.1-structural-gateway.md)                  | [Autonomous auditing](/4.-the-4-stage-verification-engine/4.3-autonomous-validator-agent.md), [settlement](/4.-the-4-stage-verification-engine/4.4-settlement-and-disbursement.md)                             |
| Contract integrators        | [Contract architecture](/5.-smart-contracts-and-arc-network-settlement/5.1-contract-architecture.md) | [Security and tests](/5.-smart-contracts-and-arc-network-settlement/5.3-security-and-test-suite.md), [deployment interfaces](/5.-smart-contracts-and-arc-network-settlement/5.4-deployments-and-interfaces.md) |
| Protocol analysts           | [Token and fair launch](/6.-protocol-economics-and-tokenomics/6.1-arcv-token-and-fair-launch.md)     | [Revenue engine](/6.-protocol-economics-and-tokenomics/6.2-protocol-revenue-engine.md), [treasury policy](/6.-protocol-economics-and-tokenomics/6.3-treasury-and-capital-allocation.md)                        |

## The protocol lifecycle

```
SOURCE                       VALIDATE                      ARCHIVE
Enterprise task payloads  ->  Human evaluation           ->  Canonical dataset bytes
Campaign specifications      Structural and quality checks  SHA-256 commitments
Native USDC escrow           Authorized acceptance          Arweave provenance
                             Contributor settlement          Verified retrieval
```

The application, off-chain verification services, settlement contract, and storage layer have distinct responsibilities. A successful transaction proves a state change under contract rules; it does not independently prove the truth of a model response. A matching digest proves byte integrity; it does not establish consent, ownership, or factual accuracy. The chapters explain these trust boundaries alongside each workflow.

## Documentation map

The complete reference contains **six sections and 21 chapters**:

1. [Overview & Protocol Fundamentals](/1.-overview-and-protocol-fundamentals/1.1-introduction.md) — mission, system architecture, and network parameters.
2. [Contributor & Annotator Guide](/2.-contributor-and-annotator-guide/2.1-workbench-overview.md) — evaluations, correction rewards, copilot privacy, and reputation design.
3. [Enterprise & Frontier AI Labs](/3.-enterprise-and-frontier-ai-labs/3.1-bounty-creation.md) — campaigns, JSON Schema, provenance checks, and training loaders.
4. [The 4-Stage Verification Engine](/4.-the-4-stage-verification-engine/4.1-structural-gateway.md) — structural validation, telemetry, model auditing, and settlement.
5. [Smart Contracts & Arc Network Settlement](/5.-smart-contracts-and-arc-network-settlement/5.1-contract-architecture.md) — authorization, replay defense, escrow invariants, tests, and interfaces.
6. [Protocol Economics & Tokenomics](/6.-protocol-economics-and-tokenomics/6.1-arcv-token-and-fair-launch.md) — launch policy, proposed revenue allocation, and bounty settlement accountability.

Use the [full table of contents](https://github.com/ArchiveDataSolutions/ArchiveARC/tree/main/docs/SUMMARY.md) to navigate every chapter.

## Implementation status and evidence

The documentation distinguishes implemented source behavior, frontend demonstrations, proposed specifications, and externally documented platform behavior. Review date: **6 October 2026**.

| Area                  | Evidence and boundary                                                                                                                                                              |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Settlement registry   | Native-value escrow, role-gated submission and payout, and persistent replay reservations exist in source. Local tests do not establish a production deployment.                   |
| Contract verification | 17 local tests pass; one fuzz test runs 256 cases. This is not formal verification or an independent audit.                                                                        |
| Fees and refunds      | The current registry pays the full configured reward. It has no fee split, cancellation, or refund function.                                                                       |
| Enterprise economics  | Section 6 specifies a proposed 10% gross settlement take-rate with equal treasury and buyback allocation. The existing frontend's 5% estimate is not enforcement of this proposal. |
| Token launch          | One-billion-token issuance and no private allocation are the ARCV launch policy. No ARCV-specific deployment or graduation is certified here.                                      |
| Copilot privacy       | The current browser implementation can persist credentials in local storage. Do not assume memory-only storage or provider-side zero retention.                                    |
| Application workflows | Simulated validation, wallet, escrow, and earnings displays are identified in the relevant chapters; they are not transaction receipts.                                            |

Use verified deployment records and compiled interfaces before moving funds. The implemented hash getter is `usedHashes(bytes32)`; `registeredHashes` and `cancelBounty` are not present in this registry version.

## Application workspaces

* [Enterprise console — SOURCE](https://arcv.network/enterprise)
* [Contributor workbench — VALIDATE](https://arcv.network/annotate)
* [Archive and network terminal — ARCHIVE](https://arcv.network/market)
* [Protocol website](https://arcv.network)

For chain-specific configuration, see [network parameters](/1.-overview-and-protocol-fundamentals/1.3-network-parameters.md). For exact byte verification before model ingestion, see [provenance and dataloaders](/3.-enterprise-and-frontier-ai-labs/3.3-provenance-and-dataloaders.md).

## Versioned documentation

These Markdown chapters are the source for `docs.arcv.network`. Changes are reviewed and saved as Git checkpoints so readers can distinguish a specification revision from a contract or application release. Public-chain examples and economic scenarios are labeled according to their evidence; illustrative balances are not protocol financial statements.

Publication to GitBook and domain configuration are separate operations. Completing this documentation source does not assert that the hosted documentation has been updated.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.arcv.network/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.