Skip to content

Proof story: Blue/Green UAS

How Valty organizes evidence for Blue and Green UAS readiness reviews.

This page describes the proof METHOD applied to the defense uncrewed aircraft systems regime: Blue and Green UAS designations, DCMA source-acceptance context, and AUVSI assessor findings. SAMPLE and illustrative only. Valty does not certify Green UAS, Blue UAS, or NDAA compliance. No specific customer is named. Specific cases are available under a readiness-package request.

Request the gated detail

Regime context: public

The Blue/Green UAS landscape and why supply-chain proof matters.

NDAA Section 848 and Section 880 restrict DoD procurement of certain UAS and associated components based on country of origin and manufacturer. Two primary designation tracks have emerged:

  • Blue UAS is the DoD-maintained Approved List of commercially available small UAS that have passed security review. Current list is public.
  • Green UAS is the AUVSI-administered Trusted List of UAS assessed by accredited third-party assessors. Tier levels vary by assessor and assessment scope.
  • DCMA source acceptance covers Defense Contract Management Agency administrative acceptance records that ground procurement eligibility in contracting documentation.

Regime descriptions above are based on publicly available DoD and AUVSI documentation. Valty does not determine or certify compliance status. It organizes and traces evidence so program teams and assessors can.

What this page does not claim

  • No named customer, supplier, or program office
  • No assertion that Valty substitutes for DCMA review or AUVSI assessment
  • No specific compliance result labeled as achieved
  • No guarantee that the Blue/Green designation lists are current; check DoD/AUVSI sources directly

Valty organizes evidence and traces proof chains. Compliance determinations are made by the relevant government authority or accredited assessor, not by Valty.

Before

Source state

Supplier and component provenance is unstructured

Before the proof workflow runs, UAS program teams typically hold supplier attestations, NDAA-compliance statements, and component declarations across disconnected spreadsheets and emails. Evidence exists but is not traceable to a claim.

Collect

Evidence intake

Evidence collected from supplier declarations and assessor findings

Valty ingests supplier-provided attestations, DCMA source-acceptance records, AUVSI-referenced assessor findings, and control mappings from 800-171 or 800-53 crosswalks. Each evidence object carries source, owner, and freshness.

Decide

Readiness decision

Readiness state ranked by evidence coverage and blocker severity

Gaps surface as claim blockers, not as pass/fail conclusions. The decision layer shows which control domains have covered evidence, which are inferred, and which are missing owner or freshness.

Export

Proof export

Proof artifact built for assessor, program office, or IC review

The export carries each claim with its evidence source, confidence tier, and publication state. Claims that cannot be supported are blocked before the pack leaves the platform.

Claim discipline: public vs gated

What Valty publishes here and what is behind a readiness-package request.

Every claim below carries its source, confidence, and freshness. Claims that require NDA, specific contract context, or named customer disclosure are gated.

Supplier attestation coverage
Source
Ingested from supplier-provided compliance declarations
Confidence
Evidence-backed; completeness is supplier-determined
Freshness
Requires current-cycle re-attestation; prior year stale
Blue UAS List crosswalk [public]
Source
DoD Approved List, public and DoD-maintained
Confidence
List state reflects DoD publication date; subject to revision
Freshness
Checked at time of engagement against current published list
Green UAS assessor tier mapping [public method]
Source
AUVSI Trusted List structure, a public framework
Confidence
Assessment currency depends on assessor recency and scope
Freshness
Current per most recent assessor engagement
Specific program office context [gated]
Source
Available under readiness-package request
Confidence
Disclosed under NDA after fit confirmation
Freshness
Reviewed before disclosure
Named supplier results [gated]
Source
Not published; engagement-specific
Confidence
Available to program teams and assessors with request context
Freshness
Current at time of request
Modeled loss exposure from a compliance gap [illustrative]
Source
FAIR-style model: method is public, inputs are engagement-specific
Confidence
Decision-support estimate; not a contract valuation or legal opinion
Freshness
Refreshed when source coverage or control state changes
UAS Proof Pack [illustrative] product surface
UAS Proof Pack [illustrative]Claim, evidence source, confidence tier, and export target for a defense-UAS readiness submission. Supplier names and specific results are gated.Open full-size product view ↗

Artifact anatomy [illustrative]

What the UAS proof pack contains when the workflow completes.

  • Supplier-level NDAA compliance posture with evidence source per claim
  • Blue/Green designation crosswalk with assessor tier and recency marker
  • DCMA source-acceptance reference chain where government records exist
  • 800-171 / 800-53 crosswalk for controls in scope of the assessment
  • Blocked-claim ledger listing claims that cannot export until evidence is provided
  • Financial exposure model with visible assumptions and confidence band

Artifact contents above are illustrative of what the Valty workflow produces in this regime. Actual outputs depend on source coverage, supplier participation, and engagement scope.

Request gated detailDesign-partner program

Proof matrix

What this page can and cannot claim

The proof matrix makes the public/gated boundary explicit. Every row carries source, confidence, and freshness. Gated rows are accessible via readiness-package request.

ClaimSourceConfidenceFreshness
NDAA compliance posture (§848/§880)Supplier attestations + component declarationsEvidence-backed; completeness depends on supplier coverageRequires current-cycle attestations; prior-year stale
Blue UAS designation contextDoD BLUE UAS Approved List (public)Public. List is DoD-maintained and subject to updateChecked against current published list at time of review
Green UAS designation contextAUVSI Trusted List / program-specific assessor findingsVaries by assessor tier and assessment recencyRequires current assessment cycle; prior assessments may be stale
DCMA source-acceptance evidenceDCMA administrative contracting officer recordsGovernment-issued; Valty normalizes, does not originateCurrent per accepted contract period
Financial exposure from compliance gapFAIR-style model with visible assumptions [illustrative]Decision-support estimate, not a contract valuationRefreshed when supplier coverage or control state changes
Named customer or specific resultGATED, not publishedAvailable under NDA via readiness-package requestReviewed before disclosure

Gated access

Program office teams and accredited assessors can request the full detail package.

The readiness-package request includes engagement scope, relevant source systems, and whether you are operating as a prime contractor, subcontractor, program office, or assessor. We will confirm disclosure scope before sharing specific supplier or program context.

Request readiness packageReview proof anatomy