Reference Preview
Product and SDK release states
Interpret Available, Beta, Preview, Planned, Case study, and Verification pending labels across Yapture.
Why the labels exist
Yapture spans released packages, public product surfaces, developer previews, integration proofs, and documented future work. The website labels those states so architecture direction is not confused with availability.
| Label | Meaning |
|---|---|
| Available | Verified in the current public product or package |
| Beta | Implemented and usable with an opt-in or release caveat |
| Preview | An API/package/surface exists but may change or lack general distribution |
| Coming soon | Planned; not presented as usable today |
| Case study | Demonstrated in another product or internal integration |
| Verification pending | Source suggests support, but the current public release has not been smoke-tested |
Claim rules
- A planned feature never gets an install or try-now control.
- A simulated fixture is labeled simulated.
- A local demo is not labeled connected or synced.
- A live API state appears only after a successful response.
- A package install command is published only after a clean install test with documented registry requirements.
- Maturity changes belong in the changelog, including Preview → Available.
Current integration notes
- Portable Script parsing and shared UI packages have production integration evidence.
- Local-first list primitives exist, but every public transport claim still needs deployment verification.
- The MAUT SDK contract is a developer preview and currently uses the
@magycfit/*namespace. - MAGYC.fit grading remains Coming soon until a versioned grading contract exists.
- Client and ecosystem surfaces carry individual release labels; a family name does not imply every client is generally available.
Check the public release status and the changelog for current verification notes.