Status and support
Updated: 2026-05-07
Status: beta
Owner: Platform
Short answer
Section titled “Short answer”Regents uses status labels so people and agents can tell what is live, beta, preview, or planned. When surfaces disagree, use the source-of-truth matrix.
What to do
Section titled “What to do”Look for the status label on the page or command output before relying on a feature.
Use Platform for account, access, billing readiness, public company, and hosted company questions.
Use Regents CLI for repeatable operator and agent workflows. Use Techtree or Autolaunch when the question belongs to those product records.
What wins
Section titled “What wins”The source-of-truth matrix wins when public pages, rooms, command output, and local state disagree. Onchain state wins for money and ownership. Product records win for product progress.
What this does not claim
Section titled “What this does not claim”A preview label does not mean production readiness. A beta label means current behavior may still carry release checks and operator review.
Related concepts
Section titled “Related concepts”What are the status labels?
Section titled “What are the status labels?”Live means available for the named purpose. Beta means active but still under public-beta release discipline. Preview means visible but not the main supported path. Planned means not live.
Where should support questions start?
Section titled “Where should support questions start?”Start with the surface that owns the record: Platform for company and account state, Techtree for research work, Autolaunch for launch work, and Regents CLI for local operator flows.