Signal atelierPublic preview
Editorial booking OSBooker

A tactile command deck for routing, negotiation, advancing, and cash collection.

Readiness-firstExplainable AIOperator-controlled
Workflow sequence2 surfaces
SetupRouteNegotiateExecuteLearn

Booker now carries the Booker-v2 public shell: role-native entry paths up front, then a clean handoff into the live workspaces once an operator signs in.

Current scopePublic preview
Sign inStart free
Canonical referenceready

Canonical reference

Booker spec hub

Product behavior changes should begin here, then flow into contracts, architecture, and implementation.

Continue to campaigns
Canonical PRDInterface doctrineRuntime readinessMilestone sequencingChange control

Control status

Documents10
Milestones7
Required runtime6/6
Review priorities20
  • Single source of truth.The spec hub should frame what changed, why it matters, and how to verify it.
  • Design system is now canonical.Major interface changes are governed by the live interface doctrine, not ad hoc styling.

Change path

01Start from user outcome and acceptance.Product, design, and engineering changes align faster when the bar is visible before implementation starts.
02Flow into contracts and runtime seams.Shared types, commands, and workflows should move in lockstep with product intent.
03Verify with focused scenarios.Functional tests and build gates are part of the product definition, not cleanup after the fact.

Canonical documents

  • Spec hubChange-control index and canonical source ordering.docs/spec-hub.md
  • PRD v1Core promise, workflows, scope, and guardrails.docs/product/BOOKER_PRD_V1.md
  • Usable-core acceptanceMinimum end-to-end bar for a usable release.docs/product/BOOKER_V1_USABLE_CORE_ACCEPTANCE_SPEC.md
  • User stories and agentic supplementDetailed epics, acceptance checks, gap-check rules, end-to-end scenarios, and beta-driven agentic enhancements.docs/product/BOOKER_V1_USER_STORIES_AND_AGENTIC_SUPPLEMENT.md
  • 2026 bleeding-edge interface systemCanonical 2026-forward design doctrine covering Bento 2.0 layout, Liquid Glass materiality, structural motion, agentic interaction, and anti-drift rules.docs/design/BOOKER_INTERFACE_SYSTEM_V2.md
  • Architecture overviewSystem shape, runtime responsibilities, and AI boundaries.docs/architecture/overview.md
  • Domain contractsEntities, bounded contexts, events, and permission semantics.docs/contracts/domain-model.md
  • Milestone roadmapSequencing from foundations to venue portal and analytics.docs/product/BOOKER_MVP_TO_MILESTONE_ROADMAP.md
  • Prompt packLead orchestration rules and subagent execution briefs.docs/orchestrator/ORCHESTRATOR_PROMPT.md
  • PM review and ordered improvementsTwenty operating-intelligence improvements prioritized and executed in build order.docs/product/BOOKER_PM_REVIEW_2026-03-19_OPERATING_INTELLIGENCE.md

Change control

  • Update the PRD or acceptance spec before changing product behavior.
  • Add or revise an ADR when technical shape or service boundaries change.
  • Update domain contracts when schemas, events, or permissions move.
  • Implement the smallest milestone-aligned slice with tests and notes.

Runtime readiness

  • Environmentstaging · hybridready
  • Required dependencies6 of 6 configured
  • PostgreSQLPrimary system of record for orgs, booking state, audit, and outbox.Configured
  • RedisRate limits, idempotency caches, and ephemeral workflow coordination.Configured
  • ClerkProduction auth, MFA, invitations, and Google/Microsoft identity.Configured
  • Public link signing secretSigns public booking asset links and prevents shared default secrets outside local development.Configured
  • Public inbox delivery providerRoutes public booking inquiries into a shared inbox or CRM provider instead of preview-only delivery.Configured
  • Public asset storage providerStores public booking packets behind a provider-backed asset layer instead of local preview files.Configured
/api/runtime/health

Reverse check

Function coverage

Contract commands mapped

70/70mapped commands100%

Every production command currently has a primary UI surface, supporting routes, and settings coverage.

Spec coverage is complete against the current production command contract.

Delivery mix

How commands reach product surfaces

Live UIPreview bridge
Live UI45
Preview bridge25
Workflows11

Durable UI already owns 64% of the contract while the remaining bridge work stays visible in product and explicit in the spec.

Surface reach

