# Nexamas UI Quality Proof Guide

Nexamas UI documentation separates product claims from proof infrastructure. A capability may be public, internal proof infrastructure, or not available. The distinction matters for customer trust.

## Live proof path

The top-level `docs/quality-proof/` folder is the live proof path. It contains the proof pages that a release reviewer should read first.

### Main proof pages

- [Quality overview](quality-proof/quality-overview.md)
- [Render Verification](quality-proof/render-verification.md)
- [Commercial gate](quality-proof/commercial-gate.md)
- [Certification orchestrator](quality-proof/certification-orchestrator.md)
- [Layout and size contracts](quality-proof/layout-size-contracts.md)
- [Theme/surface governance](quality-proof/theme-surface-governance.md)
- [Localization/RTL readiness](quality-proof/localization-rtl-readiness.md)
- [Data virtualization readiness](quality-proof/data-virtualization-readiness.md)
- [Output route readiness](quality-proof/output-route-readiness.md)
- [Documentation governance](quality-proof/documentation-governance.md)
- [Approved V1 public surface](quality-proof/approved-v1-public-surface-phase14.md)

### Release validation pages

- [Windows validation proof](quality-proof/windows-validation.md) - explains the final Windows validation command, report artifacts, and claims allowed only after an actual run.
- [Windows quality run — 2026-07-08](quality-proof/windows-quality-run-2026-07-08.md) - records the maintainer-reported `Passed: 15, Skipped: 0, Failed: 0` quality result for this documentation pass.
- [Final release validation](quality-proof/final-release-validation.md)
- [Release build and package proof](quality-proof/release-build-and-package-proof.md)

### Product-control release evidence

- [Product-control evidence pack](quality-proof/product-controls-evidence-pack.md)
- [Product-control final commercial readiness closure](quality-proof/product-controls-final-commercial-readiness-closure.md)
- [Product-control production gaps](quality-proof/product-controls-production-gaps.md)
- [Product-control measured runtime benchmarks](quality-proof/product-controls-measured-runtime-benchmarks.md)
- [Product-control benchmark baseline thresholds](quality-proof/product-controls-benchmark-baseline-thresholds.md)

### Recipe build verification

- [Recipe build-verification Batch 1 + Batch 2 Windows PASS — 2026-07-08](quality-proof/recipe-build-verification-batch1-batch2-pass-2026-07-08.md) - records maintainer-reported `196 Warning(s), 0 Error(s)` recipe sample build plus `Passed: 15, Skipped: 0, Failed: 0` full quality gate, promoting covered recipes to `Build-verified`.
- [Recipe build-verification Batch 3 Windows PASS — 2026-07-08](quality-proof/recipe-build-verification-batch3-pass-2026-07-08.md) - records maintainer-reported Batch 3 sample PASS plus `Passed: 15, Skipped: 0, Failed: 0` full quality gate, promoting theme/surface, RTL, Output, and large-data boundary recipes to `Build-verified`.
- [Documentation Recipes Windows PASS — 2026-07-10](quality-proof/documentation-recipes-windows-pass-2026-07-10.md) - closes all five batches: 41 / 41 governed recipes Build-verified, 5 / 5 runtime smokes PASS, and Render Verification snapshot smoke PASS.

## Historical proof archive

Historical phase notes, targeted closure scans, residual reviews, public API cleanup notes, virtualization micro-proofs, and superseded recipe preparation notes were moved out of the live proof path during Documentation Cleanup Pass 1.

Start here when old audit context is needed:

- [Quality proof archive](quality-proof/archive/README.md)

Archived files remain part of release history. They are not beginner documentation and should not be deleted unless claim-ledger references, release documentation, and package documentation boundaries have been checked.

## What this proves

The documentation proves the existence and boundaries of quality infrastructure through source inspection and inventories. It does not claim current release PASS unless the appropriate Windows/PowerShell/MSBuild quality gates are actually executed for that release.

## Required release validation outside this pass

The documentation recipe workstream has Windows proof. Full product release still requires the normal build/package/packed-consumer quality gates on Windows; recipe proof does not replace package release proof.

## Documentation cleanup boundary

Use the [Documentation cleanup ledger](_inventory/documentation-cleanup-ledger.md) before moving or deleting proof files. The Showcase is a demonstration surface, not proof authority.

- [API Reference Batch 1 Application source pass](quality-proof/api-reference-batch1-application-source-pass-2026-07-08.md)
- [API Reference Batch 2 Controls and Components source pass](quality-proof/api-reference-batch2-controls-components-source-pass-2026-07-08.md)
- [API Reference Batch 3 Systems, Evidence, and Compatibility source pass](quality-proof/api-reference-batch3-systems-evidence-compat-source-pass-2026-07-08.md)