> 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/vdco.md).

# VDCO Model

## Virtual Design, Construct, and Operate

The VDCO model extends the traditional design-build lifecycle into a continuous digital loop. Instead of handing over a building and walking away, the data infrastructure persists from design through operations — and through ownership transitions.

## The Three Phases

### 1. Virtual Design

| Activity               | Data Output                              | Who Owns It         |
| ---------------------- | ---------------------------------------- | ------------------- |
| Architectural modeling | BIM model, specifications                | Architect           |
| Structural engineering | Loading calculations, material specs     | Structural engineer |
| MEP design             | Mechanical, electrical, plumbing layouts | MEP engineer        |
| Permit applications    | Submission documents, approval records   | Owner / architect   |

In the VDCO model, each design artifact is anchored at creation with an ADI attestation. The architect doesn't just produce a BIM model — they produce a verified BIM model with provenance.

### 2. Construct

| Activity             | Data Output                                  | Who Owns It   |
| -------------------- | -------------------------------------------- | ------------- |
| Material delivery    | Certificates of origin, quality reports      | Supplier / GC |
| Inspections          | Inspection reports, photos, sign-offs        | Inspector     |
| Change orders        | Scope modifications, cost impacts, approvals | GC / owner    |
| Milestone completion | Completion evidence, payment triggers        | GC / PM       |

Construction is where data volume explodes. A mid-rise residential project generates thousands of records. The VDCO model captures them at the point of creation — not retroactively from memory.

### 3. Operate

| Activity            | Data Output                                 | Who Owns It      |
| ------------------- | ------------------------------------------- | ---------------- |
| Building management | Sensor data, maintenance logs, energy usage | Building manager |
| Tenant management   | Lease records, occupancy data               | Property manager |
| Insurance           | Risk assessments, claims history            | Insurer          |
| Compliance          | Regulatory filings, safety inspections      | Owner            |

The operate phase is where the golden thread pays dividends. Every maintenance event, every inspection, every ownership transition adds to the evidence chain — it never starts over.

## The Full Loop

```
Design ──→ Construct ──→ Operate ──→ Renovate ──→ Operate ──→ Transfer
  │            │            │            │            │            │
  └────────────┴────────────┴────────────┴────────────┴────────────┘
                    Continuous Evidence Chain (ADI)
```

Traditional handoffs break the data chain. The architect's BIM model doesn't connect to the contractor's project management system. The contractor's records don't flow to the building operator. The operator's maintenance logs don't reach the next owner.

VDCO eliminates these breaks. The evidence chain is continuous from first design decision to final demolition.

## Three-Stage Tokenization

The VDCO model aligns with a three-stage adoption path for real estate tokenization:

| Stage                  | What It Means                                                 | Example                                              |
| ---------------------- | ------------------------------------------------------------- | ---------------------------------------------------- |
| **Digital Twin**       | Physical asset represented digitally                          | BIM model of an existing building                    |
| **Digitally Enhanced** | Digital representation adds value to physical asset           | Verified maintenance history increases resale value  |
| **Digitally Native**   | Asset exists primarily as digital-first with physical backing | Tokenized real estate with evidence-grade provenance |

Most tokenization projects jump straight to stage 3 without building stages 1 and 2. The RealT/Detroit lawsuit demonstrates what happens when tokenization is applied to the transaction layer without the trust layer.

## Standards Alignment

| Standard                       | Role in VDCO                                                |
| ------------------------------ | ----------------------------------------------------------- |
| **ISO 19650**                  | BIM lifecycle management framework                          |
| **UK Building Safety Act**     | Mandates tamper-resistant records for higher-risk buildings |
| **NIST IR 8536**               | Supply chain traceability at point of event capture         |
| **W3C Verifiable Credentials** | Portable, tamper-proof attestations                         |

→ [ADI Credential Basics](/lv8r-labs/guides/adi-basics.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/vdco.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.