# Evidence status

Weir is a controlled private alpha. This page separates what a visitor can run or inspect today
from what still needs released-build or production evidence. It is not a case-study page and it
makes no conversion, adoption, uptime, or production-maturity claim.

## Current proof ladder

| Capability | Current status | What it proves | What it does not prove |
|---|---|---|---|
| Local author → conform → preview/release rehearsal | **Publicly runnable** | A developer can use the toolkit without an account, API key, or hosted service. | A hosted rollout reached a released customer build. |
| SwiftUI custom-component integration | **Qualified dogfood evidence** | The v4 model has been integrated into a dogfood SwiftUI app. | Public package reproducibility, external-customer adoption, or an outcome result. |
| React Native/Expo integration | **Qualified dogfood evidence** | The v4 model has been integrated into a dogfood React Native/Expo app. | Complete Android device proof or a public production claim. |
| Browser review, generated config diff, and conformance findings | **Inspectable demo data** | The dashboard can demonstrate the review model without an account. | Native-device pairing or a released-build result; demo data is never a customer account. |
| Compatible flow delivery to released builds | **Verification gate** | The product contract and local rehearsal define the intended path. | A public released-build demonstration until its evidence manifest is approved. |
| Incompatible-build refusal and retained baseline | **Verification gate** | The app-owned baseline and registry/version gates are the designed safety model. | A public observed refusal on a released build until captured and approved. |
| Decision-grade experiment outcome | **Pending sufficient traffic** | The event and assignment contract is available for the experiment lifecycle. | Conversion lift, a winning treatment, or general business impact. |

## Inspect the current loop

1. **Run it locally.** [Run everything locally](/docs/local/) for the no-account author → gate →
   local delivery rehearsal. Start with `weir audit --appRoot .` when you want an inventory of the
   declared flows, registered components, baseline, and readiness checks. The report labels its own
   limits: it does not infer active-install coverage or claim device or outcome proof. That local
   path remains the strongest public proof today.
2. **Inspect the fixture-backed product tour.** The [dashboard demo](https://weir-onboarding-2026.web.app/?demo=1#/demo)
   labels its data before showing a draft diff, conformance findings, rendered review, a
   compatibility refusal, and an experiment readout. It is an interface demonstration, not
   customer evidence.
3. **Read the delivery model.** [Concepts](/docs/concepts/) explains the app-owned component
   contract, signed delivery, embedded baseline, and kill switch.

## What a public proof recording must contain

The next public proof asset must show the following in one continuous, attributable sequence:

1. An agent edits a repository-owned flow.
2. The generated review artifact identifies the changed journey and affected components.
3. The gate reports the compatible and incompatible build decisions.
4. An already-installed compatible build receives the release without a new binary install.
5. An incompatible build refuses the remote flow and retains its embedded baseline.
6. Assignment, flow version, build version, step progress, and outcome arrive in the evidence
   surface.

Until that recording is captured with an approved evidence manifest, the homepage and docs must
describe it as a gate, not an observed public result.

## Claims boundary

Use these phrases precisely:

- **Compatible composition changes can be delivered without a new app build.** New component
  capabilities still require an app release.
- **Your app owns rendering, interaction, and product logic.** Weir composes registered screens
  and properties; it is not a raw-markup or visual-editor runtime.
- **The v4 API, flow delivery path, and dashboard are live for a controlled private alpha.** Do
  not call Weir production-proven, a public beta, or self-serve hosted software yet.

For how that boundary applies during an integration, see [Onboard an app](/docs/onboard-an-app/)
and [Review a flow](/docs/review/).