# Trust and verification

Deployed Works treats trust as separate signals, not one generic verified claim.

Audience: Buyers, providers, vendors and agents evaluating trust language.

Last updated: 2026-07-10

Canonical HTML: https://www.deployed.works/trust

Machine-readable: https://www.deployed.works/trust.md

## Trust principle

Trust signals help buyers understand evidence and risk. They do not guarantee skill, suitability, delivery quality or outcomes.

## Verification semantics

- Identity verified: An identity check may be completed through the configured verification provider.
- Organisation verified: Organisation context can be reviewed separately from individual identity where product surfaces support it.
- Billing verified: Billing access can indicate an active subscription or paid Deployment Slot; it is not proof of delivery quality.
- Capability evidence supplied: Profiles and listings can include proof, project examples, outcomes or supporting material.
- References checked: Reference checks may be used where available; absence of a reference check is not hidden.
- Credentials validated: Credentials can be reviewed where supplied and supported; validation should not be collapsed into a generic verified claim.
- Platform activity or history: Buyer-authored reviews, response history and deployment activity can be shown separately where available.
- Verification review or expiry: Verification status can be pending, failed, under review or expired; current status should be explicit.

## Independent matching

Vendors and providers cannot pay, sponsor or partner their way into better matching, Discovery ordering, fit, shortlist readiness or recommendations.