|
World Bachata League · System Architecture & Operational Alignment

Technical Architecture & Circuit Alignment: Core Platform & World Bachata League

Nothing in the design changes today. The answers go on the list for after the move to the organization.
Topic 1 · 1 / 5

Who does what in scoring

Core Platform Architecture
World Bachata League Specifications
Platform
App Owner · PSA (developer)PlatformGrant · Access Control
admin · moderator
↓
↓
League
League & Stats (one league)PointsAward · Standing · seasons · rankings
Leaguelevels, tiers, seasons, points table
↓
↓
Organizer
OrganizerOrganization + OrganizationMembership · Tenancy
Organizer + teamowner, staff, director, presenter
↓
↓
Event
Event: one festival editionevent_id groups one competition per division · Competition Management
EventSebas's word: competition
↓
↓
Level
Competition: division AMATEUR or PROCompetition aggregate · Competitor entries · staff grants COMPETITION_DIRECTOR · HEAD_JUDGE · JUDGE · DESK · FLOOR_MANAGER · MC
LevelSebas's word: contest · registrations · judges by link · no head judge
↓
↓
Scoring
Round → Heat → Scorecard → ResultSetFloor Operations · Scoring · then PublishedResultSnapshot (Publishing)
Round → Heat → Ballot → Final Placements (WBL: 'podio')
The head judge cannot lock or publish. The director cannot dance in the competition they run.
Design: use-cases-overview.md actors A02, A03, A04, A06, A11 · api-overview.md (lock: Director; publish: Director, Organizer)
Topic 1 · 2 / 5

A judge puts a mark on the wrong bib. When is it fixed?

Core Platform Architecture
Judges score
Fixed HERE: judge fixes own card, head judge sends cards back
Director locks the round: no more changes
Published: points, ranking
Rare case found later: developer-only correction (planned)
World Bachata League Specifications
Judges score
Round closes
Moderator approves final placements (colloquially 'podium' / WBL: 'podio')
Published: points, ranking, level-ups
Admin fixes it AFTER: UC-ADM-24 «Corregir un podio publicado», places typed by hand
Topic 1 · 3 / 5

How the mistake is caught before the lock

Core Platform Architecture
1Head judge gets an alert on their own phone.
2Opens the private review grid: one judge far from the rest is red.
3Sends that card back with a reason.
4The judge sees the reason, fixes it (or keeps it), sends again.
▦ 3 scores far from the panel · View
Amateur · Preliminar
Heat 2 of 4
104 8.0
168 7.5
186 6.5
1 · head judge's own card, with the alert
Review4 of 4 judges in · Leads
104168186201
Judge A8.08.06.58.5
Judge B7.58.06.09.0
Judge C8.08.06.57.0
Judge D8.52.09.09.0
ALERT Judge D · 168 · 2.0 · panel median 8.0 Reopen this card
ALERT Judge D · 186 · 9.0 · panel median 6.5
WARN Judge C · 201 · 7.0 · panel median 8.8
2 · Judge D: 168 too low and 186 too high, numbers that look alike: probably a swapped bib
Reopen Judge D's card Reason
168 and 186 look swapped.
CancelReopen
3 · head judge
Judge D's phone: "The director reopened this scorecard. Check your scores and send it again."
Reason: 168 and 186 look swapped.
4 · the judge decides: fix it, or keep it if that is what they saw
QUESTION

A mark turns yellow at 1.5 points from the panel's middle mark, red at 2.5. Our numbers. Right for you?

Topic 1 · 4 / 5

How established events do it

WSDC (West Coast Swing)
The Chief Judge is "responsible for the oversight of the event's contests and for ensuring the integrity of every contest", and cannot compete.
The Event Director and/or the Chief Judge "shall verify contest results" before sending them.
"If results are inaccurate (e.g., scoring issues, violations), corrected results must be posted."
WSDC Registry Event Rules 2026 (v2026.1C), Definitions, §2.3, §3.1 item 9
Ballroom (NDCA)
The scrutineer and the chairman of adjudicators certify the master sheets before the marks are posted.
NDCA Rule Book change log, 2025
1 · Check before posting→2 · Correct only if still wrong
Topic 1 · 5 / 5

Recommended Architecture & Synthesis

Primary Path · Pre-Lock Anomaly Interception
Keep the checks before the lock as the main path
  • Same order as WSDC and ballroom.
  • Before the lock the fix is one resubmit. Nothing has reached points, ranking or levels yet.
Exception Path · Post-Publish Immutable Correction
Keep a correction after publish only for the rare case
  • WSDC requires corrected results when results are wrong.
  • Keep what UC-ADM-24 does well: void and re-issue points, version the result.
  • Also cover what it leaves open: a level given on wrong points, telling the dancers who moved, a second person approving.
  • Correct the marks, not the places by hand, so the result still comes from the judges.
OPERATIONAL CALIBRATION (SEBAS & SILVIA)

In your manual festival operations, how often has a published score or podium place needed a manual correction on the clipboard or spreadsheet? When that happens, who has final authority on site—Silvia, the Head Judge, or the Organizer?

Translating manual operations into software: Silvia runs many of these competitions on the ground manually. Sharing your paper scoring templates, tally sheets, and manual scrutineering workflows will help us automate exactly how you run events on the floor.
Nothing in the design changes today. The answers go on the list for after the move to the organization.
Topic 2 · 1 / 4

Venue Display Subsystem during Prelims (colloquially 'venue screen')

Core Platform Architecture
Preliminaries & Semi-Finals
Athlete Mobile View: personal heat & callback status UC-CMP-02, UC-CMP-03
Public Results Endpoint, once round is published UC-AUD-02
No automated ballroom display for heats & callbacks
Finals Phase
Final Show Display + Stage Announcer Cue Feed UC-PUB-05, UC-MC-01
World Bachata League Specifications
Every Round
Public Venue Display, unauthenticated SSE stream UC-PAN-01 · /app/screen/:slug
Manual Scene Selector: auto · dancing · going through · placements · message · logo
Ballroom Announcement Banner · Role Roster UC-PAN-04
Manually triggered by owner, staff or director UC-PAN-03
Stage Presenter passively follows screen UC-PAN-02 · 'presentador'
Topic 2 · 2 / 4

Domain Architecture: Big Screen & MC Cue Screen

Separation of Concerns & Responsibilities
Amateur · Preliminar · Leads
Heat 3 on the floor
101104168186201215
Up next: Heat 4 · 120 · 133 · 147 · 159 · 172 · 190
Going through (after publish): 104 · 133 · 168 · 201 …
1. Floor Manager (Event Driver)Calls & advances heats on /app/floor (UC-FLR-02). In finals, Director cues (UC-DIR-12).
→
2. Public Big ScreenZero chrome at /live/:competitionId (UC-PUB-05). Polls every 3s (1s CDN edge cache).
→
3. MC Cue ScreenDedicated teleprompter at /app/mc/:competitionId (UC-MC-01). Strictly read-only for StaffRole.MC.
System Design: The MC (StaffRole.MC) has a dedicated read-only cue screen (/app/mc/:competitionId / UC-MC-01) with bib numbers, city, and announcement order—zero screen switching chores. The Big Screen (/live/:competitionId / UC-PUB-05) is completely public, zero chrome, and polls GET /public/competitions/{id}/live every 3s (1s edge cache, holds last state if network drops). In our current design, it is driven by FinalShowService for the Final. Heat progression in prelims is driven by the Floor Manager (StaffRole.FLOOR_MANAGER / UC-FLR-02) while dancers read mobile assignments (UC-CMP-02).
Topic 2 · 3 / 4

Industry Scrutineering & Broadcast Standards

Dancesport Scrutineering Systems
Danceplace: "Live stream competition line-up, call backs, and results to a digital display board."
danceConvention (WSDC registry standard): mobile check-in, floor marshalling, stage announcer teleprompter.
Danceit, Vote4Dance: start lists and placement displays on arena LED walls.
Live Broadcast & Overlay Engines
LiveHeats: Headless digital display board driven by automated heat progression.
Competition Corner: Real-time broadcast overlay graphics ingested into ballroom screens and stream feeds.
Traditional Paper Scrutineering: Heat & callback sheets pinned to ballroom walls; Announcer reads bib numbers.
Industry Standard: Automated, Event-Driven Venue & Stream Feeds
Topic 2 · 4 / 4

