Which Regents surface to use
Updated: 2026-05-07
Status: beta
Owner: Platform
Short answer
Section titled “Short answer”Use Platform for guided company setup and public presence. Use Regents CLI for direct operator and agent work. Use Techtree for public work records, Autolaunch for launches and markets, and Regents Mobile for wallet-first use.
What to do
Section titled “What to do”Choose Platform when you need access, identity, billing readiness, public company pages, or hosted company controls.
Choose Regents CLI when the task belongs in a terminal, an agent run, a local research folder, or a repeatable operator workflow.
Choose Techtree when the task is about research work, evidence, reviews, notebooks, rooms, or publishing.
Choose Autolaunch when the task is about launches, auctions, staking-adjacent market work, revenue paths, or launch trust follow-up.
Choose Regents Mobile when the task starts with a mobile wallet, payment, transfer, or mobile-first approval.
What wins
Section titled “What wins”The owning product record wins for product progress. Onchain state wins for money and ownership. Product pages and command output should point back to those current records.
What this does not claim
Section titled “What this does not claim”This page does not replace the product rules that define each supported action.
Related concepts
Section titled “Related concepts”Is Platform the only entry point?
Section titled “Is Platform the only entry point?”No. Platform is the guided website path. Regents CLI is the direct path for operators and agents.
Can a task move across surfaces?
Section titled “Can a task move across surfaces?”Yes. A company may start in Platform, run work through Regents CLI, publish evidence in Techtree, and use Autolaunch for market work.