Design a local two-team display with labeled awards, stable event identities, and confirmation before undo or reset. It records a human operator's inputs. It does not grade answers, apply official match rules, or decide whether a team has mastered a topic.
The Fly Scoreboard author's overview distinguishes operator controls from an HTML score display. That general separation informs this independent local example; its OBS, WebSocket, timer, and live-feed features are outside this design. No plugin code or artwork is copied. Fly Scoreboard's author overview
Keep the display and the award record together
The original fictional teams are Team Amber and Team Blue. A new unsaved local session starts at 0:0 with empty history. Give each team native, clearly labeled +1 and +2 buttons. A facilitator decides which award is appropriate; the tool accepts only those positive integer increments.
Every award has an event ID, stable team ID, point amount, and active status. Scores can be reconciled as the sum of active awards for each team. Display names are labels: changing Team Amber's displayed name must not move its points to Team Blue or rewrite the event's team identity.
Keep full team names visible beside the numbers. Amber and blue colors can support the layout, but color alone should not identify a team. Provide a text history and a textual announcement of score changes, with usable keyboard controls and retained focus. Check these features in the intended host before using the scoreboard in an activity.
Walk through one complete correction example
Use these original demonstration awards:
| Event | Manual action | Result, Amber : Blue |
|---|---|---|
| E1 | Amber +2 | 2 : 0 |
| E2 | Blue +1 | 2 : 1 |
| E3 | Amber +1 | 3 : 1 |
Before correcting E3, show an action preview: “Undo E3: Team Amber +1. Result will be Amber 2, Blue 1.” If the operator confirms, mark E3 undone and leave it visible in the history. Scores become 2:1. A targeted undo for E3 must now be disabled; confirming or revisiting that same event cannot subtract it again.
Next, a new award E4 gives Blue +2. The score becomes 2:3. E4 is a new active event; it does not reactivate E3. At that point the history contains active E1, active E2, undone E3, and active E4. The totals are Amber's two points from E1 and Blue's three points from E2 plus E4.
Define what the next Undo will target
If the generic Undo command means “latest active award,” immediately after undoing E3 its next target is E2. After adding E4, its target is E4. The operator should see that target and the proposed result before confirming; a button labeled only “Undo” is not sufficient feedback.
Targeted undo and generic next-undo are related but different controls. The first names a particular still-active event. The second chooses the latest active award at the time of the proposed correction. When none exists, disable it and explain that there is no active award to undo. Keep cancellation separate from confirmation: canceling an undo preview changes neither scores nor history.
Make reset a new-session decision
At the current 2:3 score, preview a reset that clears the current history and returns both teams to zero. Cancel must preserve 2:3 and all current events. Confirm starts a new session at 0:0 with empty current history and a visible new-session boundary. The cleared history is not promised to be recoverable.
This design has no persistence. Reloading starts a new unsaved 0:0 session by the declared rule. Saving an HTML document is separate from preserving the score state created while using its controls. Do not add an unverified save, export, broadcast, or live-sync button to imply otherwise.
Copy this prompt to request the local HTML tool
Create one self-contained HTML/CSS/JavaScript manual scoreboard for two fictional teams, Team Amber and Team Blue. Return the complete HTML text plus a test checklist. No libraries,external requests,server,form submission,WebSocket,OBS,live feed,export or persistence.
New local unsaved session:0:0,emptyhistory. Native labeled +1/+2 buttons perteam,onlypositiveinteger awards. Humanfacilitator supplies awards;noautomaticgrading,matchrules,winner/mastery claims orpersonaldata.
Use stableteamIDs andsession-scoped eventIDs,team,amount,activestatus. Displaylabel edits do notmovepoints orchangeeventidentity. Textlabels/history/score announcements required;color notsoleidentity,keyboardfocususable.
Fixtures:E1Amber+2,E2Blue+1,E3Amber+1 =>3:1. UndoE3confirmed=>2:1,E3markedundone/historyretained. TargetedE3undoagain disabled. NewE4Blue+2=>2:3,E3staysundone.
GenericUndo targets latestactiveaward:afterE3undo nextE2;afterE4 nextE4. ShowexacteventID/team/points/projectedresult beforeconfirmation;cancelchangesnothing. Noactiveaward=>disabled/explanation. Preventrepeatundo/inactiveevents fromsubtractingagain.
At2:3 resetpreview:cancelpreserves scores/history;confirmnewsession0:0,clearcurrenthistory,visibleboundary. Reloadalsofreshunsaved0:0 bydeclaredrule. Explain document saving versusruntime scorestate;nofake Save/broadcastcontrols.
Fullteamnames visible atactualarticlewidth and360px;historyhascomplete text equivalent,controls keyboardusable. Testallfixtures,undo targets/cancel,resetcancel/confirm,reload andrename identity. Do notclaim testsran merelybecause codewasgenerated. Allsampleevents illustrative,notofficialscores.
Review the scorekeeping logic in NOS
NOS can save and render prepared HTML for a review of the labeled scores and correction history. Test the local award, undo, reset, and reload behavior before using the tool in an activity. The ability to save the document does not establish that runtime score changes persist.
Finish with the next correction visibly tied to its event, so an operator can explain every point on the display and cancel a destructive reset before it happens.