SC The Southerners Cup

ENGINEERING DESK

League Tasks

The work required to move The Southerners Cup from prototype to a governed, member-ready dynasty league.

The Commissioner August 4, 2026 OperationsLiving document
Working document

This board records the engineering group’s visible next actions. Owners and statuses marked assumed are proposals for manager confirmation, not assignments made by the Commissioner.

Open workstreams

6

from the engineering thread

Blocked on approval

2

constitution and member email

Engineering home

This chat

current working assumption

Task board

Open · Greg / deployment owner

Get Andy deployment access

Invite Andy to the Fly.io deployment and source repository with the least privileges needed, then verify deploy and rollback access.

In progress · Greg + Andy · assumed

Harden and validate the Commissioner

Run authorization, prompt-injection, privacy, cron-delivery, API-failure, and recovery checks; record acceptance criteria.

Current convention · Greg + Andy

Separate engineering from league chat

Use this chat for build and administration work. Choose and configure the ordinary league conversation after validation.

Draft ready · managers approve

Finish the dynasty constitution

Resolve the open decisions in the draft, revise it, then conduct formal ratification.

Not started · Commissioner drafts

Prepare member onboarding

Write a short start-here guide covering Sleeper, waivers, trades, lineups, communication, and disputes. Managers review before delivery.

Blocked · awaiting manager approval

Email the league

Send the approved onboarding instructions only after managers approve the text and recipient list.

Suggested order of operations

  1. AccessGive Andy repository and Fly.io access; confirm permissions and recovery paths.
  2. ValidationClose bot security and reliability checks before moving normal league traffic onto it.
  3. GovernanceResolve constitution choices and ratify the dynasty rules before the startup draft.
  4. SeparationKeep this as engineering; create the ordinary league channel or DM once ready.
  5. OnboardingDraft, approve, then email the member guide.

Definition of done

Bot readiness

Both administrators can deploy and recover the service; authorization boundaries and untrusted-input handling pass documented tests; scheduled delivery is verified in the intended chats.

League readiness

The constitution is ratified, Sleeper matches it, each manager has acknowledged onboarding, and the engineering and league-conversation channels have clear purposes.

Assumptions requiring confirmation

Greg is listed as the likely access grantor because ownership of the repository and Fly.io organization was not visible here. Greg and Andy are listed as joint validation owners because both are administering/training the bot. The Commissioner is proposed as drafter and sender, while managers retain approval authority. No due dates were inferred.