← All clips · Hosting Contracts

Review a host application and decide

PASSING SMOKE Venue Manager 7 steps · 19.6s · recorded Aug 30, 11:32 AM · 77584d6

Viewing an archived run (20260830T183220Z-77584d6). Back to the current run.

This run has no video.

Speed

Applications arrive at all hours, so the same decision must be reachable three ways: the six-column pipeline board, a tokenized Telegram deep link that claims the application as you open it, and two inline Telegram buttons that decide it outright. The status machine is deliberately narrow (six states, an explicit allow-list of transitions) so an application can never skip review silently, and every move appends an append-only application_status_events row carrying who moved it and from which surface. Rejections must carry a reason because that reason is what the templated decline email says. Approval is the trigger point for the whole downstream chain: it invalidates the outstanding action tokens and calls the contracts module inside the same transaction.

← Plan a run of show backwards from the end time Load house credit and spend it →

Source: e2e/scenarios/test_wf_review_a_host_application.py:1 · run 20260830T183220Z-77584d6 · steps carry start_ms/end_ms offsets into the video

Steps

  1. Everything a promoter has submitted, newest first, with the platform's viability band already computed on each row.

  3. Headcount × projected ticket price against the venue's floor. The band is advice, not a decision — the manager still decides.

  5. Notes are append-only and part of the audit trail on the application.

Notes

Sign in to leave a timestamped review note. Notes land in the same review backlog as in-page annotations.

  1. No notes on this clip yet.
Run history (6)