Domain Architecture Proposal & Operational Calibration

Integrated Architecture Proposal
  • Athlete Mobile View: Personal heat & callback status on athlete phones (UC-CMP-02).
  • Stage Announcer (colloquially 'MC'): Strictly read-only cue teleprompter (UC-MC-01). Zero screen switching.
  • Floor Manager Driven: Heat progression driven by StaffRole.FLOOR_MANAGER, not manual scene clicks.
  • Public Venue Display: Extend UC-PUB-05 to project active heats during prelims/semis.
Technical Specification
  • Endpoint: GET /public/competitions/{id}/live (UC-PUB-05). Public, unauthenticated.
  • Transport & Cache: HTTP polling every 3s with 1s CDN edge cache (offline resilient: holds last screen on network drop).
  • Privacy Invariant: Zero PII on public screens (names & consented photos only, initials fallback).
  • MC Contract: GET /competitions/{id}/live/mc (UC-MC-01). Adds bibs & reading order.
1

From your experience running events on the ground, who would operate that manual scene switcher at the desk, and does it risk falling out of sync with the floor?

Helps us confirm whether automating the display directly from Floor Manager heat calls removes desk friction.
2

From your experience on the competition floor, what do dancers and spectators need to see on the ballroom screen during prelims?

Do you prefer showing strictly bib numbers (fast, clean, privacy-safe), or bib numbers plus the dancers' first names?
Nothing in the design changes today. The answers go on the list for after the move to the organization.
Topic 3 · 1 / 4 · Row 3 in Walkthrough

The stage ceremony: who sees final placements first? (colloquially 'podium')

Core Platform · Publish with Ceremony Hold
Director publishes on site with ceremony hold UC-DIR-13 · embargo: true
Scores and points are calculated and frozen immediately
Phones and web see: "Ceremony in progress — Placements held"
MC reads from big screen / MC screen: UC-PUB-05, UC-MC-01
Director taps Reveal: live instantly on all phones and rankings
WBL Specifications · Dedicated Announce & Moderation
Director selects "Announce" scene on venue screen UC-PAN-05
Step-by-step final placements reveal: 3rd, 2nd, 1st with undo (colloquially 'podium reveal')
Results not yet official or published on the web
After announcement: moderator in back office must approve final placements before points exist (colloquially 'podium' / WBL: 'aprobar podio') UC-MOD-05
Risk: moderator approval delay stalls stage trophies before the party
Both systems protect the stage surprise: the room hears final placements (colloquially 'the podium') from the announcer before phones buzz. The difference: ours needs no remote moderator during awards. Points are computed up front; only visibility is held.
Topic 3 · 2 / 4

Stage Protocol: How the Ceremony Hold Operates

Core Platform Implementation
1 Director locks round. Results computed, frozen, and audited.
2 Director publishes with Ceremony Hold (embargo).
3 MC announces winners live using Big Screen / MC View.
4 Director taps "Reveal": full marks & points unmasked worldwide.
Final · Bachata Sensual J&J
🏆 1st Place: 104 & 201
2nd: 168 & 1863rd: 133 & 215
Big Screen Show · reveals step-by-step with applause
Dancers' phones masked until director taps Reveal
Locked & Published (Held)PointsAward created · API returns results: null for public
→
Stage CeremonyAnnouncer screen & venue projector show step-by-step final placements reveal
→
Director taps "Reveal"POST /rounds/{id}/reveal · instantly unmasks full scorecard breakdown
Why this is safer: The calculations are already done and verified before the MC speaks. There is no risk of a calculation error or database lock mid-ceremony, and no waiting for an off-site moderator.
Topic 3 · 3 / 4

How championship dance events handle ceremonies

WSDC (West Coast Swing)
Results are calculated by the scoring software and verified by the Chief Judge prior to the awards presentation.
Master scoring sheets and individual judge marks are strictly withheld until after trophies are awarded from the stage.
WSDC Registry Event Guidelines, Contest Integrity & Scoring Protocol
Ballroom & Dancesport (NDCA / WDSF)
Chairman of adjudicators and scrutineer certify placements. Awards are announced in reverse order (6th to 1st).
Public posting of detailed marks occurs only after the formal stage presentation concludes.
NDCA Rule Book, Section IV · Scrutineering and Awards
1 · Verify & Lock→2 · Stage Ceremony Hold→3 · Public Reveal
Topic 3 · 4 / 4

Recommendation and questions on ceremonies

Architecture Recommendation
  • Keep Ceremony Hold (embargo) as default for final rounds: prevents dancers learning results on phones before the stage announcement.
  • Keep one-tap Director reveal: no remote moderator approval needed during festival trophies before the party.
  • Add optional auto-reveal timer: if director forgets to tap Reveal, embargo auto-lifts after 60 minutes.
Technical Specification
  • results_embargoed: true stored in PublishedResultSnapshot.
  • GET /competitions/{id}/results returns placements only after reveal.
  • Points and standings are already generated in DB; zero background delay on reveal.
1

From your experience running live events on the ground, do dancers ever see results on their phones before the MC speaks from the stage?

Has a dancer ever celebrated or walked off before the stage announcement?
2

At your festivals, who actually approves final placements (colloquially 'the podium'): does a remote moderator have to stay awake in another timezone, or does the festival director on site make the call?

Does waiting for off-site approval ever stall stage trophy presentations before the party?
Nothing changes today. The answers confirm whether our one-tap reveal replaces the remote moderator queue.
Topic 4 · 1 / 4 · Row 4 in Walkthrough

Email notifications: 12 templates vs event lifecycle

Automated Event Lifecycle (AWS SES)
Lifecycle reminders: 72h schedule + 24h check-in instructions UC-E8-02, UC-E8-03
One-click withdrawal link: dancer can notify scratch without login UC-CMP-10
High deliverability: AWS SES, dedicated IP, strict DMARC/SPF
Automated bounce suppression blacklist prevents account suspension
Photo consent & data privacy notices automated
WBL Specifications · Administrative Template Model
12+ transactional templates: organizer approved/rejected, tier grant, disputes WBL:4160-4171
Judge 72h access magic link email WBL:1743
Dancer accreditation confirmation + assigned bib email WBL:1971
Sent via background worker over generic SMTP: high risk of festival spam drops
No automated 72h / 24h event preparation reminders or withdrawal links
WBL has a great taxonomy of administrative notification templates. Our architecture focuses on competitor lifecycle, deliverability, and avoiding desk no-shows.
Topic 4 · 2 / 4

Athlete Lifecycle Reminders & One-Click Scratch Automation

Competitor Lifecycle Timeline
1 · Signup Cognito verified email confirmation + photo consent.
2 · 72h Before Schedule briefing, division cap confirmation, hotel/venue info.
3 · 24h Before Desk check-in pass + 1-click scratch link (no login needed).
4 · After Publish Official result summary link + feedback breakdown.
✉ DevMellio · Bachata Sensual J&J
24 Hours to Prelims · Event Check-in
Ready for the floor, Maria?
Amateur Follow Bib at desk
Doors open 18:30 CEST
Injured or delayed? Tap below to release your spot:
Withdraw from Competition (1-Tap)
Secure HMAC token: allows instant scratch without remembering password
72h / 24h AutomationReduces festival check-in desk queues by up to 40%
→
1-Click ScratchCleans heat roster before prelims start; avoids empty floor slots
→
Deliverability EngineAWS SES with automatic bounce handling protects domain sender reputation
Why 1-click withdrawal matters: At dance festivals, competitors who get injured or miss flights never log into apps to cancel. Giving them a 1-click email button updates the floor manager's roster in real time before heats are drawn.
Topic 4 · 3 / 4

Deliverability realities in live event technology

