User companion

DelphAI xLM

Standalone user-facing runtime for chat, saved prompts, schedule-driven briefings, and league-grounded sports assistance.

Preference center

User settings should change outcomes, not reveal internals

Settings are the contract between the user and the companion. They shape tone, delivery, citation behavior, and league defaults, while still keeping system administration out of the user runtime.

Audience discipline

If a setting would require admin credentials, secret management, or model deployment knowledge, it belongs to the admin Meta-XLM family instead of this app.

Control type

User preferences

This screen owns user-facing defaults only, not operational controls.

Delivery impact

Immediate

Settings affect live chat, saved prompts, and scheduled deliveries.

Support stance

Transparent

League coverage and citation settings must communicate the current reality of the data stack.

Setting groups

The user preference model is already concrete

These groups define the first persistence contract for profile defaults, league posture, and delivery channels.

Companion style

User-facing controls that shape the conversation but do not expose admin or model-ops configuration.

Preferred response length

Concise with explicit caveats

Citation mode

Always show tool and source summary

Default profile

Briefing Analyst

League coverage

The UI has to disclose where live support exists today.

MLB

Enabled

NBA

Visible but blocked pending ETL

Fallback behavior

Explain capability state instead of fabricating output

Delivery channels

Queue-backed jobs can target different channels once orchestration and notification services are live.

Primary channel

In-app and email

Urgent follow-up

Push notification

Quiet hours

22:00 to 06:30 local