Roast collects onboarding fields because they map directly to product behavior.
- Name, location, and intended use shape the profile context.
- Language and voice preferences drive the TTS output.
- Policy acceptance records make consent explicit.
- Alias and feed handoff make the account operational.
Roast does not ask for arbitrary profile theater. Each field is either operational or downstream personalization input.