# Documentation Status ## Current pass Phase 27 closes the six-stage user-documentation truth audit. The project/source boundary remains aligned at **2,864 compiled VB files**, the assembly-derived public surface remains frozen at **302 consumer-visible CLR types and 4,482 consumer-visible members**, and all **302 / 302** types have both API-reference and contextual user documentation. Documentation-to-code mismatches and reverse-coverage gaps are at zero. All **41 / 41** governed recipes built on Windows and all five batch runtime smokes passed; the Render Verification snapshot smoke also passed. See `docs/_inventory/phase6-user-documentation-closure.md`, `docs/_inventory/phase5-documentation-build-runtime-audit.md`, and `docs/quality-proof/documentation-recipes-windows-pass-2026-07-10.md`. Phase 0 established documentation governance and source-derived inventories. Phase 1 added source-verified Application/Window/Composition documentation. Phase 2 added Component System inventory. Phase 3 added Layout / Size / Responsive documentation. Phase 4 added Theme / Surface / Visual documentation. Phase 5 added Localization / RTL documentation. Phase 6 added Data / DataGrid / Virtualization documentation. Phase 7 added Output System documentation. Phase 8 added Quality / Verification documentation. Phase 9 added Commercial Adoption documentation. Phase 10 added Documentation Governance / Consistency Gate. Phase 11 closed the Documentation Center and release-docs pack. Phase 12 added public API copy-paste examples. Phase 13 added a Windows validation runner and final validation runbook. Phase 14 added practical Core Documentation pages for application, layout, controls, theme, data, localization, motion, diagnostics, and packaging. Phase 15 split beginner user documentation from maintainer governance documentation and corrected the Output beginner boundary. Phase 16 recorded the maintainer-reported Windows quality PASS and added recipe build-verification governance before Showcase implementation. Phase 17 prepared the Batch 1 recipe verification consumer sample and documented its Windows build command without promoting any recipe to Build-verified yet. Phase 18 prepared the Batch 2 recipe verification consumer sample for feedback, navigation, surfaces, input choices, and DataGrid basic rows. Phase 19 recorded maintainer-reported Windows recipe sample build `196 Warning(s), 0 Error(s)` plus full quality gate `Passed: 15, Skipped: 0, Failed: 0`, promoting Batch 1 and Batch 2 covered recipes to Build-verified while keeping them blocked from Showcase-ready until live scenes and code panels exist. Phase 20 prepared the Batch 3 recipe verification consumer sample for theme/surface, Localization/RTL, Output, and DataGrid large-data boundary recipes without promoting them to Build-verified yet. Phase 21 recorded maintainer-reported Windows Batch 3 sample PASS plus full quality gate `Passed: 15, Skipped: 0, Failed: 0`, promoting Batch 3 covered recipes to Build-verified while keeping them blocked from Showcase-ready until live scenes and code panels exist. Phase 22 performed Documentation Cleanup Pass 1 by moving historical proof notes and superseded preparation records into `docs/quality-proof/archive/` while keeping live release, product, API, and recipe PASS proof in the top-level proof path. Phase 23 added the first full API Reference documentation batch for `Nexamas.UI.Application` and locked the full public API scope at 296 public type records for batch completion tracking. Phase 24 added API Reference Batch 2 for controls, components, component models, event payloads, snapshots, and DropDownMenu records, documenting 172 additional public type records. Phase 25 added API Reference Batch 3 for the remaining systems/evidence/compatibility namespaces, documenting 53 records and completing source-documented type coverage for all 296 current public type records. ## Completed documentation areas - Documentation Center root created. - Code-first documentation policy created. - Source-of-truth policy created. - Project/package inventory created from `Nexamas.UI.vbproj` and `Nexamas.UI.nuspec`. - System inventory created from source roots. - Public surface inventory created from public type declarations. - Gateway/facade inventory created from known facade/gateway source files. - Application control factory inventory created from public `Add*` methods. - Initial claim ledger created. - Application/Window/Composition inventory created from `MASSystem/Application` source and `Nexamas.UI.vbproj` compile includes. - Product/adoption/reference/developer pages added for the public Application model. - Application boundary policy expanded: public facades documented, Friend/internal host hooks excluded from consumer docs. - Component System, Layout/Size, Theme/Surface, Localization/RTL, Data/DataGrid/Virtualization, Output System, Quality/Verification, Commercial Adoption, Documentation Governance, Docs Center Closure, and public developer examples added through Phase 12. ## Remaining boundaries - The six-stage documentation truth audit is complete, but no finite documentation audit proves every possible runtime state for all 4,482 consumer-visible members. Behavioral claims remain bounded by their source, quality-gate, recipe, or runtime evidence. - `Build-verified` and runtime-smoke proof do not automatically mean `Showcase-ready`; Showcase readiness still requires a live scene plus a matching code panel linked to the recipe ID. - Historical phase notes below preserve the chronology of earlier preparation and Linux-only limitations. Current closure status is controlled by the Phase 6 report and the durable Windows proof records. ## Validation note Static source/project/package inspection was executed in the audit environment. Platform-specific recipe validation was then executed on Windows/.NET Framework 4.8: five projects built, five runtime smokes passed, and the Render Verification snapshot smoke passed with exit code `0`. ## Phase 19 — Batch 1 + Batch 2 Recipe Build Verification Status: Maintainer-reported Windows Build-verified promotion recorded. Created/updated: - `docs/quality-proof/recipe-build-verification-batch1-batch2-pass-2026-07-08.md` - `docs/recipes/build-verification-ledger.md` - `docs/recipes/showcase-snippet-map.md` - `docs/quality-proof-guide.md` - `docs/maintainer/README.md` - `samples/README.md` - `samples/RecipeVerification.Batch1/README.md` - `samples/RecipeVerification.Batch2/README.md` Reported Windows facts: - Recipe sample build: `196 Warning(s), 0 Error(s)` - Full quality gate: `Passed: 15, Skipped: 0, Failed: 0` - Batch 1 covered recipes promoted to `Build-verified`: 8 - Batch 2 covered recipes promoted to `Build-verified`: 16 - Total newly Build-verified recipes: 24 Boundary: - `Build-verified` means the documented public usage path compiled in the prepared consumer sample path. - It does not mean `Showcase-ready`. - Showcase-ready still requires a live Showcase scene plus a matching code panel linked to the recipe ID. ## Phase 20 — Batch 3 Recipe Build Verification Preparation Status: Prepared first, then superseded by Phase 21 Windows PASS. Created/updated: - `samples/RecipeVerification.Batch3/README.md` - `samples/RecipeVerification.Batch3/MainForm.vb` - `samples/RecipeVerification.Batch3/Nexamas.UI.RecipeVerification.Batch3.vbproj` - `docs/quality-proof/archive/recipe-build-verification-batch3-prep-2026-07-08.md` - `docs/recipes/build-verification-ledger.md` - `docs/recipes/showcase-snippet-map.md` - `samples/README.md` - `docs/index.md` - `docs/maintainer/quality-gates.md` - `docs/maintainer/release-process.md` - `tools/quality/Run-NexamasUIQuality.ps1` - `eng/ci/Clean-NexamasUIReleaseWorkspace.ps1` Covered recipe IDs: - `Theme.Surface.Apply` - `Theme.Surface.Options` - `Localization.Rtl.AttachPage` - `Localization.Rtl.AttachSection` - `Output.VisualCapture` - `Output.CapabilityCatalog` - `Output.Manifest` - `DataGrid.LargeData.Boundary` Boundary: - These recipes were promoted to `Build-verified` after the maintainer-reported Windows Batch 3 PASS recorded in Phase 21. - The sample is not a Showcase scene and does not make any recipe `Showcase-ready`. - No Linux sandbox compile was executed because this project requires Windows/.NET Framework 4.8 build tools. ## Phase 21 — Batch 3 Recipe Build Verification PASS Status: Maintainer-reported Windows Build-verified promotion recorded. Created/updated: - `docs/quality-proof/recipe-build-verification-batch3-pass-2026-07-08.md` - `docs/quality-proof/archive/recipe-build-verification-batch3-prep-2026-07-08.md` - `docs/recipes/build-verification-ledger.md` - `docs/recipes/showcase-snippet-map.md` - `docs/quality-proof-guide.md` - `docs/maintainer/README.md` - `samples/README.md` - `samples/RecipeVerification.Batch3/README.md` - `docs/index.md` Reported Windows facts: - Batch 3 sample build: maintainer-reported PASS; no blocking build error reported for Batch 3. - Full quality gate: `Passed: 15, Skipped: 0, Failed: 0` - Batch 3 covered recipes promoted to `Build-verified`: 8 Boundary: - `Build-verified` means the documented public usage path compiled in the prepared consumer sample path. - It does not mean `Showcase-ready`. - Showcase-ready still requires a live Showcase scene plus a matching code panel linked to the recipe ID. - No Linux sandbox compile was executed because this project requires Windows/.NET Framework 4.8 build tools. ## Phase 22 — Documentation Cleanup Pass 1 Status: Completed archival reorganization. Created/updated: - `docs/quality-proof/archive/README.md` - `docs/quality-proof/archive/*.md` - `docs/quality-proof-guide.md` - `docs/_inventory/documentation-cleanup-ledger.md` - `docs/_inventory/documentation-status.md` - `docs/index.md` - `docs/README.md` Moved to archive: - Historical Application/runtime phase notes. - DPI/text phase notes. - Residual review notes. - Motion implementation phase notes. - Product-control targeted closure scans and release-hardening notes. - Public API cleanup proof notes. - Repo-wide and virtualization micro-proof notes. - Superseded recipe preparation proof notes for Batch 1, Batch 2, and Batch 3. Kept in live proof path: - Main proof overview pages. - Windows validation and release package proof pages. - Product-control release evidence pages. - Approved V1 public surface proof. - Recipe Batch 1 + Batch 2 PASS proof. - Recipe Batch 3 PASS proof. Boundary: - This phase is a documentation organization pass only. - It does not delete historical proof evidence. - It does not change public API, product source, build scripts, package identity, or recipe verification status. - The archived files remain available for maintainer audit and claim traceability but are no longer part of the first proof-reader path. - No Windows/.NET Framework 4.8 build was executed in this Linux sandbox. ## Phase 2 — Component System Inventory Status: Completed static source-verified documentation pass. Created/updated: - `docs/_inventory/component-system-inventory.md` - `docs/_inventory/component-factory-inventory.md` - `docs/product/component-system.md` - `docs/adoption/component-adoption-boundary.md` - `docs/reference/component-factory-surface.md` - `docs/developer/controls-overview.md` - `docs/_inventory/claim-ledger.md` - `docs/README.md` Verified static facts: - `Component/**/*.vb` files on disk: 1187 - `Component/` compile includes in `Nexamas.UI.vbproj`: 1187 - Missing component compile includes: 0 - Compile includes pointing to missing component files: 0 - Public component factory methods: 76 - Unique component factory return types: 75 - Built-in architecture descriptors found: 108 - Factory return types without descriptor: 0 Limitations: - No full Windows/MSBuild/.NET Framework 4.8 build was executed in this Linux sandbox. - Per-control behavior/render/layout/theme/RTL verification is intentionally deferred. ## Phase 3 — Layout / Size / Responsive System Status: Completed static source-verified documentation pass. Created/updated: - `docs/_inventory/layout-size-responsive-inventory.md` - `docs/product/layout-system.md` - `docs/adoption/layout-size-adoption-boundary.md` - `docs/reference/layout-size-surface.md` - `docs/developer/layout-and-sizing.md` - `docs/quality-proof/layout-size-contracts.md` - `docs/_inventory/claim-ledger.md` - `docs/README.md` Verified static facts: - `MASSystem/Layout/**/*.vb` files on disk: 157 - `MASSystem/Layout/` compile includes in `Nexamas.UI.vbproj`: 157 - Missing Layout compile includes: 0 - Compile includes pointing to missing Layout files: 0 - `MASSystem/Layout/SizeLayoutSystem/**/*.vb` files: 65, all included - `MASSystem/Layout/Composition/**/*.vb` files: 50, all included - Unique public layout/size-related types found in the inspected scope: 31 - Component files containing public `WithSize(MASSize)`: 79 - Component files participating in intrinsic-size contract measurement: 119 - Component files referencing responsive profile/resolver infrastructure: 72 Consumer-facing routes documented: - `MASApplication.Sizing` - `MASApplicationWindow.Sizing` - `MASApplicationWindow.Geometry` - `MASApplicationWindow.Controls.LayoutPage(...)` - `MASApplicationWindow.Controls.LayoutApplicationSurface(...)` Explicitly excluded from normal consumer docs: - `LayoutRegions(...)` because it is `Friend` - internal layout engines - responsive resolver/profile internals - diagnostics/audit report classes - token resolver internals Limitations: - No full Windows/MSBuild/.NET Framework 4.8 build was executed in this Linux sandbox. - Size/Layout audit infrastructure was confirmed by source inspection, but the gates were not executed here. - Per-control responsive behavior remains deferred to later targeted control/system verification. ## Phase 4 — Theme / Surface / Visual System Status: Completed static source-verified documentation pass. Created/updated: - `docs/_inventory/theme-surface-visual-inventory.md` - `docs/product/theme-surface-system.md` - `docs/adoption/theme-surface-adoption-boundary.md` - `docs/reference/theme-surface-surface.md` - `docs/developer/theme-and-surfaces.md` - `docs/quality-proof/theme-surface-governance.md` - `docs/_inventory/claim-ledger.md` - `docs/README.md` Verified static facts: - `MASSystem/Visual/**/*.vb` files on disk: 455 - `MASSystem/Visual/` compile includes in `Nexamas.UI.vbproj`: 455 - Missing Visual compile includes: 0 - Compile includes pointing to missing Visual files: 0 - `MASSystem/Visual/ThemeSystem/**/*.vb` files: 218, all included - `MASSystem/Visual/Surface/**/*.vb` files: 122, all included - `MASSystem/Visual/ThemeStudioSystem/**/*.vb` files: 19, all included - `Component/Tokens/**/*.vb` files: 82, all included - `Component/Surfaces/**/*.vb` files: 23, all included - Public app theme facades verified: `MASApplicationTheme`, `MASApplicationWindowTheme` - Public theme identity contract verified: `IMASAppTheme` - Built-in MASSignature themes verified: 3 - Public-selectable material definitions observed in registry: 14 - Public surface-material gateway/scope verified through Application facade Consumer-facing routes documented: - `MASApplication.Theme` - `MASApplicationWindow.Theme` - `MASApplicationSurfaceMaterialGateway.GetSelectableMaterials()` - `MASApplicationSurfaceMaterialGateway.CreateScope(window)` - `MASApplicationSurfaceMaterialScope.Apply(materialKey)` - `MASApplicationWindow.SurfaceMaterial` / `WithSurfaceMaterial(...)` - supported public `SurfaceMaterial` / `WithSurfaceMaterial` component gateways Explicitly excluded from normal consumer docs: - `ThemeManager` - `ThemeHost` - `ThemeAssembly` - `ThemeValidator` - deep foundation/family recipe contracts - `MASThemeStudio` and `MASSurfaceDesigner` because they are `Friend` - material registries, renderers, frame painters, runtime routing internals - visual governance/audit report classes Caution: - DG-07 source update: `MASPublicSurfaceMaterialGatewayManifestGate` now verifies that manifest entry count, expected count, ready count, required members, duplicate protection, and reflected public members agree. Documentation still treats this as pending Windows quality proof until the normal gate run is executed. Limitations: - No full Windows/MSBuild/.NET Framework 4.8 build was executed in this Linux sandbox. - Visual/theme/surface governance infrastructure was confirmed by source inspection, but the gates were not executed here. ## Phase 5 — Localization / RTL Status: Completed static source-verified documentation pass. Created/updated: - `docs/_inventory/localization-rtl-inventory.md` - `docs/product/localization-rtl-system.md` - `docs/adoption/localization-rtl-adoption-boundary.md` - `docs/reference/localization-rtl-surface.md` - `docs/developer/localization-and-rtl.md` - `docs/quality-proof/localization-rtl-readiness.md` - `docs/_inventory/claim-ledger.md` - `docs/README.md` Verified static facts: - `MASSystem/Localization/**/*.vb` files on disk: 20 - `MASSystem/Localization/` compile includes in `Nexamas.UI.vbproj`: 20 - Missing Localization compile includes: 0 - Compile includes pointing to missing Localization files: 0 - `Contracts/` files: 8, all included - `Gateway/` files: 2, all included - `Internal/` files: 4, all included - `Gate/` files: 5, all included - `Dashboard/` files: 1, included - Public Localization namespace type observed: `MASLocalizationRtl` - Public Localization gateway methods observed: 2 overloads of `AttachPage` - Product culture profiles observed: `en-US`, `de-DE`, `ar-SY` - Product string sample keys observed: 5 - Expansion samples implied by source: 10 Consumer-facing route documented: - `MASLocalizationRtl.AttachPage(window)` - `MASLocalizationRtl.AttachPage(window, page)` Explicitly excluded from normal consumer docs: - `MASLocalization` because it is `Friend` - snapshot/culture/string/format/expansion contract classes because they are `Friend` - readiness and runtime ownership report classes because they are `Friend` - catalog builders and internal product page implementation - public-translation/resource-engine claims not supported by the current public surface Limitations: - No full Windows/MSBuild/.NET Framework 4.8 build was executed in this Linux sandbox. - Localization readiness and runtime ownership infrastructure was confirmed by source inspection, but the gates were not executed here. - Per-control RTL behavior remains outside this phase and should be handled by targeted control/layout/render verification. ## Phase 6 — Data / DataGrid / Virtualization Status: Completed static source-verified documentation pass. Created/updated: - `docs/_inventory/data-virtualization-inventory.md` - `docs/product/data-grid-virtualization-system.md` - `docs/adoption/data-virtualization-adoption-boundary.md` - `docs/reference/data-component-surface.md` - `docs/developer/data-grid-and-data-view.md` - `docs/quality-proof/data-virtualization-readiness.md` - `docs/_inventory/claim-ledger.md` - `docs/_inventory/official-gateway-inventory.md` - `docs/reference/public-api-surface.md` - `docs/README.md` Verified static facts: - `MASSystem/Data/**/*.vb` files on disk: 33 - `MASSystem/Data/` compile includes in `Nexamas.UI.vbproj`: 33 - Missing Data compile includes: 0 - Compile includes pointing to missing Data files: 0 - `Component/Data/**/*.vb` files on disk: 165 - `Component/Data/` compile includes in `Nexamas.UI.vbproj`: 165 - Missing Component/Data compile includes: 0 - Compile includes pointing to missing Component/Data files: 0 - `MASSystem/Layout/VirtualizationSystem/**/*.vb` files on disk: 42 - VirtualizationSystem compile includes: 42 - Missing VirtualizationSystem compile includes: 0 - Compile includes pointing to missing VirtualizationSystem files: 0 - Public data factory methods in `MASApplicationWindowControls.ControlFactory.Data.vb`: 15 - Data factory return types with architecture descriptors: 15 / 15 - Unique public types observed under `Component/Data`: 22 - `MASSystem/Data` declarations observed as public consumer API: 0 - `MASSystem/Layout/VirtualizationSystem` declarations observed as public consumer API: 0 Consumer-facing routes documented: - `MASApplicationWindow.Controls.AddDataGrid(...)` - data/navigation visualization `Add*` factories in `MASApplicationWindowControls.ControlFactory.Data.vb` - `MASDataGrid` - `MASDataView` - `MASDataGridColumn` - `MASDataGridRow` - `MASDataGridSelectionMode` - `MASDataGridSortDirection` - DataGrid cell editing event/address types Explicitly excluded from normal consumer docs: - `MASSystem/Data/*` foundation classes because they are `Friend` - `MASSystem/Layout/VirtualizationSystem/*` because it is `Friend` - `MASDataGridVirtualizationCoordinator` - DataGrid diagnostics/governance/render-verification contribution classes - virtualization benchmark/gate/report classes Limitations: - No full Windows/MSBuild/.NET Framework 4.8 build was executed in this Linux sandbox. - DataGrid and virtualization proof infrastructure was confirmed by source inspection, but the gates were not executed here. - Detailed behavior documentation for every data-adjacent control remains deferred to targeted control-specific passes. ## Phase 7 — Output System Status: Completed static source-verified documentation pass. Created/updated: - `docs/_inventory/output-system-inventory.md` - `docs/product/output-system.md` - `docs/adoption/output-adoption-boundary.md` - `docs/reference/output-surface.md` - `docs/developer/output.md` - `docs/quality-proof/output-route-readiness.md` - `docs/output/OUTPUT_PRODUCT_API.md` - `docs/_inventory/claim-ledger.md` - `docs/_inventory/official-gateway-inventory.md` - `docs/reference/public-api-surface.md` - `docs/README.md` Verified static facts: - `MASSystem/Output/**/*.vb` files on disk: 38 - `MASSystem/Output/` compile includes in `Nexamas.UI.vbproj`: 38 - Missing Output compile includes: 0 - Compile includes pointing to missing Output files: 0 - `MASSystem/Application/Facade/Output/**/*.vb` files on disk: 2 - Application Output facade compile includes: 2 - Public `MASApplicationOutput` methods observed: 13 - Public Output contract types observed: 13 - Declared Output capabilities observed: 12 - Supported Output capabilities observed: 10 - Deliberately `NotAvailable` capabilities observed: 2 (`PdfDocument/Pdf`, `PrintJob/Printer`) - Output target kinds observed: Memory, File, Directory Consumer-facing routes documented: - `MASApplication.Output` - `MASApplicationOutput` - `MASOutputCapabilityCatalog` - `MASOutputCapability` - `MASOutputReadinessSnapshot` - `MASOutputRequest` - `MASOutputResult` - `MASOutputTarget` - `MASOutputOptions` - Output artifact/format/status/target/failure enum contracts Explicitly excluded from normal consumer docs: - `MASApplicationOutputGateway` - `MASOutputProductRuntime` - Chart/Visualization foundation classes - Report/Print foundation classes - Output governance audit classes - production PDF export claims - production OS printing claims Limitations: - No full Windows/MSBuild/.NET Framework 4.8 build was executed in this Linux sandbox. - Output governance infrastructure was confirmed by source inspection, but the audit/gates were not executed here. - Visual capture is documented as a governed Render Verification artifact route, not as a generic screenshot framework. ## Phase 8 — Quality / Verification / Commercial Proof Status: Completed static source-verified documentation pass. Created/updated: - `docs/_inventory/quality-verification-inventory.md` - `docs/product/quality-verification-system.md` - `docs/adoption/quality-commercial-proof-boundary.md` - `docs/reference/quality-verification-surface.md` - `docs/developer/render-verification.md` - `docs/quality-proof/quality-overview.md` - `docs/quality-proof/render-verification.md` - `docs/quality-proof/commercial-gate.md` - `docs/quality-proof/certification-orchestrator.md` - `docs/_inventory/claim-ledger.md` - `docs/_inventory/official-gateway-inventory.md` - `docs/reference/public-api-surface.md` - `docs/README.md` Verified static facts: - `MASSystem/Quality/**/*.vb` files on disk: 127 - `MASSystem/Quality/` compile includes in `Nexamas.UI.vbproj`: 127 - Missing Quality compile includes: 0 - Compile includes pointing to missing Quality files: 0 - Render Verification source files: 67 - Performance System source files: 31 - Certification System source files: 20 - Diagnostics Dashboard source files: 9 - Public quality/verification types under `MASSystem/Quality`: 5 - Friend/internal quality types under `MASSystem/Quality`: 130 - Required assets declared by `Nexamas.UI.QualityManifest.json`: 15 - Missing required assets in this static pass: 0 - Orchestrated quality gates declared by the manifest: 17 - Official quality runner script references verified present: 10 step references Consumer-facing routes documented: - `MASRenderVerification.CreateSnapshot(...)` - `MASRenderVerification.AttachDashboard(window, ...)` - `MASRenderVerification.AttachDashboard(window, page, ...)` - `MASRenderVerificationSnapshot` - `MASRenderVerificationEntry` - `MASRenderVerificationProgressInfo` - `MASRenderVerificationOutcome` Explicitly excluded from normal consumer docs: - `MASQualityOrchestrator` - `NexamasUICertification` - `MASDiagnosticsDashboard` - `MASPerformanceSystem` - `MASRenderVerificationRunner` - `MASRenderVerificationTargetCatalog` - `MASRenderBaselineStore` - `MASRenderVerificationGate` - Commercial Gate PASS claims without an actual run report - screenshot/baseline approval claims without generated proof artifacts Limitations: - No full Windows/MSBuild/.NET Framework 4.8 build was executed in this Linux sandbox. - The official quality runner, commercial gate, runtime harness, startup probe, performance smoke, pack, packed consumer proof, and Render Verification capture were not executed here. - This phase verifies quality/proof infrastructure and documentation boundaries, not current release readiness status. ## Phase 9 — Commercial Adoption / Product Packaging Status: Completed static source-verified documentation pass. Created/updated: - `docs/_inventory/commercial-adoption-inventory.md` - `docs/commercial/product-brief.md` - `docs/commercial/commercial-adoption-guide.md` - `docs/commercial/what-is-included.md` - `docs/commercial/subscription-readiness.md` - `docs/commercial/licensing-and-delivery-boundary.md` - `docs/commercial/company-evaluation-guide.md` - `docs/commercial/stability-and-roadmap-boundary.md` - `docs/_inventory/claim-ledger.md` - `docs/README.md` Verified static facts: - Root proprietary commercial SDK license file exists: `LICENSE.md` - Third-party notices file exists: `THIRD_PARTY_NOTICES.md` - Package id/version snapshot: `Nexamas UI` / `1.0.0-rc.1` - Binary package payload is declared by `Nexamas.UI.nuspec` and remains allowlisted to README, DLL, XML, PDB, and buildTransitive target file. - `buildTransitive/Nexamas.UI.targets` records Windows desktop / WinForms / .NET Framework 4.8 / Release|x64 compatibility envelope and rejects unsupported target framework ranges. - License text delegates updates/support/maintenance and customer-specific license terms to purchased license or separate written agreement/order form. - No runtime subscription billing, online activation server, customer portal, or license-server feature was documented from source in this phase. Commercial documentation boundaries: - Subscription is documented as a contract/delivery model, not as a Nexamas UI runtime feature. - Source access, private feed access, update/support entitlement, seats, permitted products, and delivery terms must be defined by a written agreement/order form. - PDF/Printer Output, public Theme Studio, public Surface Designer, public Quality Orchestrator, public virtualization SDK, and public translation/resource-engine API remain excluded unless a later source-reviewed phase proves them. Limitations: - No full Windows/MSBuild/.NET Framework 4.8 build was executed in this Linux sandbox. - Commercial gate results were not regenerated here; the phase documented commercial/adoption assets and boundaries from source. ## Phase 10 — Documentation Governance / Consistency Gate Status: Completed static documentation-governance authoring pass. Created/updated: - `tools/docs/Invoke-NexamasUIDocumentationGate.ps1` - `docs/_inventory/documentation-governance-inventory.md` - `docs/quality-proof/documentation-governance.md` - `docs/reference/documentation-gate.md` - `docs/developer/maintaining-documentation.md` - `docs/_inventory/claim-ledger.md` - `docs/README.md` Implemented static documentation checks: - required documentation foundation files exist; - Markdown files exist under `docs/`; - local Markdown links resolve; - `_inventory/claim-ledger.md` has parseable claim rows; - claim IDs are unique; - claim rows include claim, status, evidence, and documented-in cells; - documented `docs/*.md` paths referenced by claim rows exist; - source-evidence paths that look statically checkable are reported when missing; - forbidden wording that treats the Showcase as documentation source of truth is rejected; - documentation files are not included as `` items in `Nexamas.UI.vbproj`; - `docs/README.md` and this status file mention `Invoke-NexamasUIDocumentationGate.ps1`. Compile boundary: - Documentation files are not VB source files. - They must not enter the compilation pipeline as `` items. - They may remain repository/source-control files, may optionally be included as `` for Visual Studio visibility, and may be selectively packaged through `.nuspec` when desired. Execution note: - PowerShell execution was not available in this Linux sandbox. - The gate was authored and cross-checked by static inspection plus independent link/claim checks in the sandbox. - Run `tools/docs/Invoke-NexamasUIDocumentationGate.ps1` on the normal Windows/PowerShell development machine before claiming a release PASS. ## Phase 11 — Documentation Release Packaging / Docs Center Closure Status: Completed static documentation packaging and navigation pass. Created/updated: - `docs/index.md` - `docs/customer-guide.md` - `docs/company-adoption-guide.md` - `docs/developer-guide.md` - `docs/quality-proof-guide.md` - `docs/reference-guide.md` - `docs/_inventory/release-documentation-pack.md` - `docs/_inventory/package-documentation-boundary.md` - `release-docs/README.md` - `release-docs/NexamasUI_Product_Brief.md` - `release-docs/NexamasUI_Adoption_Guide.md` - `release-docs/NexamasUI_Quality_Proof.md` - `release-docs/NexamasUI_Documentation_Pack_Manifest.md` - `tools/docs/Invoke-NexamasUIDocumentationGate.ps1` - `docs/_inventory/claim-ledger.md` - `docs/README.md` Purpose: - Convert the previously source-verified documentation set into a readable Documentation Center. - Add audience-specific entry points for customers, company evaluators, developers, quality reviewers, and reference readers. - Add a curated `release-docs/` pack for commercial review without making it the source of truth. - Define what remains repository documentation, what is a release reading pack, and what may or may not enter a NuGet/package payload. Verified static facts: - `docs/index.md` and audience guides exist. - `release-docs/` exists and contains 5 curated Markdown files. - The current `Nexamas.UI.nuspec` packages the declared package readme plus root license and third-party notices, and does not include the full `docs/` or `release-docs/` folders. - Markdown documentation is not included as `` in `Nexamas.UI.vbproj`. - Documentation packaging is treated as a release/commercial decision, not as a compile step. Boundary: - This phase adds navigation and curated documentation packaging only. - It does not add new Nexamas UI product capabilities. - It does not execute the Windows build, Commercial Gate, SDK Harness, Render Verification, NuGet pack, or packed consumer proof. ## Phase 12 — Developer Examples / Copy-Paste Usage Guides Status: Completed static source-verified documentation pass. Created/updated: - `docs/_inventory/developer-examples-inventory.md` - `docs/examples/README.md` - `docs/examples/application-window-quickstart.md` - `docs/examples/controls-basic-example.md` - `docs/examples/layout-page-example.md` - `docs/examples/application-surface-example.md` - `docs/examples/theme-surface-example.md` - `docs/examples/localization-rtl-page-example.md` - `docs/examples/datagrid-example.md` - `docs/examples/output-example.md` - `docs/examples/render-verification-example.md` - `docs/developer/quickstart-copy-paste.md` - `docs/developer/common-consumer-patterns.md` - `docs/developer/consumer-do-and-dont.md` - `docs/developer-guide.md` - `docs/index.md` - `docs/README.md` - `tools/docs/Invoke-NexamasUIDocumentationGate.ps1` Verified static facts: - Examples use documented public entry points from `MASApplication`, `MASApplicationWindow`, public control factories, public layout builders, public theme/material facades, `MASLocalizationRtl`, `MASDataView` / `MASDataGrid`, `MASApplication.Output`, and `MASRenderVerification`. - No `.md` example files are included as `Compile` items in `Nexamas.UI.vbproj`. - Examples are source-derived documentation snippets, not Showcase-derived sample code. Limitations: - No full Windows/MSBuild/.NET Framework 4.8 build was executed in this Linux sandbox. - The examples should be compile-validated in a Windows SDK consumer project before being labeled as build-tested quickstarts. ## Phase 13 — Windows Validation / Real Gate Run Pack Status: Completed static packaging/update pass; real Windows execution still required. Created/updated: - `tools/validation/Invoke-NexamasUIWindowsValidation.ps1` - `docs/_inventory/windows-validation-inventory.md` - `docs/quality-proof/windows-validation.md` - `docs/developer/windows-validation-runbook.md` - `docs/reference/windows-validation-runner.md` - `docs/_inventory/claim-ledger.md` - `docs/README.md` - `docs/index.md` Source distribution cleanup performed in this phase: - removed `Nexamas.UI.vbproj.user` from the project snapshot - removed `samples/MinimalConsumerApp/bin/` from the project snapshot - removed `samples/MinimalConsumerApp/obj/` from the project snapshot Validation boundary: - The runner is ready for Windows. - Full build/runtime/package validation was not executed in this Linux sandbox. - A real pass requires running `tools/validation/Invoke-NexamasUIWindowsValidation.ps1 -Mode FullRelease -Configuration Release -Platform x64` on Windows. - Phase 13 FIX5: SDK harness build is platform-aligned with the x64 Nexamas UI commercial assembly. ## Phase 13 FIX6 — SDK Harness MSBuild Argument Quoting Status: Completed runner compatibility fix. Updated: - `eng/tests/Run-NexamasUISdkHarness.ps1` Verified issue addressed: - MSBuild failed with `MSB1008: Only one project can be specified` when the repository path contained spaces such as `D:\My Work Space\...`. - The SDK harness runner now passes MSBuild parameters through an argument array instead of an inline native-command argument expression. - The harness output path no longer relies on a trailing backslash in the `/p:OutputPath=...` value. Validation boundary: - This fix is source/static prepared in the generated package. - A real PASS still requires rerunning `tools/validation/Invoke-NexamasUIWindowsValidation.ps1 -Mode FullRelease -Configuration Release -Platform x64` on Windows. ## Product Controls ProductionReady Pack Status: Added. - Product pages: `docs/product/product-controls/` - Consumer-safe sample pages: `docs/examples/product-controls/` - Evidence page: `docs/quality-proof/product-controls-evidence-pack.md` - Release-facing summary: `release-docs/NexamasUI_ProductControls_Evidence_Pack.md` - Code governance: `MASDocumentationSampleEvidenceGate` Boundary: documentation and samples now reflect the all-control `ProductionReady` promotion, while API permanence and broader release packaging remain separate decisions. ## Phase 15 — User and Maintainer Documentation Split Status: Completed static source-verified documentation pass. Created/updated: - `docs/user/README.md` - `docs/user/installation.md` - `docs/user/first-window.md` - `docs/user/layout.md` - `docs/user/controls.md` - `docs/user/data.md` - `docs/user/theme.md` - `docs/user/localization-rtl.md` - `docs/user/output.md` - `docs/user/validation.md` - `docs/maintainer/README.md` - `docs/maintainer/documentation-rules.md` - `docs/maintainer/api-boundary-policy.md` - `docs/maintainer/quality-gates.md` - `docs/maintainer/release-process.md` - `docs/maintainer/showcase-integration-policy.md` - `docs/index.md` - `docs/README.md` - `docs/developer-guide.md` - `docs/developer/output.md` - `docs/recipes/showcase-snippet-map.md` Purpose: - Create a clean beginner path under `docs/user/` for real application development. - Create a clean maintainer path under `docs/maintainer/` for documentation governance, API boundaries, quality gates, release proof, and Showcase integration. - Keep user documentation separate from historical proof notes and internal maintenance details. - Correct the Output developer guide so release-evidence bundle generation is not presented as a public beginner API. - Correct the Theme developer/adoption guides so arbitrary `IMASAppTheme` registration is not presented as public beginner API. Verification state: - Source-verified against the current repository snapshot. - No Windows/.NET Framework 4.8 build was executed in this Linux sandbox. - No recipe was promoted from `Source-verified` to `Build-verified` by this pass. ## Phase 16 — Windows quality pass and recipe build-verification governance Status: Completed documentation governance pass after maintainer-reported Windows quality success. Created/updated: - `docs/quality-proof/windows-quality-run-2026-07-08.md` - `docs/recipes/build-verification-ledger.md` - `docs/recipes/README.md` - `docs/recipes/showcase-snippet-map.md` - `docs/quality-proof-guide.md` - `docs/maintainer/README.md` - `docs/maintainer/quality-gates.md` - `docs/maintainer/release-process.md` - `docs/_inventory/documentation-status.md` Recorded Windows result: ```text Passed: 15, Skipped: 0, Failed: 0 ``` Verification boundary: - The quality result was reported from the Windows development environment. - The Linux documentation sandbox did not execute Windows/.NET Framework 4.8 build tools. - Recipes remain `Source-verified` until their exact snippets, or equivalent consumer-project copies, compile in a clean Windows/.NET Framework 4.8 consumer context. - `Controls.BasicSet` and `Verification.RenderSnapshot` were promoted from `Draft` to `Source-verified` in the Showcase snippet map because their public gateway/source routes were inspected. They are not `Build-verified` yet. Next phase: - Build-verify Batch 1 recipes: first window, explicit lifetime, basic layout, basic controls, primary button, save/cancel buttons, TextBox, SearchTextBox. - Do not begin Showcase implementation until at least the first user-facing recipe batch is build-verified. ## Phase 23 — API Reference Batch 1 Application Status: Completed static source documentation pass. Created/updated: - `docs/reference/api/README.md` - `docs/reference/api/all-public-types-index.md` - `docs/reference/api/application-api.md` - `docs/reference-guide.md` - `docs/reference/public-api-surface.md` - `docs/reference/public-api-v1.md` - `docs/index.md` - `docs/README.md` - `docs/quality-proof/api-reference-batch1-application-source-pass-2026-07-08.md` - `docs/quality-proof-guide.md` - `docs/_inventory/documentation-status.md` Scope: - Total public type records locked for API Reference coverage: `296`. - Batch 1 documented namespace: `Nexamas.UI.Application`. - Batch 1 documented public types: `71`. - Batch 1 Stable records: `68`. - Batch 1 Evidence records: `3`. Boundary: - This pass documents public type and member evidence. - It does not execute Windows/MSBuild/.NET Framework 4.8 quality tools in the Linux documentation sandbox. - It does not promote Batches 2 or 3 to documented status. - It does not promote any preview, advanced, evidence, or compatibility type to beginner-stable V1 API. ## Phase 24 — API Reference Batch 2 Controls and Components Status: Source-documented. Created/updated: - `docs/reference/api/controls-components-api.md` - `docs/reference/api/README.md` - `docs/reference/api/all-public-types-index.md` - `docs/quality-proof/api-reference-batch2-controls-components-source-pass-2026-07-08.md` - `docs/quality-proof-guide.md` - `docs/reference-guide.md` - `docs/reference/public-api-v1.md` - `docs/index.md` - `docs/README.md` - `docs/_inventory/documentation-status.md` Scope: - `Nexamas.UI.Controls`: 50 public type records. - `Nexamas.UI.Components`: 117 public type records. - `Nexamas.UI.Components.DropDownMenu`: 5 public type records. - Total Batch 2 records: 172. Boundary: - This phase is a documentation/source pass only. - It does not change public API, source behavior, recipe state, Showcase readiness, package identity, or quality gates. - `Nexamas.UI.Controls` stable records remain the beginner control surface. - `Nexamas.UI.Components` and DropDownMenu records are documented for full coverage but remain Advanced or Preview where classified that way by the official manifest. - No Windows/.NET Framework 4.8 build was executed in this Linux sandbox. ## Phase 25 — API Reference Batch 3 Systems, Evidence, and Compatibility Status: Source-documented. Full current public type coverage complete. Created/updated: - `docs/reference/api/systems-evidence-compat-api.md` - `docs/reference/api/README.md` - `docs/reference/api/all-public-types-index.md` - `docs/quality-proof/api-reference-batch3-systems-evidence-compat-source-pass-2026-07-08.md` - `docs/quality-proof-guide.md` - `docs/reference-guide.md` - `docs/reference/public-api-v1.md` - `docs/index.md` - `docs/README.md` - `docs/_inventory/documentation-status.md` Scope: - `Nexamas.UI.FileSystem`: 4 public type records. - `Nexamas.UI.Icons`: 7 public type records. - `Nexamas.UI.Layout`: 9 public type records. - `Nexamas.UI.Localization`: 1 public type record. - `Nexamas.UI.Output`: 13 public type records. - `Nexamas.UI.Rendering`: 1 public type record. - `Nexamas.UI.TextInput`: 1 public type record. - `Nexamas.UI.Theming`: 8 public type records. - `Nexamas.UI.Values`: 3 public type records. - `Nexamas.UI.Verification`: 5 public type records. - `Nexamas.UI.WinForms`: 1 public type record. - Total Batch 3 records: 53. - Historical Batch 3 source-ledger coverage: 296 / 296 explicitly declared records. Current assembly-reconciled coverage: 302 / 302 CLR-visible types, including 6 compiler-generated nested event delegates. Boundary: - This phase is a documentation/source pass only. - It does not change public API, source behavior, recipe state, Showcase readiness, package identity, or quality gates. - Batch 3 contains no V1-approved beginner records; the types are Advanced, Evidence, or Compat according to the official classification manifest. - Evidence types support diagnostics, output readiness, or render-verification proof and should not be promoted as beginner application-building APIs. - `Nexamas.UI.WinForms.MASMenuButton` remains a compatibility surface, not the primary adoption route. - No Windows/.NET Framework 4.8 build was executed in this Linux sandbox. ## Final behavioral documentation expansion — 2026-07-10 The consumer documentation now includes dedicated behavioral references for the daily control families, advanced composite controls, all eight governed Product Controls, the Output facade, and the public Render Verification gateway. The references are source-checked by dedicated scripts under `tools/docs` and preserve Stable/Advanced and public/Friend boundaries. Remaining documentation risk is no longer missing system-family guidance. The remaining limitation is exhaustive XML/member-by-member IntelliSense coverage across every public member; this should be treated as a polish track rather than a missing user journey for the documented release surface. - The full Windows quality path now inspects the newly built `Nexamas.UI.dll` with `tools/docs/Invoke-NexamasUIPublicApiDrift.ps1`; the gate blocks unexplained hash, type/member, source-alignment, or assembly-freshness drift.