# Nexamas UI Company Adoption Guide

This guide is for a company evaluating whether Nexamas UI can be adopted inside a product or internal Windows desktop application.

## Evaluation order

1. Confirm the commercial boundary in [Commercial adoption guide](commercial/commercial-adoption-guide.md).
2. Confirm package and delivery expectations in [What is included](commercial/what-is-included.md).
3. Confirm target framework and platform boundaries in [Company evaluation guide](commercial/company-evaluation-guide.md).
4. Review public API boundaries in [Public surface policy](adoption/public-surface-policy.md).
5. Review quality proof boundaries in [Quality proof guide](quality-proof-guide.md).
6. Run the required Windows quality, package, and external-consumer gates in the supported build environment.

## Public surface rule

A company should rely on public consumer-facing entry points only. Friend/internal systems may be used as evidence that Nexamas UI owns a capability, but they are not adoption APIs.

Important references:

- [Public API surface](reference/public-api-surface.md)
- [Application facade surface](reference/application-facade-surface.md)
- [Component factory surface](reference/component-factory-surface.md)
- [Layout/size surface](reference/layout-size-surface.md)
- [Theme/surface surface](reference/theme-surface-surface.md)
- [Localization/RTL surface](reference/localization-rtl-surface.md)
- [Data component surface](reference/data-component-surface.md)
- [Output surface](reference/output-surface.md)
- [Quality verification surface](reference/quality-verification-surface.md)

## Detailed adoption boundaries

- [Application composition model](adoption/application-composition-model.md)
- [Component adoption boundary](adoption/component-adoption-boundary.md)
- [Data and virtualization adoption boundary](adoption/data-virtualization-adoption-boundary.md)
- [Layout and size adoption boundary](adoption/layout-size-adoption-boundary.md)
- [Localization and RTL adoption boundary](adoption/localization-rtl-adoption-boundary.md)
- [Output adoption boundary](adoption/output-adoption-boundary.md)
- [Package and delivery model](adoption/package-and-delivery-model.md)
- [Theme and surface adoption boundary](adoption/theme-surface-adoption-boundary.md)
- [Quality and commercial proof boundary](adoption/quality-commercial-proof-boundary.md)

## Adoption caution

This documentation does not replace a real integration test. A company adoption decision still requires a Windows/Visual Studio/.NET Framework 4.8 build, package, SDK harness, commercial quality runner, and consumer proof run.

See [Commercial gate](quality-proof/commercial-gate.md) and [Documentation gate](reference/documentation-gate.md).