> 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/lv8r-labs/capabilities.md).

# Capability Overview

## Philosophy

> "The opposite of a data lake."

LV8R Labs doesn't aggregate data into a central repository. It orchestrates data across stakeholders who retain ownership of their records. Each participant contributes to and accesses the shared evidence chain without surrendering custody.

## Multi-Model AI Orchestration

LV8R Labs uses multiple AI models as a chorus of voices, not a single source of truth. A conductor doesn't play one instrument. An orchestrator doesn't run one service.

| Layer                        | What It Does                                                                                |
| ---------------------------- | ------------------------------------------------------------------------------------------- |
| **Prompt Engineering**       | Frame the question, get the answer. Works for simple tasks.                                 |
| **Context Engineering**      | Specify all steps necessary to reach the outcome. Move from a question to a workflow.       |
| **Organizational Alignment** | Ensure software alignment matches organizational goals — people, compliance, revenue model. |

{% hint style="warning" %}
When organizations skip Layer 3, they end up with powerful tools that create risk instead of reducing it.
{% endhint %}

## Evidence-Grade vs. Compliance-Grade

| Standard             | Survives                                                              | Doesn't Survive                    |
| -------------------- | --------------------------------------------------------------------- | ---------------------------------- |
| **Compliance-Grade** | Routine audit                                                         | Forensic scrutiny, legal discovery |
| **Evidence-Grade**   | Audit, legal discovery, insurance investigation, criminal prosecution | —                                  |

An evidence-grade record is cryptographically anchored at the moment of creation. It carries an immutable provenance chain: who created it, when, what they attested to, and who reviewed it.

> "The gap between these two standards is where buildings fail and people die."

→ [VDCO Model Guide](/lv8r-labs/guides/vdco.md) · [Published Articles — Golden Thread Series](/lv8r-labs/lv8r-labs/articles.md)

## Core Stack

* **PPCS (ProductionOS)** — Contractor ops: job board, tradesman credentialing, project pipeline from RFP to payment. [PPCS →](/lv8r-labs/lv8r-labs/ppcs.md)
* **MicroPay** — USDC & EURDC payment rails: Circle wallets, reconciliation, multi-chain settlement. [MicroPay →](/lv8r-labs/micropay/micropay.md)
* **LV8R Labs Stack** — Glue layer: asset tracking, IP management, compliance monitoring, multi-model AI orchestration.
* **tradesman-verify** — Multi-layer contractor verification for AI agents (OSS, MIT licensed). [tradesman-verify →](/lv8r-labs/lv8r-labs/tradesman-verify.md)
* **ClawHub** — Agent skill registry with behavioral testing and provenance pipeline. [ClawHub →](/lv8r-labs/lv8r-labs/clawhub.md)

## Architecture Principles

1. **Point-of-entry validation** — Verify at ingestion, not retroactively. [VDCO →](/lv8r-labs/guides/vdco.md)
2. **Decentralized identity** — W3C Verifiable Credentials on Accumulate ADI. [ADI Basics →](/lv8r-labs/guides/adi-basics.md)
3. **Multi-model orchestration** — No single-vendor lock-in.
4. **Proof-triggered settlement** — Cryptographic proofs trigger payment disbursement. [Settlement →](/lv8r-labs/shared/proof-settlement.md)
5. **Data sovereignty** — Stakeholders retain ownership; LV8R Labs orchestrates, never custodies.


---

# 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/lv8r-labs/capabilities.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.