Clear scope
Every live session should define what it is, what it is not, who it is for, and what preparation is required.
Private sessions should feel considered before they feel bookable.
Live services, guided conversations and future practitioner sessions belong in the ecosystem, but they should launch with the same clarity, boundary language and premium restraint as the core modules.
Protected trust layer
Consultation, reflection and commerce should not blur together in the first viewport. The premium shell stays consistent, while the service scope stays explicit.
Staged release
New live services should open first as controlled staging pathways, then graduate to production only after the booking, notification and consent flows pass QA.
Method before mystique.
The staging experience makes the source, calculation boundary, and interpretation boundary visible before any claim is made.