team-live-ops

You can plan a live-ops season pipeline by orchestrating specialized roles across narrative design, economy design, and analytics to generate a complete season brief, reward track, and communication calendar.

A seasonal event plan includes scope definition, content lists, retention hooks, resource budgets, narrative framing, reward track fairness checks, telemetry requirements, and player communication schedules.

You design an economy reward track by creating a seasonal theme and balance structure, validating against an ethics policy file, and generating specific analytics instrumentation requirements for tracking.

Yes, you can run live-ops season planning without fragmented back-and-forth by using a coordinated workflow that delegates subagent tasks across specialized roles and requires phase-gated user approvals.

Yes, live-ops planning blocks advancement if an economy design violates the provided ethics policy file, ensuring reward tracks are checked for fairness before proceeding to analytics and comms handoff.

The best way to generate player-facing communication calendars and success metrics is to use a structured live-ops workflow that outputs telemetry readiness documents and comms schedules under a design directory.