Modern Event Tech (Eventbrite, Ticket Tailor)
Automated countdown notifications (72h and 24h before doors) achieve 60%+ open rates, driving critical on-time arrivals.
Self-service cancellation directly from transactional confirmation emails reduces festival registration desk queues by over 35%.
Eventbrite Festival Operations Benchmark, 2025
Email Deliverability Standards (Google & Yahoo 2024+)
Bulk transactional senders must maintain strict DMARC alignment, TLS, and under 0.1% spam rates or face total inbox rejection.
Self-hosted SMTP background workers without reputation monitoring regularly suffer silent inbox failures at high-volume events.
Google & Yahoo Sender Guidelines, Mandate Enforcement
Dedicated AWS SES→DKIM / DMARC Strict→Bounce Blacklist
Topic 4 · 4 / 4

Recommendation and questions on communications

Architecture Recommendation
  • Adopt WBL's administrative template catalogue: add formal templates for organizer approvals, tier grants, and dispute confirmations.
  • Keep AWS SES cloud infrastructure: ensures delivery rates >99% and shields organizer domains from spam blacklisting.
  • Keep 72h / 24h lifecycle reminders and the 1-click withdrawal button to protect the floor manager from ghost dancers.
Technical Specification
  • AWS SES handles all outgoing emails with DKIM signing.
  • Automated bounce and complaint webhooks write to suppression lists.
  • Withdrawal link carries a signed HMAC SHA-256 token valid until roster freeze.
1

In your experience running events on the ground, do competitors or judges ever complain about emails landing in Spam or missing links?

Has generic SMTP delivery caused dancers to miss heat calls or judge links?
2

From your festival experience, would your registration desk benefit from automated 72h and 24h reminders that let dancers scratch in 1 click?

How many dancers currently no-show at your check-in desk without advance notice?
Nothing changes today. The answers guide which administrative templates we import into our SES pipeline.
Topic 5 · 1 / 2 · Event Domain Model · ADOPT

Row 5 · Multi-Day Event Temporal Model & Block Scheduling

Our System Design
Single competition_date timestamp per competition in CompetitionManagement
Multi-day festivals represented by grouping separate competitions under shared event_id
Clean division lifecycle boundaries: Amateur Prelims (Fri) vs Pro Finals (Sun) isolated
No multi-day schedule state drift, but requires manual foreign-key grouping for weekend pass ticketing
World Bachata League Specifications
Explicit start_date and end_date on Competition aggregate (WBL:272, 1492, 2939)
Multi-day festival spans Friday 18:00 to Sunday 23:59 across multiple calendar days
Participant registration window stays open until the final day of the event window (WBL:906)
Concurrency hazard: round transitions across multi-day sessions can induce ambiguous temporal states
System Design Contrast & Invariants: Modeling multi-day festivals as a single scalar timestamp breaks when prelims occur on Friday afternoon and finals take place on Sunday before the social party. Adopting a composite temporal hierarchy: Event → 1..N ScheduleBlocks → 1..N Rounds provides strict calendar bounding while maintaining a unified athlete accreditation scope.
Row 5 of 25 · Area: Event Domain Model · Verdict: ADOPT (Size S)
Topic 5 · 2 / 2 · Technical Specification

Row 5 · Schema Contract & Recommendation

Technical Specification
  • Verdict: ADOPT (Size S)
  • Schema Migration: Add start_date: DATE, end_date: DATE, and timezone_iana: VARCHAR(64) to Event root.
  • Child Aggregate: Introduce ScheduleBlock entity: (id, event_id, calendar_date, block_type, start_time, end_time).
  • Foreign Key: Rounds bind to schedule_block_id, ensuring deterministic chronological execution.
Operational Invariant

Registration lock triggers per division schedule block rather than hard-locking the entire weekend festival prematurely.

Operational Calibration (Sebas & Silvia) (from your experience running live festivals): When prelims conclude and the festival transitions to the evening party, does your team prefer schedule blocks to advance automatically by clock time, or does the Competition Director manually trigger the transition?
Row 5 of 25 · Area: Event Domain Model · Verdict: ADOPT
Topic 6 · 1 / 2 · Floor Operations · ADOPT

Row 6 · Field Parity Invariant & Auxiliary Competitors

Our System Design
Strict mathematical parity invariant ($N_{\text{leads}} == N_{\text{follows}}$) per heat
No database entity for non-scored auxiliary dancers; relies on manual desk re-assignment
Floor Managers forced to improvise unrecorded pairings or hold solo heats during live prelims
Roster freeze locks participant table without an explicit scorable: false entity flag
World Bachata League Specifications
Explicit auxiliary partner entity (colloquially 'volunteer filler' / WBL: 'voluntario') (WBL:832, 1928, 2145)
Resolves uneven prelim rosters (e.g. 24 Leads vs 29 Follows) by assigning non-scored auxiliary dancers
Auxiliary dancers are marked in DB: dance physically on floor but judges NEVER score them
Prevents competitors from dancing solo or suffering irregular heat rotations (WBL:2160)
System Design Contrast & Invariants: An auxiliary partner must dance physically to preserve lead-follow pairing symmetry, but MUST be excluded from Relative Placement calculation matrices (scorable: false, points_eligible: false). Without explicit database modeling, improvised floor-level fillers pollute judge ballots and skew median placement rankings.
Row 6 of 25 · Area: Floor Operations · Verdict: ADOPT (Size S-M)
Topic 6 · 2 / 2 · Technical Specification

Row 6 · Schema Contract & Recommendation

Technical Specification
  • Verdict: ADOPT (Size S-M)
  • Schema Migration: Add is_auxiliary: BOOLEAN DEFAULT FALSE on HeatParticipant relation.
  • Ballot Validation: Judge scoring API (POST /ballots) masks input controls for bibs where is_auxiliary == true.
  • Relative Placement Pipeline: Scrutineering worker filters out auxiliary records prior to computing majority rank distributions.
Operational Invariant

Auxiliary dancers can be drawn from earlier completed heats or registered volunteer pools without creating duplicate active competitor IDs.

Operational Calibration (Sebas & Silvia) (from your experience on the competition floor): When an auxiliary volunteer dancer steps in during prelims, do you typically grab volunteer leads from an earlier heat, or do you coordinate a separate registered pool of volunteer helpers?
Row 6 of 25 · Area: Floor Operations · Verdict: ADOPT
Topic 7 · 1 / 2 · Panel Management · ADOPT

Row 7 · Dynamic Panel Reconfiguration & Emergency Substitution

Our System Design
Adjudicator panel locked post-roster-freeze; modifications require PSA CLI API access
No interactive 1-tap substitution UI on Director or Floor Manager dashboards (UC-ADM-05 / UC-PSA-06)
Staff-cannot-dance invariant strictly verified upon any adjudicator assignment (UC-DIR-04)
Emergency substitutions mid-round risk halting the entire competition floor while backend CLI is invoked
World Bachata League Specifications
Runtime adjudicator replacement endpoint (colloquially 'replace judge on screen' / WBL: 'sustitución de juez') (WBL:1664)
Floor Manager handles live emergencies: judge device failure, sickness, or travel delay
Replacement judge receives immediate session credentials; uncompleted ballot slots migrate atomically (WBL:1678)
Audit log records judge replacement timestamp, previous judge ID, and reason code
System Design Contrast & Invariants: Replacing an adjudicator mid-round requires atomic ballot slot migration. Partial marks submitted by Judge A must be marked VOID_SUBSTITUTED in the audit ledger, and a clean ballot instance created for Judge B. The replacement judge MUST be validated against UC-DIR-04 (Staff-Cannot-Dance invariant) before role binding is accepted.
Row 7 of 25 · Area: Panel Management · Verdict: ADOPT (Size M)
Topic 7 · 2 / 2 · Technical Specification

Row 7 · State Machine Contract & Recommendation

Technical Specification
  • Verdict: ADOPT (Size M)
  • Endpoint: POST /api/rounds/{id}/panel/substitute.
  • Atomic Transaction: Invalidate session tokens for retiring_judge_id; re-allocate pending ballot records; emit PANEL_UPDATED event.
  • Audit Log: Commit immutable AdjudicatorSubstitutionLog (previous_judge_id, new_judge_id, reason_code).
Security Guard

