One release, one shared journey
Amber's beta actively tests its release contract with real web apps. Your framework, dependencies, installation, updates, technical docs, tutorials and agent guidance should describe the same supported experience.
Beta.5 already has coordinated framework/CLI, package, fresh database-backed consumer, documentation and public-origin proof. The supported web foundation is stable and release-gated. Individual library/tool releases move at their own pace; the tracker records their publication and exact source independently. Native apps and named previews follow their separate support gates.
Take an app through the loop
- Bring the need through a GitHub issue with your coding assistant and human-reviewed evidence. A maintainer agrees on scope.
- Link the implementation PR, behavioral proof, documentation/tutorial change and a short release sentence. Performance changes link their measured research.
- Select exact library and tool versions, full source revisions, verified artifact hashes and dependency closure. Include the compiler's source, bootstrap, LLVM/system inputs, build recipe and output identity.
- Exercise fresh installation and an existing-app upgrade: render, create/edit, restart, make an assistant-assisted change, inspect it, and check applicable budgets.
- Review every required scenario and support claim, approve the candidate, publish its artifacts, then verify the served website and resources. Keep the predecessor and an exercised recovery plan.
- Return app discoveries as issues and carry the resulting code/guidance into the next release. Showcase publication confirms permission and credit.
Release notes stay short: the change, who benefits, support boundaries and links to the detailed guides and research.
What is automated today
The website's ecosystem collector checks the declared repository roster hourly, on manual dispatch and on supported repository dispatch. It resolves release tags to full commits, records GitHub-reported asset digests, retains immutable snapshots and exposes the last successful check. Incomplete collection keeps the previous complete snapshot. Source, tag, release and support states remain distinct.
This tracker is the publication ledger for repository metadata. A unified bundle connecting every library's versioned API docs, runnable tutorials, docs MCP corpus, agent catalogs, update feed, performance gates and compiler provenance is still being completed. Broad policy/check installation, full themed library-doc generation, agent-context-preserving upgrades and recovery rehearsal have their own acceptance.
Choosing a business pattern
The template promise adds a reference app, migration path and published measured operating range to each recommendation. Current client-portal, inventory and service-desk invitations have unmeasured template capacity. Existing core/codec research retains its declared scope.
As a pioneer, build one useful slice and report the versions, journey checkpoint, expected/actual behavior and reproduction. That is enough to help test the contract.