# Documentation Cleanup Ledger

This ledger classifies documentation files by reader path and cleanup action. It exists to prevent accidental deletion of release evidence while still keeping the main documentation clean for customers, application developers, API reviewers, and future Showcase work.

## Cleanup Rule

| Rule | Meaning |
|---|---|
| Main path | Keep linked from audience entry points. These files are meant to be read directly. |
| Evidence path | Keep available for maintainers/release reviewers, but do not promote as beginner/user documentation. |
| Archive path | Historical proof, phase closure material, superseded preparation notes, or low-level audit notes. Preserve for traceability; keep out of the first reader path. |
| Delete candidate | Only delete after local links, release-pack links, claim-ledger references, package inclusion rules, and maintainer value have been checked. |

No file should be deleted only because it has an old phase number. Some phase files are the only evidence for a past quality or API decision.

## Documentation Cleanup Pass 1 Status

Status: Completed archival reorganization.

Documentation Cleanup Pass 1 moved historical proof notes from the top-level `docs/quality-proof/` folder into `docs/quality-proof/archive/`. The move keeps the evidence available while making the release-reader proof path much cleaner.

## Current Counts

| Area | Count | Current cleanup stance |
|---|---:|---|
| `docs/quality-proof/*.md` live proof files | 22 | Keep visible from [Quality proof guide](../quality-proof-guide.md) or as live release/product/recipe proof. |
| `docs/quality-proof/archive/*.md` archived files | 57 | Preserve for maintainer audit/history; do not promote as beginner or customer documentation. |
| Product-control live release/evidence pages | 5 | Keep as release reviewer evidence, not beginner documentation. |
| Recipe PASS proof pages | 2 | Keep in live proof path because they justify `Build-verified` recipe status. |
| Superseded recipe preparation notes | 3 | Archived because PASS proof pages supersede them. |
| `release-docs/*.md` files | 9 | Keep as a curated release reading pack, not source of truth. |

## Main Proof Pages

These files remain easy to find from [Quality proof guide](../quality-proof-guide.md):

| File | Reason |
|---|---|
| `quality-proof/quality-overview.md` | Main quality proof overview. |
| `quality-proof/render-verification.md` | Public Render Verification proof route. |
| `quality-proof/commercial-gate.md` | Commercial gate explanation. |
| `quality-proof/certification-orchestrator.md` | Internal certification/evidence orchestrator boundary. |
| `quality-proof/layout-size-contracts.md` | Layout and size proof boundary. |
| `quality-proof/theme-surface-governance.md` | Theme/surface governance proof boundary. |
| `quality-proof/localization-rtl-readiness.md` | Localization/RTL readiness proof boundary. |
| `quality-proof/data-virtualization-readiness.md` | Data/virtualization readiness proof boundary. |
| `quality-proof/output-route-readiness.md` | Output route readiness proof boundary. |
| `quality-proof/documentation-governance.md` | Documentation gate proof boundary. |
| `quality-proof/windows-validation.md` | Windows validation proof instructions. |
| `quality-proof/final-release-validation.md` | Final release validation boundary. |
| `quality-proof/release-build-and-package-proof.md` | Build/package proof boundary. |
| `quality-proof/approved-v1-public-surface-phase14.md` | V1 public API approval proof. |
| `quality-proof/windows-quality-run-2026-07-08.md` | Maintainer-reported Windows quality PASS record. |
| `quality-proof/recipe-build-verification-batch1-batch2-pass-2026-07-08.md` | Batch 1 + Batch 2 recipe Build-verified promotion proof. |
| `quality-proof/recipe-build-verification-batch3-pass-2026-07-08.md` | Batch 3 recipe Build-verified promotion proof. |

## Product-Control Evidence Pages

These files remain available for release reviewers and product-control maintainers:

| File | Reason |
|---|---|
| `quality-proof/product-controls-evidence-pack.md` | Product-control evidence pack. |
| `quality-proof/product-controls-final-commercial-readiness-closure.md` | Final commercial readiness closure. |
| `quality-proof/product-controls-production-gaps.md` | Known production gaps and closure tracking. |
| `quality-proof/product-controls-measured-runtime-benchmarks.md` | Measured runtime benchmark evidence. |
| `quality-proof/product-controls-benchmark-baseline-thresholds.md` | Benchmark threshold evidence. |