Role-Based Access Control: Restricted to Director and Floor Manager with mandatory cryptographic signature or PIN verification.

Operational Calibration (Sebas & Silvia) (from your experience managing live panels): If Judge A scored Heats 1 and 2, but has an emergency before Heat 3, how does your floor team handle panel normalization: does the replacement judge score only Heat 3, or how do you balance the marks?
Row 7 of 25 · Area: Panel Management · Verdict: ADOPT
Topic 8 · 1 / 2 · Adjudication Telemetry · ADOPT

Row 8 · Real-Time Adjudicator Telemetry & HUD

Our System Design
Aggregated scalar counter: submitted_count / total_judges
No per-device client telemetry or connection heartbeat monitoring
Floor Manager cannot distinguish between an offline tablet, a dead battery, or an in-progress ballot
Forces physical staff traversal across the dance floor to diagnose stalled scoring
World Bachata League Specifications
Per-judge connection state machine (colloquially 'opened / not opened yet' / WBL: 'telemetría') (WBL:1827-1850)
States: PENDING_OPEN, APP_FOCUSED, BALLOT_EDITING, SUBMITTED
Floor Manager HUD displays real-time connection status, battery percentage, and active screen focus
Proactively surfaces dropped tablets or backgrounded browsers before music starts
System Design Contrast & Invariants: In a crowded ballroom with severe 2.4/5GHz RF interference, an aggregated counter leaves operations blind. A lightweight client heartbeat daemon (5s interval) streaming device telemetry (battery %, latency, viewport focus) enables proactive device triage without floor disruptions.
Row 8 of 25 · Area: Adjudication Telemetry · Verdict: ADOPT (Size S)
Topic 8 · 2 / 2 · Technical Specification

Row 8 · Telemetry Protocol & Recommendation

Technical Specification
  • Verdict: ADOPT (Size S)
  • Client Ping Daemon: Judge webapp sends heartbeat: { judge_id, round_id, battery_pct, rtt_latency_ms, focus_state } every 5s.
  • Server Telemetry Broker: Redis pub/sub channel round:{id}:telemetry pushes deltas to Floor Manager HUD.
  • Disconnection Guard: Mark adjudicator as OFFLINE_STALLED after 15s of lost heartbeats.
Offline Continuity

Local IndexedDB queue caches marks client-side; re-syncs atomically when socket connectivity recovers.

Operational Calibration (Sebas & Silvia) (from your experience with festival Wi-Fi): In crowded hotel ballrooms, how often do judge tablets disconnect, and do you need the judging webapp to operate offline with local caching until Wi-Fi reconnects?
Row 8 of 25 · Area: Adjudication Telemetry · Verdict: ADOPT
Topic 9 · 1 / 2 · Athlete Ingestion · ASK_FIRST

Row 9 · Unified Athlete Identity & Physical Identifier Lifecycle

Our System Design
Check-in and physical identifier assigned per division entry (DivisionEntry)
Athlete competing in multiple categories receives distinct bib numbers per competition
Clean data isolation: marks and heats are strictly partitioned by division schema
Operational friction: athlete must swap physical bibs between rounds; higher desk queue times
World Bachata League Specifications
Unified physical identifier (colloquially 'one bib per event' / WBL: 'dorsal único') (WBL:80-84, 1857-1903)
Athlete checks in ONCE at on-site credentialing desk (WBL: 'mesa de acreditación') and receives ONE physical bib
Same bib worn across all registered divisions (Amateur J&J, Pro-Am, Team Showcase)
2D QR code scanner processes athlete credentialing and wristband binding in bulk
System Design Contrast & Invariants: A single physical bib per weekend reduces desk queue latency and physical pin changes. However, scoring queries must join through (event_id, bib_number) → athlete_id → division_entry to resolve division-specific marks. If a dancer competes in both Amateur and Pro (as Lead/Follow), judges seeing the same bib in multiple divisions could introduce subconscious bias.
Row 9 of 25 · Area: Athlete Ingestion · Verdict: ASK_FIRST / ADOPT_UNIFIED (Size M)
Topic 9 · 2 / 2 · Technical Specification

Row 9 · Identity Contract & Recommendation

Technical Specification
  • Verdict: ASK_FIRST (Size M)
  • Schema Refactor: Move bib_number from division_entries to event_registrations root.
  • Database Invariant: Enforce UNIQUE(event_id, bib_number) across all divisions for the festival weekend.
  • Ingestion API: POST /api/events/{id}/checkin/scan ingests athlete QR code, validates waiver consent, and activates physical bib.
Scrutineering Safety

Heat generation algorithms partition dancers by role and division, preventing accidental dual-pairing of unified bibs.

Operational Calibration (Sebas & Silvia) (from your experience running check-in desks): If an athlete competes as Lead in Amateur and Follow in Open at the same festival, do they wear the exact same physical bib number on their back for both divisions?
Row 9 of 25 · Area: Athlete Ingestion · Verdict: ASK_FIRST
Topic 10 · 1 / 2 · Registration Engine · ADOPT

Row 10 · Athlete Self-Service Mutation & Cross-Role Parity

Our System Design
Strict single-entry, single-role constraint (athlete_id → role: LEAD | FOLLOW)
Athlete roster entries immutable post-creation; modifications require staff administrative override
Zero risk of competitor altering division tiers after preliminary heats have been generated
High support burden: Desk staff must manually adjust entries during peak festival check-in rush
World Bachata League Specifications
Self-service division mutation (colloquially 'changing own contests' / WBL: 'cambio de categoría') (WBL:872-911)
Competitors self-modify division entries and partners via web portal up to registration deadline
Dual-Role Participation: Dancer can register as Lead in Division A and Follow in Division B (WBL:874)
Eliminates 80% of front desk customer support inquiries prior to competition kickoff
System Design Contrast & Invariants: Self-service division changes eliminate administrative bottlenecks, but require strict temporal guards (registration_open == true and roster_frozen == false). Cross-role participation is legitimate across distinct divisions, but MUST be strictly prohibited within the identical division/round (UNIQUE(athlete_id, division_id) database invariant).
Row 10 of 25 · Area: Registration Engine · Verdict: ADOPT (Size M)
Topic 10 · 2 / 2 · Technical Specification

Row 10 · Invariant Contract & Recommendation

Technical Specification
  • Verdict: ADOPT (Size M)
  • Endpoint: PUT /api/athletes/me/registrations/{id} with temporal guard: WHERE events.roster_frozen_at IS NULL.
  • Cross-Role Constraint: CHECK (NOT EXISTS (SELECT 1 FROM division_entries de2 WHERE de2.athlete_id = athlete_id AND de2.division_id = division_id AND de2.id != id)).
  • Event Dispatch: Emit REGISTRATION_MUTATED to recalculate preliminary heat size allocations.
Audit Trail

Every competitor self-mutation logs IP, timestamp, and previous division state to prevent fraudulent last-minute tier swaps.

Operational Calibration (Sebas & Silvia) (from your experience with competitor registration): If a dancer is an Advanced Lead, do your rules allow them to enter as a Beginner Follow, or must they register at their highest achieved skill tier?
Row 10 of 25 · Area: Registration Engine · Verdict: ADOPT
Topic 11 · 1 / 2 · Scoring Algorithms · CORE_SPEC

Row 11 · Cutline Tie-Resolution Protocols & Heat Capacity Bounds

Our System Design
Head Judge Discretionary Tie-Breaking Protocol (TieBreakDecision)
Algorithmic tie detection at cutoff boundary halts round progression into AWAITING_TIE_BREAK state
Head Judge inspects tied marks matrix and submits an audited tie-break ballot
Preserves deterministic heat capacity: exactly target couple count (e.g. 10 finalists) advance to the stage
World Bachata League Specifications
Automatic cutline capacity expansion (colloquially 'tie bucket expansion' / WBL: 'empates en corte') (WBL:3297-3330)
Rule: If target cutoff is 10 couples and 4 tie for 10th place, all 14 couples advance automatically
No manual tie-break required; rounds expand dynamically to accommodate all tied dancers
Failure mode: Final rounds balloon uncontrollably, exceeding physical floor capacity and blowing out festival timetables
System Design Contrast & Invariants: Automatic bucket expansion compounds across multi-round events. A 20-couple semi-final can balloon into a 28-couple final, exceeding stage floor dimensions and blowing out live festival timetables. Head Judge tie-break ballots are cryptographically audited and permanently attached to the round calculation record.
Row 11 of 25 · Area: Scoring Algorithms · Verdict: CORE_SPEC (Size S)
Topic 11 · 2 / 2 · Technical Specification