Pages, setup, and config touchpoints

  • Primary workspace routes15 pages directly own a command flow.
  • Supporting routes16 adjacent surfaces carry handoff or review context.
  • Settings and setup routes16 config-oriented routes anchor onboarding, setup, and policy posture.
  • Heaviest setup route/artists · 17 mapped commands

Workflow coverage

Every operator workflow mapped back to contract commands

Setup

2 primary routes · /team · /sign-in

2commands
0 live2 preview
Artists

1 primary route · /artists

6commands
1 live5 preview
Venues

3 primary routes · /venues · /venue-portal · /event-needs

19commands
14 live5 preview
Campaigns

1 primary route · /campaigns

6commands
3 live3 preview
Inbox

1 primary route · /inbox

1command
0 live1 preview
Deals

1 primary route · /opportunities

6commands
6 live0 preview
Shows

2 primary routes · /shows · /lineup

11commands
10 live1 preview
Finance

1 primary route · /finance

12commands
4 live8 preview
Admin

1 primary route · /admin

5commands
5 live0 preview
Assistant

1 primary route · /

1command
1 live0 preview
Public booking

1 primary route · /book/[artistId]

1command
1 live0 preview

Runtime domains

Which infrastructure domains each UI function depends on

core-data

Currently owned directly by live product surfaces.

44commands
44 live0 preview
auth

Currently bridged while infrastructure hardens.

2commands
0 live2 preview
assets

Currently bridged while infrastructure hardens.

1command
0 live1 preview
outreach

Currently bridged while infrastructure hardens.

5commands
0 live5 preview
payments

Currently bridged while infrastructure hardens.

4commands
0 live4 preview
esign

Currently bridged while infrastructure hardens.

4commands
0 live4 preview
calendar

Currently bridged while infrastructure hardens.

4commands
0 live4 preview
worker

Currently bridged while infrastructure hardens.

5commands
0 live5 preview
public

Currently owned directly by live product surfaces.

1command
1 live0 preview

Primary routes

Pages that directly own command behavior

/finance

Finance

12commands
4 live8 preview
/venues

Venues

11commands
6 live5 preview
/lineup

Shows

8commands
8 live0 preview
/artists

Artists

6commands
1 live5 preview
/campaigns

Campaigns

6commands
3 live3 preview
/opportunities

Deals

6commands
6 live0 preview
/admin

Admin

5commands
5 live0 preview
/event-needs

Venues

5commands
5 live0 preview
/venue-portal

Venues

3commands
3 live0 preview
/shows

Shows

3commands
2 live1 preview
/team

Setup

1command
0 live1 preview
/sign-in

Setup

1command
0 live1 preview
/inbox

Inbox

1command
0 live1 preview
/

Assistant

1command
1 live0 preview
/book/[artistId]

Public booking

1command
1 live0 preview

Settings and setup routes

Pages where configuration, setup, and policy controls live

/artists

Artists · Venues · Campaigns · Deals · Shows

17commands
9 live8 preview
/finance

Finance

12commands
4 live8 preview
/lineup

Shows · Finance

12commands
12 live0 preview
/venues

Venues

11commands
6 live5 preview
/admin

Admin · Venues

11commands
7 live4 preview
/venue-portal

Venues

8commands
8 live0 preview
/campaigns

Venues · Campaigns · Assistant

8commands
4 live4 preview
/opportunities

Deals · Venues

7commands
7 live0 preview
/settings

Setup · Artists · Assistant · Public booking

5commands
2 live3 preview
/calendar

Artists · Deals · Shows

5commands
3 live2 preview
/shows

Shows

5commands
4 live1 preview
/event-needs

Venues

5commands
5 live0 preview
/team

Setup

2commands
0 live2 preview
/sign-in

Setup · Public booking

2commands
1 live1 preview
/assets

Artists

1command
0 live1 preview
/inbox

Inbox

1command
0 live1 preview

Workflow matrix

Command to surface mapping

02

Setup

0 live · 2 preview

Live UIPreview bridge
  • organization.inviteAccess setup
    Preview bridgeauth
    /teamSettings: /team, /settingsInvite commands are now staged through Team access while production identity stays on the auth bridge.
  • organization.joinJoin-mode onboarding
    Preview bridgeauth
    /sign-inSettings: /sign-in, /teamJoin mode is handled during onboarding, then echoed back into Team access for operator review.
06

Artists

1 live · 5 preview

