Appearance
Brook MVP — Ballon d'Or Voting System
Architecture
Two independent leagues stored in separate Postgres schemas on CT100:
- Cinema League — movies and anime
- Tube League — YouTube content
Voting model
Pundits (Directors, Actors, Channels) cast 3-2-1 weighted votes. Feedback loop uses Bad / OK / Good to promote/relegate voter weight (Elite → Standard → Relegated).
Implementation queue (from handover)
| # | Task | Detail | Status |
|---|---|---|---|
| 1 | Z2 bind mount | Replace /opt/hinata-z2/scripts NFS symlink with mount --bind | proposed |
| 2 | Brook Postgres schemas | brook_cinema + brook_tube in hinata DB (CT100) | proposed |
| 3 | Brook API ingest | add --movie and add --yt endpoints on Z2 collector | proposed |
| 4 | MVP daily ballot | Cron tally of pundit votes → Telegram "Daily MVP" announcement | proposed |
| 5 | Bulma Sheets bridge | GCP service account for Tier 1 Google APIs | proposed |
Infrastructure
- Postgres: CT100 (192.168.1.253)
- Z2 collectors: ports :8090–:8094 active; Brook allocated :8096
- Doctrine: API for decoupling, direct Postgres allowed for heavy background tallying
Google API roadmap (L-research synthesis)
Tier 1 (priority):
- Sheets API — Bulma finances
- Drive API — infrastructure/cloud bridge
Michael-gated decisions
- Approval of voter weight tiers (Elite/Standard/Relegated)
- Confirmation of Tier 1 Google API rollout sequence (Bulma first)