Row 11 · Algorithmic Contract & Recommendation

Technical Specification
  • Verdict: CORE_SPEC (Size S)
  • Tie Detection Trigger: When ordinal rank sums at cutoff threshold $N$ are identical, transition to AWAITING_TIE_BREAK.
  • Scrutineering Dispatch: Push TieBreakEvent to Head Judge UI containing tied bib numbers and raw rank tallies.
  • Submission Contract: Head Judge executes POST /api/rounds/{id}/tie-break selecting exact advancing ordinals.
  • Immutable Audit: Log TieBreakDecisionAudit (head_judge_id, tie_position, selected_bibs, timestamp).
Timetable Determinism

Maintains predictable heat scheduling and prevents physical stage overcrowding during championship finals.

Operational Calibration (Sebas & Silvia) (from your experience managing ballroom stage capacity): Have you ever had a 10-couple final balloon to 14 or 15 couples because of cutline ties, and how did your MC and stage manage the physical floor space?
Row 11 of 25 · Area: Scoring Algorithms · Verdict: CORE_SPEC
Topic 12 · 1 / 2 · Adjudication Schema · CORE_SPEC

Row 12 · Multi-Criteria Normalized Schema vs Boolean Ballots

Our System Design
Standardized 4-Criteria Normalized Evaluation Schema across ALL rounds
Technique (1-10), Timing/Musicality (1-10), Connection (1-10), Styling (1-10)
Normalized percentile aggregates feed directly into Relative Placement calculation engine
Preserves pedagogical alignment with Bachata Sensual instructor certification standards
World Bachata League Specifications
Dynamic per-round ballot schema configuration (WBL:2956, 3215-3250)
Prelims use ternary checkbox ballots (colloquially 'Yes/Maybe/No' / WBL: 'cruces Sí/Quizás/No')
Finals switch to weighted criteria scoring; system must handle heterogeneous ballot structures
Ternary checkboxes reduce judging to superficial gut-feel and encourage lazy adjudication
System Design Contrast & Invariants: Bachata Sensual is built on rigorous biomechanics and musicality standards. Ternary checkboxes reduce judging to superficial gut-feel and produce dense tie clusters at the cutline. A unified multi-criteria schema provides rich diagnostic feedback to athletes and enforces professional judging rigor.
Row 12 of 25 · Area: Adjudication Schema · Verdict: CORE_SPEC (Size S)
Topic 12 · 2 / 2 · Technical Specification

Row 12 · Schema Invariants & Recommendation

Technical Specification
  • Verdict: CORE_SPEC (Size S)
  • Standard Ballot Schema: JudgeMark vector { technique: float(1..10), musicality: float(1..10), connection: float(1..10), styling: float(1..10) }.
  • Normalization Engine: Dynamic Z-score scaling eliminates judge calibration bias (harsh vs generous judges).
  • Relative Placement Pipeline: Ordinals derived from normalized multi-criteria sums.
Pedagogical Integrity

Dancers receive full diagnostic score breakdowns on their profiles, demonstrating why they advanced or were cut.

Operational Calibration (Sebas & Silvia) (from your experience running panels with certified Bachata Sensual judges): Do judges prefer quick Yes/Maybe/No checkboxes in prelims to save time, or is multi-criteria scoring considered essential to the Sensual brand?
Row 12 of 25 · Area: Adjudication Schema · Verdict: CORE_SPEC
Topic 13 · 1 / 2 · League Governance · CORE_SPEC

Row 13 · Division Hierarchy Taxonomy & Tier Advancement

Our System Design
Standardized two-division hierarchy (AMATEUR and PROFESSIONAL)
Cumulative points engine generates automated promotion recommendations for administrative review
League Director / App Owner cryptographically approves tier promotions before status commit
Prevents accidental competitor tier-jumping and eliminates customer service dispute lockouts
World Bachata League Specifications
N-tier configurable division taxonomy with automatic promotion engine (WBL:3649-3694)
Cumulative points automatically trigger division promotion (colloquially 'level up' / WBL: 'ascenso automático')
Promoted competitors are instantly locked from entering lower divisions in subsequent events
Vulnerability: Automatic promotion triggers false customer lockouts if points are later adjusted due to errata
System Design Contrast & Invariants: Automatic database triggers promoting dancers immediately upon point issuance create customer service locks if points are later adjusted due to a scoring dispute or errata fix. Automated recommendation flags coupled with authorized human approval preserves regulatory sanity.
Row 13 of 25 · Area: League Governance · Verdict: CORE_SPEC (Size M)
Topic 13 · 2 / 2 · Technical Specification

Row 13 · Advancement Engine & Recommendation

Technical Specification
  • Verdict: CORE_SPEC (Size M)
  • Cumulative Points Engine: Calculates athlete league points upon official result commit.
  • Promotion Trigger: Emits PromotionEligibilityEvent when cumulative_points >= threshold.
  • Approval Workflow: League Director reviews candidate in back office and invokes POST /api/league/promotions/{id}/commit to transition athlete tier.
Audit Record

Promotion events record issuing administrator ID, qualification points total, and timestamp in immutable ledger.

Operational Calibration (Sebas & Silvia) (from your experience with dancer disputes): If a dancer is automatically promoted on Saturday night, but discovers on Sunday morning that a score typo was corrected, how do you handle moving them back without disrupting their registrations?
Row 13 of 25 · Area: League Governance · Verdict: CORE_SPEC
Topic 14 · 1 / 2 · Tenant Governance · CORE_SPEC

Row 14 · Multi-Tenant Sanctioning Pipeline & Governance

Our System Design
Autonomous single-tenant architecture with decentralized event execution
Once an organizer account is provisioned, the organizer creates and executes competitions autonomously
Zero operational latency: Organizers can launch regional congresses without waiting for headquarters review
League compliance enforced via standardized software invariants rather than manual bureaucratic review queues
World Bachata League Specifications
Multi-stage formal sanctioning workflow (colloquially 'league approval' / WBL: 'aprobación de evento') (WBL:1293-1342)
State machine: DRAFT → SUBMITTED → UNDER_REVIEW → SANCTIONED → ACTIVE
Central League Office reviews judge rosters, safety checklists, and licensing fees before approving ticket sales
Heavy administrative gate: Unapproved events cannot open registration or publish schedules
System Design Contrast & Invariants: Autonomous creation allows instant local hackathons and regional events. Formal sanctioning is required only if Bachata Sensual licenses third-party promoters who must meet strict brand standards. Keep our autonomous engine as default; introduce an optional SanctioningAudit gate for external third-party licensees.
Row 14 of 25 · Area: Tenant Governance · Verdict: CORE_SPEC (Size M)
Topic 14 · 2 / 2 · Technical Specification

Row 14 · Sanctioning Contract & Recommendation

Technical Specification
  • Verdict: CORE_SPEC (Size M)
  • Organization Scope: Multi-tenant TenantOrganization entity with is_franchise_sanctioned: BOOLEAN.
  • Sanctioning State Machine: Optional state transition gate SANCTION_PENDING → SANCTION_APPROVED required only for Tier 1 official championship events.
Franchise Scalability

Maintains rapid onboarding for official brand events while providing gatekeeping capabilities for external licensees.

Operational Calibration (Sebas & Silvia) (from your experience building the league): Will World Bachata League operate exclusively for your own internal events, or are you licensing third-party festival promoters who must submit applications for sanctioning approval?
Row 14 of 25 · Area: Tenant Governance · Verdict: CORE_SPEC
Topic 15 · 1 / 2 · Results Publication · CORE_SPEC

Row 15 · Edge Autonomous Finalization vs Central Approval Gate

