Live entertainment operations, connected.
A maintainable first product foundation for artist planning, venue fit, Dynamic Rider data, provider coordination, ticketing and finance signals, and AI-assisted action handling in one realistic seeded story.
One show, every dependency in one operating system
This is the MVP thesis in product form: a Berlin show is not publishable because one card says demand is strong; it becomes publishable when artist context, venue reality, rider requirements, provider mitigation, ops review, ticket proof, and settlement agree.
- 01
Artist source
Luna Vale
2026.05 Dynamic Rider
Open artist cockpitEvidence link
seededProfile, audience signal, tour assumptions, and approval context are locked into the same story.
Owned fans
32.700
- 02
Venue constraint
Astra Kulturhaus
1.200 cap · 22:30 curfew
Open venue cockpitEvidence link
brokengrandMA3 compact lighting console is broken and blocks publish approval.
Tech fit
72/100
- 03
Rider requirement
Lighting console
2026.05
Open riderEvidence link
requiredThe touring show file needs a programmable desk or accepted provider alternative.
Priority
required
- 04
Provider mitigation
Pulse Production Collective
lighting
Open provider cockpitEvidence link
reviewingBackup desk is available; show-file import and venue DMX patch still need confirmation.
Checklist
1/3
- 05
Ops action
Resolve console
effectum ops
Open action taskEvidence link
open3 resolution paths stay auditable in the action center.
Due date
2026-05-31
- 06
Ticket proof
Sell First preview
threshold met
Preview ticket shopEvidence link
threshold met913 preview tickets keep commercial proof connected before public launch.
Preview tickets
913/850
- 07
Settlement outcome
Artist payout
forecast
Open finance guardrailEvidence link
forecast€35,360 revenue forecast stays connected to venue, provider, and marketing costs.
Forecast P&L
€12,456
Live backend
d1 liveActions and inventory health can persist through Cloudflare D1.
Required
highCritical production decisions stay explicitly gated.
Canonical case
seededdemo-luna-vale-maxvp · 2026-05-28
MVP operating model
A connected demo surface, not a slide deck
The first live MVP should prove the core Effectum thesis immediately: one entertainment decision touches artist approval, venue inventory, provider execution, ticket demand, finance, and human-reviewed AI action.
- 01seeded
Seed one artist story
Luna Vale carries profile, rider, management context, audience signal, and tour assumptions into the MVP.
6 roles
- 02at risk
Generate the route against venue reality
5 DACH cities are shaped by audience demand, date windows, drive time, and rider-impacting inventory.
92% demand
- 03high
Turn risk into accountable work
Pulse Production Collective and Effectum Ops share the lighting-console action instead of managing it as an external note.
2 open
- 04threshold met
Prove market and settlement
Sell First demand, ticket preview, revenue forecast, and artist payout remain visible before public launch.
€12,456
Role selection
Open the MVP from any network role
10-minute investor path
- 1Open management or artist context
- 2Open the Tour Creation Studio
- 3Inspect the Luna Vale DACH route plan
- 4Compare Berlin venue fit and technical risk
- 5Review Dynamic Rider requirements
- 6Confirm Sell First threshold state
- 7Resolve the lighting-console action
- 8Check ticketing, settlement, and margin assumptions
Connected proof signals
Sell First threshold
913/850 tickets before public launch
Demand
92%
Berlin audience fit
Technical fit
72%
blocked by inventory health
Preview sold
913
ticket buyer allocation
Artist payout
€12,456
forecast settlement
Dependency ledger
What changes where when the story moves
if
grandMA3 compact lighting console is broken
then
technical fit drops, provider readiness remains under review, and Berlin stays approval-gated.
if
913 preview tickets cross threshold
then
tour generation can justify keeping Astra in review instead of switching venue too early.
if
Resolve broken Astra lighting console is resolved
then
risk, technical fit, provider state, investor story, and payout framing converge across reloads.
Product foundation
TypeScript domain schemas cover organizations, users, artists, venues, rooms, inventory, providers, riders, tours, shows, booking, ticketing, settlements, recommendations, and tasks.
Seed selectors keep business logic out of route files so mocked data can move toward Cloudflare-backed persistence without rebuilding the UI shell.
Operational states
Open tasks
2
human-reviewable queue
Provider requests
2
pending coordination
Backend path
Current MVP data is typed and seeded locally. The transition path targets Niklas' personal Cloudflare account for Workers, D1/KV/R2, domains, and trial persistence.
Cloudflare D1 demo state
pending confirmationThe UI can run from local seed data; live Pages deployments also expose /api/health, /api/scenario, and /api/actions/resolve.