> For the complete documentation index, see [llms.txt](https://framework.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://framework.aic.io/company-operating-manual/agile-delivery-approach/beta.md).

# Beta

### Purpose

Beta is where the best idea from alpha is built for real users.

The goal is to develop, test, improve, and prepare the service or product for live operation.

### Private Beta

Private beta is used with a limited group of users.

It allows the team to:

* validate the service with real users
* identify usability issues
* test operational support
* refine technical performance
* improve security and reliability
* reduce risk before wider release

### Public Beta

Public beta is used when the service is ready for wider use but still being actively improved.

It allows the team to:

* test scale
* monitor performance
* gather broader feedback
* improve support processes
* prepare for live transition

### Beta Activities

Typical beta activities include:

* product build
* user research
* accessibility testing
* security testing
* performance testing
* integration testing
* operational readiness planning
* service support design
* data protection review
* release planning

### Beta Outputs

Beta should produce:

* working service or product
* tested user journeys
* service metrics
* support model
* technical documentation
* security evidence
* release plan
* live readiness assessment
* updated roadmap

### Exit Criteria

Beta is complete when:

* the service works for users
* operational support is ready
* security and assurance requirements are met
* performance is acceptable
* metrics are in place
* the service is ready to move into live operation