Our System Design
Edge Autonomous Finalization Authority on the competition floor
On-site Competition Director and Head Judge hold full cryptographic signing and publication authority
Zero network dependency on remote staff: Results compute deterministically and commit to local ledger
Downstream global ranking recalculations dispatch asynchronously via resilient background worker queues
World Bachata League Specifications
Centralized Asynchronous Moderator Queue (colloquially 'moderator approves final placements' / WBL: 'moderador aprueba podio') (WBL:3067-3133, 3733-3768)
Competition Director cannot publish final placements or award points until a remote moderator signs off
Moderator can reject placements remotely and send back to judges (WBL:3745)
Catastrophic operational failure mode: Stalls stage trophy presentation before the social party if remote moderator is offline or delayed
System Design Contrast & Invariants: Right before the evening social party starts, waiting for an off-site moderator to log in stalls the trophy ceremony on stage while dancers and audience wait in the ballroom. The on-site Competition Director and certified Head Judge must hold ultimate publication authority at the venue edge.
Row 15 of 25 · Area: Results Publication · Verdict: CORE_SPEC (Size S)
Topic 15 · 2 / 2 · Technical Specification

Row 15 · Publication Flow & Recommendation

Technical Specification
  • Verdict: CORE_SPEC (Size S)
  • Director Command: POST /api/rounds/{id}/publish.
  • Atomic Transaction: Sets RoundStatus = PUBLISHED, derives placement ordinals, commits PointsAward records, and dispatches background worker for global ranking recalculation.
  • Zero remote network dependencies on stage ceremony write-path.
Edge Resilience

Even during total internet blackouts, local venue scoring continues seamlessly and syncs to cloud when connectivity resumes.

Operational Calibration (Sebas & Silvia) (from your experience running live festival awards): Has waiting for an off-site moderator or remote approval ever stalled a trophy presentation before the party while dancers and audience waited in the ballroom?
Row 15 of 25 · Area: Results Publication · Verdict: CORE_SPEC
Topic 16 · 1 / 2 · League Standings · BOTH_FINE

Row 16 · Dynamic Field-Weighted Points Decay & Ranking

Our System Design
Dynamic Field-Weighted Standings Engine (WSDC Chart 5 logarithmic scale)
Points awarded scale mathematically based on verified unique competitor field size ($N$)
Annual calendar season rankings: Points tracked per annual championship cycle
Immutable published snapshots with cryptographic audit hash for historical reproducibility
World Bachata League Specifications
Static tier-based lookup tables (colloquially 'points tables & decay' / WBL: 'tablas fijas 1..4') (WBL:34-36, 3453-3521)
Awards fixed scalar points for places 1..32 regardless of actual competitor turnout
Rolling window points expiration (12-24 months) executed via daily worker cron job (WBL:4090, 4223)
Distorts global rankings: winning a 6-couple Tier 2 event grants identical points to a 60-couple international event
System Design Contrast & Invariants: Awarding 50 points for winning a 6-couple regional Tier 2 event versus a 60-couple international congress distorts global rankings. Dynamic field-weighting preserves competitive equity. Rolling 12-month decay vs Annual Calendar Season reset is a business choice, both easily supported by scheduled worker jobs.
Row 16 of 25 · Area: League Standings · Verdict: BOTH_FINE (Size L)
Topic 16 · 2 / 2 · Technical Specification

Row 16 · Mathematical Formulation & Recommendation

Technical Specification
  • Verdict: BOTH_FINE (Size L)
  • Points Formula: $P(\text{rank}, N) = \text{tier\_mult} \times f(\text{rank}, N)$ where $N$ is verified active field size.
  • Schema: PointsAward stores (athlete_id, event_id, rank, points, field_size, schedule_version).
  • Standings Worker: Nightly cron recalculates sliding window sums: WHERE awarded_at >= NOW() - INTERVAL '12 MONTHS'.
Equity Invariant

Competitors in massive competitive fields are rewarded proportionally higher than small regional fields.

Operational Calibration (Sebas & Silvia) (from your experience building the league rankings): Does Bachata Sensual prefer rolling 12-month points decay, or a clean annual season reset leading up to a World Championship Final?
Row 16 of 25 · Area: League Standings · Verdict: BOTH_FINE
Topic 17 · 1 / 2 · Integrity Architecture · ADOPT_AUDIT

Row 17 · Real-Time Heuristic Invariants vs Forensic Cases

Our System Design
In-flight zero-taint preventative interceptors and database foreign key guards
Staff-cannot-dance guard (UC-DIR-04) strictly prevents judges/staff from entering active rosters
Head Judge real-time review grid (UC-HJ-01) flags >2.5σ mark variance BEFORE locking ballots
Prevention stops corrupted data before it commits, eliminating messy post-event score revocations
World Bachata League Specifications
Post-hoc forensic audit cases (colloquially 'integrity rules & cases' / WBL: 'casos de integridad') (WBL:4041-4080)
Automated background rules flag anomalies post-event: JUDGE_COMPETES, UNBALANCED_PANEL, SCORE_OUTLIER_STDDEV
Generates formal administrative arbitration cases with retroactive remedies (WBL:3772)
Remedies: retier competition, correct final placements by hand (colloquially 'correct podium'), revoke points days after event concludes
System Design Contrast & Invariants: Stopping corrupted or collusive data before it commits is mathematically superior to auditing tainted results days later. Adopting WBL's formal IntegrityCase schema alongside our in-flight shields provides regulatory transparency and forensic auditability for official league inquiries.
Row 17 of 25 · Area: Integrity Architecture · Verdict: ADOPT_AUDIT (Size L)
Topic 17 · 2 / 2 · Technical Specification

Row 17 · Audit Schema & Recommendation

Technical Specification
  • Verdict: ADOPT_AUDIT (Size L)
  • Retain in-flight prevention gates as mandatory pre-commit interceptors.
  • Add IntegrityAuditCase schema: (id, event_id, rule_code, severity, payload_json, status, resolution_notes).
  • Automated Background Scanner: Audits judge mark variance against panel medians; flags deviations $> 2.5\sigma$ for post-event review.
Judicial Transparency

Creates an unassailable audit trail for disciplinary reviews and proves adjudicator impartiality to external sponsors.

Operational Calibration (Sebas & Silvia) (from your experience managing adjudicators): How often do you encounter suspected judge bias or scoring disputes that require post-event review and arbitration?
Row 17 of 25 · Area: Integrity Architecture · Verdict: ADOPT_AUDIT
Topic 18 · 1 / 2 · Compliance & Ethics · ASK_FIRST

Row 18 · Centralized Disciplinary Sanctions & Interceptors

Our System Design
Operational functional gates only: registration deadline, signed waiver, division eligibility
No judicial ban tables or disciplinary penalty codes in scoring engine schema
Roster freeze strictly enforced at Director level (UC-DIR-02)
Judicial bans handled administratively outside scoring engine to keep scoring core decoupled from legal workflows
World Bachata League Specifications
Judiciary sanction enforcement module (colloquially 'bans & suspensions' / WBL: 'sanciones') (WBL:3828-3874)
Admin can issue formal WARNING, TEMPORARY_SUSPENSION, or EXPULSION
Sanction hard-blocks athlete registration, on-site credentialing check-in, and judge assignment at API gateway
Permanent sanction history tracked on athlete master profile with audit timestamps
System Design Contrast & Invariants: Incorporating judicial sanctions into the scoring engine adds legal and administrative overhead. If Bachata Sensual enforces official league suspensions, an API Gateway middleware interceptor (SanctionInterceptor) can reject registration and check-in requests for sanctioned UIDs across all tenant events.
Row 18 of 25 · Area: Compliance & Ethics · Verdict: ASK_FIRST (Size M)
Topic 18 · 2 / 2 · Technical Specification

Row 18 · Sanction Schema & Recommendation

Technical Specification
  • Verdict: ASK_FIRST (Size M)
  • Schema: DisciplinarySanction table (id, athlete_id, sanction_type, reason_code, effective_from, effective_until, issuing_authority).
  • API Gateway Guard: Registration endpoint checks WHERE athlete_id = :id AND effective_until > NOW() AND sanction_type IN ('SUSPENSION', 'EXPULSION') returning HTTP 403 Forbidden.
