Scorecard

Scorecard answers a single question: is this game ready to ship?

It’s a milestone-gated rubric — Greenlight, Vertical Slice, Alpha, Beta, Launch-Ready — that scores your project across six axes using a data-driven signal registry, with a Claude narrative pass on top.

What Scorecard does

Sonar looks outward at your audience. Radar looks at your delivery health. Scorecard reads “where are you in the lifecycle, and what’s blocking the next milestone?”

A run produces:

• Per-axis scores across Market, Product, Tech, GTM, Team, and Business — each signal contributes deterministically, math is enforced in code
• Composite score weighted by the milestone you’re targeting (tech depth matters more at Alpha than at Greenlight; GTM matters more at Launch-Ready than at Vertical Slice)
• Gap callouts — the specific signals dragging your score, ranked by impact
• Narrative — a Claude-written read of what the scores mean, what’s blocking, what to fix first
• Full audit trail — every signal’s input data and computed score, persisted with the engine version

The six axes

• Market — addressable audience, comp performance, genre tailwinds (cross-references your Sonar reports)
• Product — design clarity, mechanic readiness, scope coherence
• Tech — engine maturity, build health, performance budget (cross-references Radar signals)
• GTM — channel readiness, audience reach, marketing prep (cross-references Launcher plans)
• Team — staffing fit, contributor stability, velocity (cross-references Radar’s team signals)
• Business — funding runway, revenue model, monetisation plan

How a run works

1. Pick a game and a target milestone
2. Scorecard resolves the signals registered for that milestone
3. Self-report signals pull from a profile form your team fills in; auto-collected signals read from Sonar / Radar / Launcher data
4. Per-signal scores roll up into per-axis scores; the composite is weighted by the milestone
5. Claude writes the narrative pass
6. The run is persisted with full audit trail and engine_version

You can re-run the same milestone at any time. When the engine version changes, prior runs are flagged stale; re-running on the same inputs gives you a direct before/after comparison.

What you see in the UI

• Game Picker — your games with their last-run summary
• Game Overview — current scores, milestone status, run history
• Run Wizard — kick off a new run and watch the live trace as signals resolve
• Report — radar chart, gap callouts, narrative, full audit

Privacy

Scorecard pulls from the same studio-scoped data as the rest of the platform. Cross-studio access is rejected at the API layer. No contributor-level data ever surfaces — Scorecard reads team-health observations from Radar (concentration risk, velocity) rather than individual records.

Where it lives

Scorecard is part of the Hypercade portal at app.hypercade.io (UI mounted at /scorecard/). Same login as Sonar, Radar, Launcher, and the Studio Portal.

Status

Live (foundation tier). The engine, signal registry, and UI are running in production. Signal coverage is partial — the rubric is in place but not every signal across every axis is wired to a real collector yet. Coverage is expanding as more studios onboard.

Questions?

Email [email protected] — we’ll help you run your first scorecard or interpret the gaps.