01 / Foundation
e9373c2Initial integrated workflow
The MVP connected submission, scheduling, storage and downstream delivery.
ResultSubmission tasks moved into one interface.
EngineeringProduction system · V0
- Repository window
- 20 Feb — 19 Oct 2026
- Last reviewed
- 27 Oct 2026
Paranoise Console
Engineering record
- Commits
- 92
- Residents
- 63
- Media processed
- 28 GB
- Published audio
- 126 h
01 / Evolution through code
Implementation history
Selected production milestones from the repository history.
02 / Production hardening
0012630Direct-to-storage uploads
A concentrated week of presigning, route, memory and transfer changes responded to the realities of large audio on serverless infrastructure.
ResultMedia no longer travelled through the application server.
03 / Publishing
c19eea2Mixcloud publishing
Mixcloud publishing extended Console beyond broadcast delivery into archive publishing.
ResultSubmissions could be published from the admin interface.
04 / Resilience
4521578Adaptive multipart uploads
Multipart retries, failure telemetry and adaptive part sizing made long uploads recoverable rather than opaque.
ResultFailures became observable states with recovery paths.
05 / Operations
aaa4f73Operational reporting
Confirmation email and daily schedule-readiness reporting gave operators visibility outside the dashboard.
ResultThe product became an operational feedback loop.
06 / Access
09baa9cPasswordless producer access
Invitation-only passwordless access aligned producer identity with the schedule while keeping public signup closed.
ResultAccess became easier for residents and safer to operate.
07 / Platform
becd889Multi-channel publishing
Calendar and social publishing joined artwork, Mixcloud and Webflow in a wider orchestration layer.
ResultConsole now coordinates more of the episode journey.
02 / Development intensity
Weekly commit activity
Production branch activity from February to October 2026.
03 / Architecture
Submission and publishing flow
The systems involved from show selection to delivery and reporting.
- 01
Select the scheduled show
Console reads upcoming occurrences and matches them to the authenticated producer.
Google Calendar → Supabase Auth - 02
Stage media
The browser uploads audio and artwork directly using short-lived presigned instructions.
Browser → Cloudflare R2 - 03
Validate and record
Console validates metadata, stores the submission record and tracks each delivery state separately.
Next.js → Supabase - 04
Deliver for broadcast
Audio is streamed from staging storage to the producer folder and scheduled for airing.
R2 → FTP → Centova - 05
Publish and archive
A durable workflow publishes the episode and reconciles the resulting archive records.
Mixcloud → Webflow - 06
Report the outcome
Confirmation, partial failures and schedule readiness are reported to residents and operators.
Supabase → Resend
04 / Decision log
Technical decisions
Decisions addressing media size, external dependencies and partial failure.
D-01Upload directly to object storage+
ConstraintAudio files can reach 900 MB, beyond a sensible serverless request path.
DecisionThe browser uploads to R2 with short-lived presigned instructions, then submits only object keys and metadata.
ConsequenceLower server load and fewer request-size failures, with more client-side orchestration to manage.
D-02Represent partial success explicitly+
ConstraintFTP, Drive, database and email delivery can succeed or fail independently.
DecisionPersist destination-level outcomes instead of reducing the workflow to one success boolean.
ConsequenceOperators can see what completed, recover what did not and avoid repeating successful work.
D-03Move publishing into a durable workflow+
ConstraintA browser request is the wrong lifetime for uploading and reconciling a long Mixcloud publication.
DecisionStart a retryable background workflow and make reconciliation and cleanup separate steps.
ConsequenceNavigation cannot interrupt publishing, and cleanup failure cannot erase a successful publication.