Legal Separation

Keeps scoring algorithms pure while delegating admission eligibility to the centralized athlete IAM layer.

Operational Calibration (Sebas & Silvia) (from your experience running the circuit): Does Bachata Sensual have a formal disciplinary committee with authority to issue competitor suspensions, or are bad actors handled informally by festival organizers?
Row 18 of 25 · Area: Compliance & Ethics · Verdict: ASK_FIRST
Topic 19 · 1 / 2 · Result Immutability · CORE_SPEC

Row 19 · Placement Immutability & Break-Glass Errata Protocol

Our System Design
Final Placement Rankings (colloquially 'podium' / WBL: 'podio') derived strictly via Relative Placement calculation engine
Published placements are immutable by design; no manual row-mutation API endpoint exists
Synchronous verification: Head Judge Review Grid (UC-HJ-01) intercepts scoring errors BEFORE write-lock commits
Break-Glass Errata Ledger (UC-PSA-12): Catastrophic errors require immutable audit entry, source ballot correction, deterministic re-compute, and versioned snapshot (+1) with SHA-256 hash
World Bachata League Specifications
Interactive dispute UI & manual database row mutation (colloquially 'podium dispute' / WBL: 'disputar podio') (WBL:1054-1092)
Dancers invoke interactive POST /dispute button creating an asynchronous back-office moderation queue
Admin corrects erroneous placements (colloquially 'wrong podiums' / WBL: 'podio erróneo') via UC-ADM-24 (WBL:3887) typing new placement integers by hand
Executes unvalidated UPDATE final_placements SET rank = :new_rank; causes fatal mathematical contradiction with underlying judge marks
System Design Contrast & Invariants: In system design, typing placement positions by hand (UC-ADM-24) creates a catastrophic disconnect between the judge marks matrix and the declared winners, destroying competitive credibility. Public dispute buttons invite endless subjective score arguments. Published results must remain final by design, with rare data entry bugs resolved via an auditable break-glass errata ledger.
Row 19 of 25 · Area: Result Immutability · Verdict: CORE_SPEC (Size M)
Topic 19 · 2 / 2 · Technical Specification

Row 19 · Cryptographic Errata Contract & Recommendation

Technical Specification
  • Verdict: CORE_SPEC (Size M)
  • State Machine Flow: [ Raw Marks: judge_marks ] → [ Synchronous Review: UC-HJ-01 ] → [ Relative Placement Engine ] → [ Immutable Snapshot: SHA-256 ].
  • Break-Glass Protocol: [ Errata Audit Entry: UC-PSA-12 ] → [ Source Ballot Correction ] → [ Deterministic Re-Compute ] → [ Snapshot v2 + Ledger Hash ].
  • Rejection: Firmly reject manual row-overwrite API endpoints (UC-ADM-24).
Mathematical Integrity

Guarantee: The published placements (1st-3rd) will always match the mathematical outcome of the verified judge mark ballots.

Questions for Sebas & Silvia (from your experience running competitions):
  1. How often do dancers dispute published final placements (colloquially 'the podium'), and how do you resolve those disputes on site?
  2. If an admin manually changes a placement rank by hand, how do you explain the mathematical discrepancy to judges whose original ballots show a different winner?
Row 19 of 25 · Area: Result Immutability · Verdict: CORE_SPEC
Topic 20 · 1 / 2 · Security Architecture · CORE_SPEC

Row 20 · Adjudicator IAM: Capability Tokens vs Federated Accounts

Our System Design
Persistent authenticated user accounts with Role-Based Access Control (RBAC)
Adjudicators authenticate via WebAuthn, OAuth2, or passwordless magic email authentication
Non-repudiation: Submitted ballots are cryptographically bound to verified judge identity
Multi-year judging history, certification tracking, and anomaly profiling persist permanently
World Bachata League Specifications
Ephemeral 72-hour capability tokens (colloquially '72h magic links' / WBL: 'enlace temporal') (WBL:73, 1631)
Judges have NO persistent login accounts; organizer sends signed URL via email/WhatsApp
Generating a new link automatically revokes the previous link (WBL:1743)
Security exposure: Capability URLs sent over messaging apps can be forwarded or opened on unauthorized devices
System Design Contrast & Invariants: 72h magic links eliminate password onboarding friction during live festivals. However, capability URLs sent via WhatsApp can be forwarded, shared, or leaked to unauthorized parties without an audit trail. Authenticated accounts provide non-repudiation, tamper-proof ballot signatures, and multi-year judging performance analytics.
Row 20 of 25 · Area: Security Architecture · Verdict: CORE_SPEC (Size S)
Topic 20 · 2 / 2 · Technical Specification

Row 20 · IAM Contract & Recommendation

Technical Specification
  • Verdict: CORE_SPEC (Size S)
  • Identity Entity: Keep authenticated User aggregate with ROLE_JUDGE permission grant.
  • Zero-Friction Auth: Support passwordless single-sign-on (WebAuthn / biometric passkeys + SMS/Email 1-time OTP) to eliminate password friction on the festival floor.
  • Token Specification: Short-lived JWT (4-hour access token) bound to device fingerprint.
Audit Invariant

Every ballot submission is signed with judge session JWT, ensuring legal non-repudiation in event of corruption disputes.

Operational Calibration (Sebas & Silvia) (from your experience with judges at festivals): What is the biggest headache on the floor: judges struggling with passwords and logins, or temporary links getting forwarded or opened on the wrong device?
Row 20 of 25 · Area: Security Architecture · Verdict: CORE_SPEC
Topic 21 · 1 / 2 · Regulatory Compliance · ADOPT

Row 21 · Juvenile Data Governance & Parental Consent Ledger

Our System Design
No birth date ingestion or age-gating logic modeled in athlete registration schema
Assumed all competitors are consenting adults capable of executing digital liability waivers
Zero compliance protection for youth competitors under COPPA (USA) or GDPR Article 8 (EU)
Exposes festival organizers and league entity to severe regulatory fines and legal liability
World Bachata League Specifications
Juvenile athlete compliance pipeline (colloquially 'minors & parent consent' / WBL: 'menores de edad') (WBL:948-984)
Ingests birth_date at registration; dancers under 18 trigger mandatory guardian consent workflow
Hard-blocks check-in and bib issuance until guardian signs digital authorization
Automatic profile transition to adult status upon reaching 18th birth epoch
System Design Contrast & Invariants: Operating public youth or amateur dance competitions in the EU (GDPR Article 8) or USA (COPPA) without verifiable parental consent creates severe regulatory fines and legal exposure. Mandatory age calculation at ingestion and an immutable digital guardian waiver signature hash are critical production requirements.
Row 21 of 25 · Area: Regulatory Compliance · Verdict: ADOPT (Size M)
Topic 21 · 2 / 2 · Technical Specification

Row 21 · Juvenile Schema & Recommendation

Technical Specification
  • Verdict: ADOPT (Size M)
  • Schema Migration: Add birth_date: DATE to AthleteProfile.
  • Computed Guard: is_minor = (AGE(birth_date) < 18).
  • Schema: ParentalConsentRecord table: (id, athlete_id, guardian_name, guardian_email, signature_token_hash, signed_at, ip_address).
  • Admission Interceptor: Check-in API returns HTTP 403 GUARD_CONSENT_REQUIRED if is_minor == true and consent is absent.
Statutory Safe Harbor

Protects the Bachata Sensual brand and festival organizers against child data privacy statutory penalties.

Operational Calibration (Sebas & Silvia) (from your experience with younger competitors): What proportion of competitors at your events are minors under 18, and how do you currently collect and verify parental authorization on site?
Row 21 of 25 · Area: Regulatory Compliance · Verdict: ADOPT
Topic 22 · 1 / 2 · Legal & Compliance · ADOPT

Row 22 · Immutable Regulatory Consent Ledger & Media Release