## Archived Files

These files were moved to `docs/quality-proof/archive/` during Documentation Cleanup Pass 1.

| Group | Files |
|---|---|
| Application/runtime phase notes | `application-controls-render-fault-policy-phase3.md`, `application-runtime-stress-proof-phase4.md`, `composition-root-shutdown-owner-quarantine-app06.md`, `input-wheel-and-facade-failure-app02-app03.md`, `motion-float-lifecycle-app01.md` |
| DPI/text phase notes | `dpi-textinput-paint-lifecycle-phase5.md`, `dpi-text-measurement-render-parity-phase6.md`, `dpi-text-shaping-fallback-performance-phase7.md`, `dpi-text-large-multiline-caret-policy-phase8.md` |
| Residual review notes | `datagrid-dataview-residual-review-phase12.md`, `diagnostics-quality-residual-review-phase13.md`, `localization-rtl-residual-review-phase14.md`, `virtualization-residual-review-phase15.md` |
| Motion implementation phases | `motion-system-phase16a-implementation.md`, `motion-system-phase16b-implementation.md`, `motion-system-phase17a-implementation.md`, `motion-system-phase17b-implementation.md`, `motion-system-phase17c-implementation.md`, `motion-system-phase18a-implementation.md`, `motion-system-phase18b-implementation.md`, `motion-system-final-lockdown.md` |
| Product-control scans and closures | `product-controls-dashboard-resize-host-sample-closure.md`, `product-controls-hosting-contracts.md`, `product-controls-keyboard-accessibility-stress.md`, `product-controls-masterdetail-splitview-closure.md`, `product-controls-phase0-baseline-lock.md`, `product-controls-provider-host-adoption-closure.md`, `product-controls-provider-state-closure.md`, `product-controls-public-api-freeze-audit.md`, `product-controls-public-api-review-ledger.md`, `product-controls-public-exposure-scan.md`, `product-controls-readiness-truth-scan.md`, `product-controls-release-blocker-scan.md`, `product-controls-release-freeze-lockdown.md`, `product-controls-routing-shell-boundary-closure.md`, `product-controls-source-boundary-scan.md`, `product-controls-strict-source-hygiene-scan.md` |
| Public API cleanup proof | `public-api-classification-baseline-phase9.md`, `public-api-cleanup-phase10.md`, `public-api-cleanup-phase11.md`, `public-surface-type-freeze-audit.md`, `post-rename-product-identity-audit.md` |
| Repo and virtualization proof notes | `repo-wide-exception-handling-scan.md`, `virtualization-accessible-range-proof.md`, `virtualization-consumer-behavior-proof.md`, `virtualization-consumer-diagnostics-strict-mode-proof.md`, `virtualization-datagrid-render-invalidation-proof.md`, `virtualization-large-data-windowing-catalog-coverage-proof.md`, `virtualization-large-data-windowing-catalog-proof.md`, `virtualization-listview-bounded-measurement-proof.md`, `virtualization-projection-scale-proof.md`, `virtualization-projection-scope-contract-proof.md`, `virtualization-tilebox-single-planning-proof.md` |
| Superseded recipe preparation notes | `recipe-build-verification-batch1-prep-2026-07-08.md`, `recipe-build-verification-batch2-prep-2026-07-08.md`, `recipe-build-verification-batch3-prep-2026-07-08.md` |

## Release Docs Boundary

`release-docs/` is a curated commercial reading pack. It is useful for release handoff, but it is not the documentation source of truth. The source of truth remains `docs/`, source code, project/package contracts, public/Friend boundaries, quality assets, and evidence inventories.

## Deletion Boundary

Documentation Cleanup Pass 1 did not delete historical proof files. It only moved them to an archive path and updated links. Deletion remains blocked until all of these checks pass:

1. Inbound Markdown links.
2. Claim-ledger references.
3. Release-pack and commercial handoff references.
4. `.nuspec` and package inclusion rules.
5. Maintainer audit value.