Reference
Master reference
Detailed presentation source and decisions.FESTLY MASTER REFERENCE / JULY 2026
One source of truth.
Many useful drill-downs.
This page protects the simple story while keeping the deeper business, product, community, storefront, event, venue, and technology decisions connected.
REFERENCE POINTSMaster reference
4Public stepsdiscover · follow · support · return
7Operating stepsapply through return
4Status labelsnow · pilot · next · locked
1Source of truthcurrent decisions beat old drafts
01 / THE BIG PICTURE
People experience moments. Staff operates a repeatable system.
Festly connects the people who make the weekend. The public experience remains simple; deeper implementation detail appears only when someone chooses to open it.
02 / HOW THE PARTS FIT
Six jobs. No mystery layer.
Each part exists to move a real person toward a useful relationship or a clearly owned offer.
The simple fan experience: discover, follow, support, and return.
Voluntary relationships created through follows, saves, alerts, posts, referrals, and repeat participation.
Named artist, seller, and organizer offers with visible ownership and delivery responsibility.
Shows, weddings, camps, activations, and services run through a repeatable review and delivery process.
An independently operated room that can host private events, production days, and selected cultural sessions.
Approved stories, recaps, artist content, and next invitations that extend the relationship after an event.
03 / TRUTH LABELS
Simple at the top. Precise when you drill in.
Connect every screen to a named participant and useful action.
Name the owner, terms, cost, and customer promise.
Tie each platform investment to the customer or operator outcome it supports.
Payments, valid tickets, fulfillment, settlement, refunds, check-in, and payouts connect through the appropriate operating systems.
04 / WHO OWNS WHAT
Connection never removes responsibility.
Public experience, verification process, page relationships, permissions, attribution rules, reporting definitions, and approved services.
Identity, rights, event facts, catalog, pricing, inventory, creative claims, delivery promise, and customer obligations.
WooCommerce and Dokan remain the record for products, sellers, checkout, orders, inventory, refunds, commissions, payouts, payments, and shipping.
Room operations, safety, permits, staffing, hospitality, private-event delivery, and venue economics.
Profile, follows, saves, alerts, posts, preferences, consent, and participation choices.
05 / ARCHIVE REVIEW
Keep the useful idea. Retire the stale claim.
The prior plans are valuable research. They are not automatic authority for current brands, prices, dates, ownership, product capability, or launch readiness.
- The visible experience should prove the operating system with real people and real outcomes.
- Applications are useful data intake for review, placement, schedules, production, safety, and reporting—not just forms.
- Every event can create approved media and a next invitation.
- Start with a narrow useful loop, then add complexity after evidence.
- Separate total customer spending, Festly revenue, direct cost, participant proceeds, and contribution.
- Old Studio Transform names, membership prices, rent structures, or partnership assumptions.
- EVO TV, EVO Society, Emberland, Evolution, Springfling, or SLC Afterdark as approved Festly properties without a separate decision.
- Named AI employees, AI token economics, white-label licensing, or broad automation as near-term products.
- Multi-level reseller structures, automatic commissions, or unapproved referral promises.
- Live checkout, valid ticketing, automated fulfillment, payouts, capacity, event dates, or venue approvals that have not passed their gates.
06 / EDITING RULES
Use these rules before adding another page or promise.
- 01
The overview must be understandable without platform vocabulary.
- 02
Every public page gets one primary action.
- 03
Every graphic must explain a flow, show a real subject, prove a capability, or compare a sourced decision.
- 04
Every offer names the payer, delivery owner, fee, direct cost, and promise.
- 05
Every capability names its status and next gate.
- 06
No legacy brand, property, price, date, or capacity becomes current through repetition.
- 07
When documents conflict, the current platform contract and production blocker record win.