Live UIPreview bridge
  • artist.upsertArtist create and durable editor
    Live UIcore-data
    /artistsSettings: /artistsArtists page owns profile creation and persisted editing.
  • artist.asset.versionAsset versioning
    Preview bridgeassets
    /artistsSettings: /artists, /assetsThe asset workflow is fully visible in UI while provider-backed storage remains on the asset bridge.
  • artist.calendar.connectCalendar connection
    Preview bridgecalendar
    /artistsSettings: /artists, /settingsArtist setup owns calendar provider posture.
  • artist.calendar.hold_sync.toggleHold-sync controls
    Preview bridgecalendar
    /artistsSettings: /artists, /settingsHold sync is mapped in the artist workspace so route and availability can stay coherent.
  • artist.availability.overrideAvailability overrides
    Preview bridgecalendar
    /artistsSettings: /artists, /calendarAvailability overrides stay in artist setup with calendar context nearby.
  • artist.outreach_template.updateOutreach templates
    Preview bridgeoutreach
    /artistsSettings: /artistsArtist-owned messaging templates are edited in the roster workflow and used downstream by campaigns.
19

Venues

14 live · 5 preview

Live UIPreview bridge
  • venue.upsertVenue record editor
    Live UIcore-data
    /venuesSettings: /venuesVenue workspace remains the primary write path for room records.
  • talent.profile.upsertTalent profile editor
    Live UIcore-data
    /venuesSettings: /venues, /artistsTalent profile maintenance is mapped into the venue intelligence workflow.
  • venue.claim.requestVenue ownership claim
    Live UIcore-data
    /venue-portalSettings: /venue-portalVenue users can initiate ownership through the portal and ops can review the request.
  • venue.intelligence.seed.requestIntelligence seed request
    Preview bridgeworker
    /venuesSettings: /venues, /adminThe UI can request graph expansion even while durable worker orchestration stays previewed.
  • venue.intelligence.refresh.requestIntelligence refresh request
    Preview bridgeworker
    /venuesSettings: /venues, /adminVenue refresh controls are exposed in the graph even while worker runtime is not fully live.
  • venue.availability.upsertVenue availability updates
    Live UIcore-data
    /venuesSettings: /venues, /venue-portalAvailability lives in venue intelligence and is mirrored into calendar/portal views.
  • venue.datasource.upsertVenue data sources
    Preview bridgeworker
    /venuesSettings: /venues, /adminSource metadata is visible in UI while durable ingestion jobs remain bridged.
  • venue.contact.upsertVenue contact ingest
    Live UIcore-data
    /venuesSettings: /venues, /adminOperators and users can add booking contacts directly into the shared venue graph.
  • venue.contact.validation.runContact validation
    Preview bridgeworker
    /venuesSettings: /venues, /adminVenue and admin surfaces expose validation actions even while workflow runtime is previewed.
  • venue.correction.applyVenue corrections
    Live UIcore-data
    /venuesSettings: /venues, /adminCorrection flows are part of the venue intelligence and admin review model.
  • talent.booking.recordBooking evidence logging
    Live UIcore-data
    /venuesSettings: /venuesVenue intelligence captures booking evidence so routing and fit improve over time.
  • talent.fit.refreshTalent fit refresh
    Preview bridgeworker
    /venuesSettings: /venues, /campaignsFit recalculation is mapped into venue/campaign planning while durable workers stay bridged.
  • venue.portal.updateVenue portal preferences
    Live UIcore-data
    /venue-portalSettings: /venue-portalVenue-side profile and preference edits live in the portal.
  • venue.portal.respondVenue response actions
    Live UIcore-data
    /venue-portalSettings: /venue-portalVenue reply actions are handled in the venue portal.
  • event.need.createEvent-need builder
    Live UIcore-data
    /event-needsSettings: /event-needs, /venue-portalVenue-side programming starts with a durable event-need object before artist search and invites begin.
  • event.need.updateEvent-need editor
    Live UIcore-data
    /event-needsSettings: /event-needs, /venue-portalEvent-need editing stays in the venue-side programming lane.
  • event.need.artist.shortlistArtist shortlist
    Live UIcore-data
    /event-needsSettings: /event-needs, /venue-portalShortlist state links venue demand to specific artist candidates before outreach starts.
  • venue.artist_invite.sendVenue-side invite send
    Live UIcore-data
    /event-needsSettings: /event-needs, /venue-portalVenues can initiate artist-side outreach directly from the event-need shortlist.
  • event.need.deal.createVenue-originated deal creation
    Live UIcore-data
    /event-needsSettings: /event-needs, /opportunitiesEvent needs can now create shared Booker opportunities without a separate custom workflow.
