Studio policy is only useful if people can find it at the moment it matters. A late-cancel rule hidden in an admin settings page does not help a student understand a charge. A role benefit buried in a spreadsheet does not help staff explain why access was granted. Context is part of the policy experience.
Sangha is designed so policy settings can resolve where the decision is happening. Booking, access checks, pricing, cancellations, complimentary access, and payroll-related decisions can all point back to the relevant studio policy, effective date, version, override path, and inputs.
That matters because studio policies change. A rule can be true this month and different next month. A teacher benefit can apply to one offering but not another. A late-cancel policy can be different for a workshop than a weekly class. The system needs to resolve the current context without rewriting history.
Putting policy in context also reduces awkward social labor. Staff should not have to apologize for a mysterious system or search through old messages while a student waits. Students should be able to see the rule before they feel surprised by it.
Good policy work is not about making a studio rigid. It is about making agreements clear enough that compassion and consistency can coexist. Sangha keeps policy close to the action so decisions are easier to understand and easier to trust.
