One system.
Four roles.

Child, parent, coach, program staff. The same case state, the same canonical spine, but presented differently to each role. A coach's observation becomes a daily action for the child, a conversation prompt for the parent, a propagation record in the player's case, and a workload signal for staff. Every visible feature projects back to one underlying system.


The Player

A plan they can actually carry.

The child surface is simple, structured, and identity-rich, it looks like baseball, not a blank AI interface. One primary action today. The week's plan, the next game, a simple progress indicator. Post-practice reflections are tap-first, text-second, voice-optional.

MON · 4:15P PILLAR 3/8
Today's Challenge
20 glove reps →
Warm-up · stretch
Pre-practice breath
Reflection · 3 taps
  • Central goal always visible. Pillars are the navigation spine.
  • Measured items for mechanics. Witnessed items for character, recorded, not scored.
  • Bounded baseball-affinity layer: a moderated space to talk about favorite players.
  • Native mobile. Push, media capture, offline-resilient, parental controls.
The Supporter

Clarity about what matters tonight.

The parent surface answers four questions: what matters this week, what needs doing tonight, what changed, and what needs your attention now. Flexible delegation, review everything, approve exceptions, or let the system handle ordinary cases.

This Week 2 need review
Skip Thursday drill?
Share coach note
  • Daily mode for quick approvals on mobile; weekly mode for reflection.
  • Co-present mode, parent and child on the same device, working together.
  • Transparency is first-class: see what the system learned, and why.
  • Shared-device handling built in from day one, not an edge case.
The Evaluator

Signal, not another inbox.

Coaches do not need another communication channel. They need visibility, signal compression, and exception handling. Contribute a small number of high-value inputs after a game, the system translates them into a training task, a parent explanation, and a case record.

ROSTER · 12A
PLAYERTRENDFLAG
M. Ortiz
J. Tanaka
R. Hayes
A. Singh
  • Observations about a player are distinct from observations visible to the family.
  • Dense web dashboard, density, keyboard entry, desk-first workflow.
  • Mobile companion for on-field observation capture when you need it.
  • Trends, attendance, post-game summaries, alerts that warrant attention.
The Governor

Oversight without surveillance.

The staff surface is the governance, operations, and quality-assurance layer. Engagement health, family attention flags, coach workload, moderation queues, escalation outcomes. The principle is controlled visibility, staff see what they need, not what families would experience as monitoring.

GOVERNANCE · LIVE 04:12:33
MOD QUEUE
12
ESCALATE
03
HEALTH
OK
  • Escalation is the primary location of human judgment, precise, infrequent.
  • Moderation queues, escalation review, audit trails, program-health dashboards.
  • Version-controlled policy and configuration, team judgment lives between iterations.
  • Observability: model traces, retrieval provenance, decision paths, corrections.
Operating Principle

A bounded developmental manager, not a chatbot, not a drill tracker. It maintains a structured model of each player's case, decomposes long-horizon goals into daily action, and escalates to humans when policy or uncertainty requires judgment.

CANONICAL SPINE
People
Goals
Activities
Observations
Governance

Every consequential action is bounded by rules the team configures. Team judgment lives between iterations.