06

Campaigns

3 live · 3 preview

Live UIPreview bridge
  • campaign.createCampaign builder
    Live UIcore-data
    /campaignsSettings: /campaignsCampaign creation is fully mapped into the routing workspace.
  • campaign.updateCampaign editor
    Live UIcore-data
    /campaignsSettings: /campaignsCampaign editing and launch preparation live in the same workspace.
  • campaign.route.approveRoute approval
    Live UIcore-data
    /campaignsSettings: /campaignsRoute approval remains part of the campaign planning flow.
  • outreach.approveOutreach approval
    Preview bridgeoutreach
    /campaignsSettings: /campaigns, /artistsOutreach launch controls are present in campaigns even while send infrastructure stays previewed.
  • outreach.launchOutreach launch
    Preview bridgeoutreach
    /campaignsSettings: /campaigns, /artistsCampaign launch is UI-complete and currently rides the outreach preview bridge.
  • outreach.personalizePersonalization refresh
    Preview bridgeoutreach
    /campaignsSettings: /campaigns, /artistsPersonalization is exposed in the planner even while live sending is bridged.
01

Inbox

0 live · 1 preview

Live UIPreview bridge
  • inbox.reply.classifyReply classification
    Preview bridgeoutreach
    /inboxSettings: /inboxThe inbox owns reply labeling and handoff into opportunity state.
06

Deals

6 live · 0 preview

Live UIPreview bridge
  • opportunity.createOpportunity intake
    Live UIcore-data
    /opportunitiesSettings: /opportunitiesDeals can be created from research and inbox context directly in the opportunity desk.
  • opportunity.updateOpportunity editor
    Live UIcore-data
    /opportunitiesSettings: /opportunitiesOpportunity editing and timeline progression stay in the deal workspace.
  • opportunity.policy.approvePolicy exception approval
    Live UIcore-data
    /opportunitiesSettings: /opportunities, /artistsPolicy exceptions remain visible inside the deal desk with artist guardrails attached.
  • opportunity.offer_review.approveOffer review approval
    Live UIcore-data
    /opportunitiesSettings: /opportunities, /artistsOffer review state is managed in the opportunity desk.
  • opportunity.alternate_dates.proposeAlternate dates
    Live UIcore-data
    /opportunitiesSettings: /opportunities, /calendarAlternate-date proposal lives inside opportunity detail.
  • opportunity.alternate_date.selectAlternate date selection
    Live UIcore-data
    /opportunitiesSettings: /opportunities, /calendarSelected alternate dates stay on the same opportunity timeline.
11

Shows

10 live · 1 preview

Live UIPreview bridge
  • show.confirmShow lifecycle
    Live UIcore-data
    /showsSettings: /showsConfirmed deals move into the show workspace through the lifecycle lane.
  • show.advance.toggleAdvance checklist
    Preview bridgecalendar
    /showsSettings: /shows, /calendarAdvancing actions are operator-visible while calendar sync stays bridged.
  • show.operations.updateShow operations editor
    Live UIcore-data
    /showsSettings: /showsShow operations edits are owned by the show workspace.
  • member.upsertMember directory
    Live UIcore-data
    /lineupSettings: /lineup, /artistsLineup management starts with durable member records tied to the act.
  • member.assignment.upsertArtist-member assignments
    Live UIcore-data
    /lineupSettings: /lineup, /artistsAssignments define which members fulfill which act roles across lineup workflows.
  • member.availability.upsertMember availability
    Live UIcore-data
    /lineupSettings: /lineup, /calendarMember-level availability is now durable and can block or unlock lineup readiness.
  • lineup.requirement.upsertLineup requirements
    Live UIcore-data
    /lineupSettings: /lineup, /artistsActs can now define durable role requirements instead of relying on implicit band knowledge.
  • lineup.confirmation.requestLineup confirmation requests
    Live UIcore-data
    /lineupSettings: /lineup, /showsConfirmation requests turn lineup readiness into a durable booking dependency.
  • lineup.confirmation.recordLineup confirmation responses
    Live UIcore-data
    /lineupSettings: /lineup, /showsMember responses now update lineup readiness directly inside Booker.
  • lineup.substitute.proposeSubstitute proposals
    Live UIcore-data
    /lineupSettings: /lineup, /artistsSubstitute candidates can now be proposed as part of lineup recovery instead of living in notes.
  • lineup.substitute.approveSubstitute approvals
    Live UIcore-data
    /lineupSettings: /lineup, /artistsApproved substitutes now live in a durable pool Booker can use during lineup conflicts.
