> For the complete documentation index, see [llms.txt](https://tradesman.gitbook.io/lv8r-labs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tradesman.gitbook.io/lv8r-labs/guides/adi-basics.md).

# ADI Credential Basics

## What Is an ADI?

An **Accumulate Digital Identifier (ADI)** is a human-readable, self-sovereign identity on the [Accumulate Network](https://accumulatenetwork.io/). Unlike wallet addresses (long hex strings), ADIs look like URLs:

```
acc://example-org.acme
acc://example-org.acme/credentials/example-contractor-llc
```

## Why ADIs for Construction?

Construction has a credential fragmentation problem. A licensed plumber in Georgia verifies their identity for:

* Every new project
* Every new platform
* Every new payment processor
* Every new jurisdiction

Each system maintains its own copy of the contractor's credentials. None of them talk to each other. When a license expires, some systems catch it and some don't.

ADI credentials solve this by creating a single, portable, verifiable identity that the contractor owns and carries across every system.

## How It Works

```
Contractor → tradesman-verify → Verification passes → ADI credential issued
                                                            │
                          ┌─────────────────────────────────┤
                          │              │                   │
                        PPCS        BIMHeroDAO          MicroPay
                      Job board    Governance           Payment
                      access       participation        eligibility
```

1. **Verification** — [tradesman-verify](/lv8r-labs/lv8r-labs/tradesman-verify.md) checks business entity, trade license, and risk score
2. **Issuance** — passing verification triggers credential issuance on Accumulate
3. **Portability** — the credential works across PPCS, BIMHeroDAO, and MicroPay without re-verification
4. **Revocation** — if a license expires or is suspended, the credential is revoked across all systems simultaneously

## W3C Verifiable Credentials

ADI credentials follow the [W3C Verifiable Credentials](https://www.w3.org/TR/vc-data-model/) standard:

| Field          | What It Contains                                            |
| -------------- | ----------------------------------------------------------- |
| **Issuer**     | The entity that verified the contractor                     |
| **Subject**    | The contractor's ADI                                        |
| **Claims**     | Trade type, license number, jurisdiction, verification date |
| **Proof**      | Cryptographic signature anchored on Accumulate              |
| **Expiration** | Matches the underlying license expiration                   |

## Key Properties

| Property           | What It Means                                             |
| ------------------ | --------------------------------------------------------- |
| **Self-sovereign** | The contractor owns their credential, not any platform    |
| **Tamper-proof**   | Anchored on Accumulate — cannot be altered after issuance |
| **Human-readable** | ADI URLs, not hex addresses                               |
| **Revocable**      | Credential status checked in real time                    |
| **Cross-platform** | Works across the entire LV8R Labs + MicroPay stack        |

## Accumulate Network

Accumulate is the successor to the Factom protocol (DHS SVIP heritage, $789K public record). It provides:

* **Identity-first architecture** — ADIs are first-class objects, not afterthoughts
* **Sub-token accounting** — credential operations don't require expensive gas fees
* **Multi-chain anchoring** — Accumulate anchors to Bitcoin and Ethereum for additional security

Learn more: [accumulatenetwork.io](https://accumulatenetwork.io/)

→ [VDCO Model](/lv8r-labs/guides/vdco.md) · [Data Orchestration](/lv8r-labs/guides/data-orchestration.md) · [Capability Overview](/lv8r-labs/lv8r-labs/capabilities.md)


---

# 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://tradesman.gitbook.io/lv8r-labs/guides/adi-basics.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.