# Evaluate Tenhaw Quality

This guide describes the implemented setup and evidence workflow. It does not establish a live provider qualification, customer outcome or service certification. Check the current operator-published qualification statement and your agreement before starting an evaluation.

## Start with one release

1. Sign in at `/quality-start` and select or create your organization. Current organization and project membership control access.
2. Create a project and connect GitHub or Azure DevOps. Choose an exact source revision and supply approved expected behavior and standards.
3. Review the proposed test setup, approved environment actions, qualified runner, scope and spending allowance. Production actions require explicit owner approval.
4. Run the approved plan. Review passing, failing and incomplete checks separately. Keep unresolved findings and mutation survivors visible. Human release decisions remain attributed.

Creating a workspace does not approve a plan, grant a paid entitlement, reserve funds or execute a test.

## Inspect the owned sample

The downloadable evidence pack contains an independent invoice specification, source and unit examples, measured outcomes, six unchanged native API/property reports and per-file SHA256 checksums. The fixed sample passes its core tests; seeded shipping and tenant faults fail their relevant expectations. Six of twelve mutants survived. Local host paths and stack traces are excluded from the public outcome projection.

The sample contains no customer data, cloud execution or model-generated results. It is educational evidence and does not qualify E2B, a private VM, an independent evaluation corpus or paid delivery. After extracting the pack, Node20+ can execute the included unit examples:

```sh
node --test sample/tests/rules.test.cjs
```

## Review your execution boundary

Customer repository code runs within a qualified disposable E2B or customer-private VM boundary. The control worker does not run that code on its host. Targets, resource use, network allowance, deadlines, cancellation and cleanup are part of the execution admission. Source-built browser targets require separate application and runner network namespaces and their qualified bridge.

Provider repository credentials stay in the source broker. Private API personas use a dedicated source-free credential lane. Generated tests are limited to approved expectations; new assumptions need review. A model response is untrusted input, not a passing result.

## Plan for cancellation and export

Cancellation requests termination and stops new admission. Cleanup proof and cost settlement are separate steps. Resource leases and reservations can remain occupied while cleanup or liability is unknown. Performance settlement follows the accepted quote and native delivery evidence.

Export report data, retained artifacts and supported approved definitions from your authorized workspace before their retention expires. Missing and expired evidence remain explicit. Closing an evaluation checks feedback, ongoing work, cleanup and cost liabilities; a closure decision does not prove complete erasure of every customer-managed system.

## Questions to resolve before purchase

- Which exact provider, image, region and methods have current qualification evidence?
- Which representative release and independent expectations define a successful evaluation?
- What targets, permitted actions, request volume, duration and cost ceilings are approved?
- What data handling agreement, subprocessors, retention, deletion and access rules apply?
- What scope is included in the offer, and how are cancellations and incomplete delivery treated?
- Who reviews findings, decides on release, handles support and authorizes renewal?

Generic command adapters are extension mechanisms, not native coverage of every language, device, security technique or regulated domain. Automated accessibility scans cover selected rules. Browser, Testcontainers and source-build paths have explicit supported subsets. No percentage confidence, best-in-class comparison, unlimited capacity, realized margin or revenue outcome is established by the sample.