12

Finance

4 live · 8 preview

Live UIPreview bridge
  • contract.sendContract lifecycle controls
    Preview bridgeesign
    /financeSettings: /financeFinance owns contract packet lifecycle while provider-backed e-sign remains previewed.
  • contract.viewedContract lifecycle controls
    Preview bridgeesign
    /financeSettings: /financeViewed state is part of the same finance contract lane.
  • contract.signContract lifecycle controls
    Preview bridgeesign
    /financeSettings: /financeSigned state is visible and actionable in finance.
  • contract.overdueContract lifecycle controls
    Preview bridgeesign
    /financeSettings: /financeOverdue packet escalation is tracked in finance.
  • deposit.requestDeposit lifecycle controls
    Preview bridgepayments
    /financeSettings: /financeDeposit collection is visible in finance while payments infrastructure remains bridged.
  • deposit.partialDeposit lifecycle controls
    Preview bridgepayments
    /financeSettings: /financePartial collection state lives in the same finance lane.
  • deposit.paidDeposit lifecycle controls
    Preview bridgepayments
    /financeSettings: /financePaid collection state is visible in finance and mirrored into show readiness.
  • deposit.overdueDeposit lifecycle controls
    Preview bridgepayments
    /financeSettings: /financeOverdue deposit posture stays in finance.
  • member.payout_rule.upsertMember payout rules
    Live UIcore-data
    /financeSettings: /finance, /lineupInternal payout rules are now durable so post-show batches do not depend on external spreadsheets.
  • member.payout.calculateMember payout calculation
    Live UIcore-data
    /financeSettings: /finance, /lineupFinance can calculate internal payout batches directly from the show and settlement context.
  • member.payout.approveMember payout approval
    Live UIcore-data
    /financeSettings: /finance, /lineupInternal payout batches now have an explicit approval boundary before money is marked released.
  • member.payout.mark_sentMember payout sent state
    Live UIcore-data
    /financeSettings: /finance, /lineupSent-state tracking closes the internal payout loop in the same finance workspace.
05

Admin

5 live · 0 preview

Live UIPreview bridge
  • venue.claim.approveVenue claim approval
    Live UIcore-data
    /adminSettings: /adminInternal ops owns approval of venue claims.
  • venue.claim.rejectVenue claim rejection
    Live UIcore-data
    /adminSettings: /adminInternal ops can reject ownership requests from the admin queue.
  • venue.claim.revokeVenue claim revocation
    Live UIcore-data
    /adminSettings: /adminAdmin retains revocation control for misuse and compliance events.
  • admin.issue.resolveAdmin issue resolution
    Live UIcore-data
    /adminSettings: /adminInternal ops can resolve review and compliance issues directly in admin.
  • admin.issue.reopenAdmin issue reopening
    Live UIcore-data
    /adminSettings: /adminAdmin can reopen reviews from the same queue surface.
01

Assistant

1 live · 0 preview

Live UIPreview bridge
  • assistant.action.logAssistant action logging
    Live UIcore-data
    /Settings: /settings, /campaignsAssistant actions now write to the same durable product model so chat and GUI can share approvals and handoff history.
01

Public booking

1 live · 0 preview

Live UIPreview bridge
  • public.inquiry.createPublic booking inquiry
    Live UIpublic
    /book/[artistId]Settings: /sign-in, /settingsPublic inquiries originate on the booking page and route back into Booker.

Milestone map

Execution sequence

01

Milestone 0

Repo scaffold, shared contracts, design system, and app shell.

Complete
02

Milestone 1

Artist profiles, policies, assets, and campaign inputs.

Live demo
03

Milestone 2

Venue and contact data with provenance, freshness, and confidence.

Live demo
04

Milestone 3

Outreach sequences, shared inbox, and reply classification.

Live demo
05

Milestone 4

Offers, holds, contracts, and negotiation guardrails.

Live demo
06

Milestone 5

Deposits, calendar, advancing, and operational show readiness.

Live demo
07

Milestone 6