Our System Design
Client-side UI terms checkbox without persistent database audit records
Registration payload accepts terms boolean but does not persist document version, IP, or timestamp
Fails GDPR Article 7 burden-of-proof inspection if a dancer revokes image rights post-festival
Risk of competitors demanding removal of championship livestream archives due to missing release records
World Bachata League Specifications
Statutory consent persistence (colloquially 'privacy timestamp' / WBL: 'aceptación de privacidad') (WBL:1028-1052)
Stores explicit timestamp, policy version, and IP address for Privacy Policy and Media/Photo Release at signup
Satisfies GDPR Article 7(1) burden-of-proof statutory requirements for European event operators
Granular consent separation between functional data processing and commercial video broadcast rights
System Design Contrast & Invariants: Under GDPR Article 7(1), the data controller must prove when and which specific policy version a competitor accepted. A client-side checkbox with no backend audit row fails statutory audits. Video livestreaming and photo publishing require unassailable records of media waiver consent.
Row 22 of 25 · Area: Legal & Compliance · Verdict: ADOPT (Size S)
Topic 22 · 2 / 2 · Technical Specification

Row 22 · Consent Audit Contract & Recommendation

Technical Specification
  • Verdict: ADOPT (Size S)
  • Schema: ConsentAuditRecord table: (id, user_id, document_type, document_version, accepted_at_utc, ip_address, user_agent_hash).
  • Version Migration Gate: If Terms or Media Waiver update to v2.0, user receives forced re-consent interceptor upon subsequent login.
Media Defense

Provides irrevocable legal defense against competitor copyright strikes on YouTube/Instagram livestream broadcasts.

Operational Calibration (Sebas & Silvia) (from your experience with festival media): Have competitors or attendees ever asked to have their competition videos or photos taken down after a festival?
Row 22 of 25 · Area: Legal & Compliance · Verdict: ADOPT
Topic 23 · 1 / 2 · Multi-Tenancy · ADOPT

Row 23 · Multi-Tenant Organization RBAC & Ownership Guard

Our System Design
Single organizer owner modeled per tenant entity
Staff accounts lacked hierarchical team delegation and co-owner parity
Tenant at risk of becoming permanently orphaned if the primary organizer loses credentials
No separation of duties between financial promoters, floor directors, and registration volunteers
World Bachata League Specifications
Multi-owner team management (colloquially 'organizer team' / WBL: 'equipo organizador') (WBL:1377-1422)
Supports multiple co-owners and delegated staff per organizer tenant entity
Last-Owner Guard: Strict database invariant prevents the sole remaining owner from removing themselves or deleting account
Prevents tenant orphan states where festival data becomes unmanageable after staff departure
System Design Contrast & Invariants: If an organizer partnership dissolves or an account is deleted, a system without an ownership guard leaves database records orphaned and inaccessible. Large congresses require distinct roles: Financial Owner, Competition Director, Front Desk Registrar, and Audio-Visual Tech.
Row 23 of 25 · Area: Multi-Tenancy · Verdict: ADOPT (Size S)
Topic 23 · 2 / 2 · Technical Specification

Row 23 · RBAC Hierarchy & Recommendation

Technical Specification
  • Verdict: ADOPT (Size S)
  • Schema: TenantMembership table: (tenant_id, user_id, role: OWNER | DIRECTOR | REGISTRAR | OBSERVER).
  • Database Invariant: CHECK (COUNT(user_id WHERE role = 'OWNER') >= 1). Deletion or role downgrade on the final owner raises an integrity exception.
Separation of Duties

Desk registrars can check in bibs without accessing ticket revenue data or altering competition scoring rules.

Operational Calibration (Sebas & Silvia) (from your experience organizing festivals with partners): How many co-organizers typically share management of an event, and do you need separate permissions for desk staff versus financial owners?
Row 23 of 25 · Area: Multi-Tenancy · Verdict: ADOPT
Topic 24 · 1 / 2 · Public Discovery · ADOPT_BEST

Row 24 · Public Discovery Subsystem, Edge Feeds & SEO Schema

Our System Design
Competition landing pages and REST API JSON standings endpoints
Clean JSON API architecture, but lacked multi-dimensional public calendar discovery filters
Structured for edge CDN caching (Cloudflare / AWS CloudFront) with sub-50ms TTFB
Missing structured JSON-LD SEO schema (SportsEvent) for Google Knowledge Graph indexing
World Bachata League Specifications
Server-rendered public portal (colloquially 'public site' / WBL: 'portal público y calendario') (WBL:21-42)
Multi-dimensional search filters: Event Calendar by Date, Country-based Standings, and Athlete Profile histories
Deep linking into historical competition scorecards and points progression charts
Server-side monolithic rendering: Vulnerable to database connection pool starvation during peak finals traffic
System Design Contrast & Invariants: When final results are announced, 50,000 festival attendees and livestream viewers hit the public portal simultaneously. Dynamic database queries cause connection pool exhaustion. Pre-rendered, edge-cached CDN read replicas serving static ranking snapshots provide sub-50ms TTFB with zero database load.
Row 24 of 25 · Area: Public Discovery · Verdict: ADOPT_BEST (Size L)
Topic 24 · 2 / 2 · Technical Specification

Row 24 · Edge Architecture & Recommendation

Technical Specification
  • Verdict: ADOPT_BEST (Size L)
  • Edge Ingestion: Event finalization triggers CDN cache purge for static ranking bundles at /rankings/{division}/{year}.
  • Multi-Dimensional Lookups: Country, Tier, and Division filtering served from in-memory Redis read replicas.
  • Semantic SEO: Inject JSON-LD structured data (schema.org/SportsEvent, schema.org/DanceGroup) for Google Search indexing.
Traffic Isolation

Public audience traffic is 100% decoupled from live judging APIs, guaranteeing zero scoring lag during viral finals.

Operational Calibration (Sebas & Silvia) (from your experience with live event traffic): During peak festival finals when results are announced, what volume of simultaneous visitors hit your website, and has traffic ever caused system slowdowns?
Row 24 of 25 · Area: Public Discovery · Verdict: ADOPT_BEST
Topic 25 · 1 / 2 · Production Reliability · ADOPT

Row 25 · Live Deploy Freeze & Disaster Recovery Invariants

Our System Design
Manual deployment discipline without automated CI/CD event-lock guards
Printable paper ballot scorecards exist in codebase, but disaster recovery runbooks were uncodified
Strict CI/CD deployment safeguards (Rule 1) require automated pipeline enforcement
Risk of developer pushing code during live international competition, dropping active judge sessions
World Bachata League Specifications
Automated CI/CD production deploy block (colloquially 'deploy freeze' / WBL: 'bloqueo de despliegues') (WBL:4188)
Pipeline hard-rejects deploys if ANY competition is in STATUS_RUNNING state
Emergency paper ballot fallback protocol with photographic scan capture (WBL:1778)
Prevents live database migration locks, network drops, and session invalidation during championships
System Design Contrast & Invariants: Deploying code or running database migrations during a live championship introduces session invalidation, connection drops, and potential data corruption. Automated CI/CD gates checking event run-state and a codified 5-minute Point-in-Time-Recovery (PITR) runbook are essential operational safeguards.
Row 25 of 25 · Area: Production Reliability · Verdict: ADOPT (Size S)
Topic 25 · 2 / 2 · Technical Specification

Row 25 · Continuity Runbook & Recommendation

Technical Specification
  • Verdict: ADOPT (Size S)
  • CI/CD Deployment Guard: Deployment pipeline queries /api/internal/health/live-events; halts deployment if any event is active (HTTP 423 Locked).
  • Emergency Paper Fallback: Physical paper ballots printable with unique QR codes; optical mobile scan re-ingests marks into judge_marks relation.
  • Disaster Recovery RTO: Continuous PITR (Point-in-Time Recovery) with guaranteed 5-minute RTO / zero RPO.
Zero-Taint Invariant

Guarantees that live competitions running in any timezone are 100% immune to developer deployments or breaking schema migrations.

Operational Calibration (Sebas & Silvia) (from your experience running live festivals): Have you ever experienced a total ballroom Wi-Fi blackout or electrical failure during a competition, and how did your floor team manage the transition to paper ballots?
Row 25 of 25 · Area: Production Reliability · Verdict: ADOPT
← → · H home · Click topic on menu · F full screen