Skip to content

Latest commit

 

History

History
49 lines (40 loc) · 4.73 KB

todo.md

File metadata and controls

49 lines (40 loc) · 4.73 KB

Half Life – open work

The six items from the original notes are done. This file records the cross-cutting decisions that were settled alongside them and the external steps that remain before launch.

Status

# Item State
1 Register the Ari callback URL Built; operator panel at /admin/program shows the URL + config state. External: register it and set the secrets.
2 Notify participants of review outcomes Built – Slack DM, all three outcomes, both decision paths (console + Ari). Email is a Loops workflow off the Airtable row. External: configure that workflow.
3 Submission state across the projects UI Built – card borders, per-phase chips, legend; the project page has a Review block above the repo checks.
4 Review actions on the project page Built – resubmit (opens the submit sheet) and dispute (flags for staff, changes no state).
5 Project placeholder from a reel or devlog Built – cover → newest journal image → newest reel frame (thumbnail, else a video's first frame).
6 Send grants from the admin panel (HCB) Built – manual, idempotent top-up on /admin/users/[id]. External: HCB OAuth app + refresh-token persistence.

Decisions

  • Payout ownership – the Airtable/YSWS pipeline owns payouts. The HCB "Send grant" action is a deliberate manual fallback, not the normal path. It is idempotent within Half Life but does not know what the pipeline has paid, so enabling both can double-pay. See docs/BACKEND.md → Payouts.
  • Email – Loops, off Airtable. Half Life does not mail anyone. It writes the decision to the submission's row – Loops - halfLifeReviewStatus and the reviewer's note in Loops - halfLifeReviewerNotes (see syncReviewDecisionToYsws in src/lib/airtable/sync.ts) – and a Loops workflow sends from there. The Resend path was removed rather than kept as a second sender. The same write fills two override columns – Loops - Override - halfLifeProjectName and Loops - Override - halfLifeProjectWeek – because email-tools only forwards a Loops - … field whose value changed on that row. Without them a decision on an older project changed only status and note, so the contact kept the project name and week from the maker's most recent submission. The override prefix makes email-tools apply them to the same contact property.
  • Notifications – all three outcomes, to the maker, Slack DM plus the Loops email. approved, changes requested and rejected all notify.
  • Green border – the current phase approved. The design until the build starts, the build once it has. A passed design with the build not begun reads green.

Before launch (external)

  1. Ari: register https://<host>/api/integrations/ari/webhook, set ARI_PROGRAM_ID / ARI_SIGNING_SECRET / ARI_WEBHOOK_SECRET, create the ari-retry job.
  2. Email: build the Loops workflow on the Airtable base – it reads Loops - halfLifeReviewStatus (and quotes Loops - halfLifeReviewerNotes) and sends for Approved, Changes Requested and Rejected. Create Loops - Override - halfLifeProjectName and Loops - Override - halfLifeProjectWeek as single-line text fields, then run bun run loops:backfill-review-overrides once (dry run first, then --commit) so the new columns start with each row's own values. Pause the email-tools Airtable source while doing this: the first poll after new Loops - … fields appear does a full resync, and blank overrides on that pass would clear the project name on every contact. Resume once the backfill has filled them.
  3. HCB (only if the manual fallback is wanted): register the OAuth app, invite it to the org as a manager, run a $1 top-up on a test org, and decide where the rotated refresh token is persisted.
  4. Slack: set SLACK_DISPUTES_CHANNEL_ID if dispute notices should be posted.

Original notes

  • Callback URL for Ari
  • Project approval (when done in Ari) should notify the user
    • By email and by Slack DM
  • Indicate submission state on the projects page for each project
    • Green border = approved
    • Blue border = submitted, not reviewed
    • Yellow/orange/amber border = reviewed, needs changes
    • Red border = rejected
    • Also display state and extra review info on the project page
      • Display above repo checks section
      • Multiple choice for options
        • "I have made these changes, resubmit"
        • "This review is incorrect, project works as intended" or similar
        • Other idk
  • A button in the admin panel to send out grants
  • Placeholder image for project should be a screenshot from a reel or image from a devlog