Analytics, venue portal, compliance, and operational hardening.

Live demo

PM review

Ordered improvement sequence

Execution order

  • 1. Publish the second PM review and build orderOperating model · Keep the next 20 product moves visible in the spec hub so the next iteration builds on the real product state.A new PM review captures the operating-intelligence build sequence in-product.Implemented
  • 2. Add a dashboard morning briefDashboard · Operators need the one-minute read on launch readiness, risk, blocked data, and cash posture.The home surface now opens with a concise operating pulse.Implemented
  • 3. Add an owner agenda to the dashboardDashboard · Booker should show who owns the next move across deals, finance, tasks, and admin queues.The dashboard now surfaces the next owner-led agenda items.Implemented
  • 4. Add a readiness ladder by operating domainDashboard · The team should see which domain is weakest, not just a single blended score.Booker now breaks readiness into artists, campaigns, deals, shows, finance, and data trust.Implemented
  • 5. Add an artist booking strategy briefArtists · Roster records should explain how the team should position the act, not just store fields.Artists now show a strategic booking thesis per roster entry.Implemented
  • 6. Add an artist asset-freshness splitArtists · Operators should understand which assets are fresh, stale, and versioned before sharing them.Artist records now summarize freshness, stale assets, and version history quality.Implemented
  • 7. Add campaign spacing diagnosticsCampaigns · A route should explain whether it is compressed, balanced, or too loose before launch.Campaigns now score route pacing and spacing pressure.Implemented
  • 8. Add campaign anchor and contactability scorecardsCampaigns · Shortlists need to show whether they contain real anchors, sendable contacts, and market gaps.Campaigns now summarize anchor rooms, sendable contacts, stale records, and uncovered markets.Implemented
  • 9. Add venue relationship memoryVenues · Venue records should tell the team whether the room is warm, blocked, active, or still cold.Venue pages now show relationship memory from threads and deals.Implemented
  • 10. Add inbox waiting-on-us versus waiting-on-them framingInbox · The team should know whether inbox pressure comes from delayed replies or delayed follow-through.Inbox now separates operator work from market wait states.Implemented
  • 11. Add an urgent-response queue in the inboxInbox · The most time-sensitive threads should be visible in one place, not buried in filters.Inbox now surfaces a dedicated urgent-response shortlist.Implemented
  • 12. Add a deal momentum timelineDeals · Deals should show exactly where momentum is strong, blocked, or incomplete.The deal desk now visualizes the commercial path from reply to show record.Implemented
  • 13. Add a hold-expiry radarDeals · Holds are one of the easiest places to lose momentum if the team cannot see what expires first.The deal desk now highlights the next hold deadlines across the board.Implemented
  • 14. Add contract packet readinessDeals · Before a contract goes out, Booker should explain whether the packet is commercially complete.Opportunity records now show packet blockers, readiness score, and clean items.Implemented
  • 15. Add a show critical-path panelShows · Advancing should spotlight the few items that still block a clean show day.Show ops now summarize blockers and the next milestone for each date.Implemented
  • 16. Add travel and rest-risk framingShows · Back-to-back dates and tight buffers should be visible before they create execution stress.Show ops now flag compressed routing and recovery pressure.Implemented
  • 17. Add a finance aging ladderFinance · Cash posture should be organized into due-now, due-soon, and secure buckets.Finance now summarizes aging pressure before users scan individual rows.Implemented
  • 18. Add a profitability leak detectorFinance · Booker should flag where margin, expenses, invoicing, or collection quality are leaking value.Finance now highlights the records with the worst margin and cash leakage.Implemented
  • 19. Add analytics portfolio scorecardsAnalytics · Operators need a compact read on funnel, cash, and data trust quality across the portfolio.Analytics now shows portfolio scorecards instead of isolated metrics only.Implemented
  • 20. Add admin owner-load and queue-balancing viewsAdmin · Internal ops should see where queue ownership is overloaded before trust work backs up.Admin now shows owner load, queue distribution, and balancing pressure.Implemented

Why this sequence

  • Start with operator clarity.Readiness, blockers, and next-best actions create leverage across every later workflow.
  • Tighten launch quality before adding more automation.Campaigns, outreach, and deals should feel controlled and high-signal before becoming more autonomous.
  • Finish with venue and admin actionability.Internal ops and venue-side workflows matter most after the core booking loop already feels strong.
This sequence is now part of Booker’s live spec surface.
Booker