# Nexamas UI Adoption Guide

This guide summarizes how a company or customer should evaluate Nexamas UI without relying on undocumented internals.

## Adoption model

- Use public consumer-facing entry points only.
- Treat Friend/internal classes as implementation and proof infrastructure.
- Treat the Showcase as a demonstration layer, not as the product source of truth.
- Run the Windows build/package/quality gates before claiming release readiness.

## Required evaluation references

- [`../docs/company-adoption-guide.md`](../docs/company-adoption-guide.md)
- [`../docs/commercial/commercial-adoption-guide.md`](../docs/commercial/commercial-adoption-guide.md)
- [`../docs/commercial/company-evaluation-guide.md`](../docs/commercial/company-evaluation-guide.md)
- [`../docs/reference/public-api-surface.md`](../docs/reference/public-api-surface.md)
- [`../docs/commercial/stability-and-roadmap-boundary.md`](../docs/commercial/stability-and-roadmap-boundary.md)

## Commercial boundary

Subscription terms, support, update rights, seats, private feed access, source access, and customer-specific permissions must be defined by a written agreement or order form. The SDK snapshot does not implement runtime subscription billing or online activation.