Scene room
Your next step
Use this room to join, hold a spot, confirm, message the group, and leave if needed. Payment can be part of confirmation for priced scenes; payout readiness is only a later check, not a payout.
Step 1
Ask to join
Send your interest
Step 2
Join the room
Become a participant
Step 3
Hold a spot
Reserve capacity
Step 4
Confirm
Pay only when the scene is priced
Room workflow
Follow the room from access request to confirmation, then use the member thread once server authority recognizes your account for this scene.
Coordination board
A room-level board for the four product lanes members expect: participant state, slot capacity, confirmation, and messages.
Coordination checklist
Viewer-scoped progress only; server transitions stay gated.
Canonical chain position
Intent gate only
No slots published for this scene yet.
Read-only projection of runtime truth. Observed states come from the scene runtime snapshot for the current viewer; readiness comes from the local runtime chain projection (mode: simulation-only). No participant, slot, lock, or confirmation is mutated here, and no payment, payout, or production is implied. The live slot grid is a point-in-time, public-safe view of slot occupancy only — no other participant's identity or profile is exposed. Real-time updates and a full multi-participant roster are still Planned.
Records interest only. The next steps - participant, slot hold, confirmation, value/ledger, settlement, distribution, and payout execution - remain separate server-controlled facts.
scene chain
Uses server authority to move in order: interest, participant, slot hold, payment evidence when required, ledger check, then confirmation. Settlement, distribution, payout execution, and analytics remain separate downstream facts.
leave scene
Reverses only your current non-confirmed place in the chain. It may withdraw interest, cancel a waiting participant spot, or reopen a held slot. It does not delete records and does not touch payment, ledger, settlement, distribution, or payout execution.
Member-scoped thread for the scene owner and participating members. Message identity is server-owned. This does not create payment, ledger, settlement, distribution, payout, moderation, or realtime facts.
No messages are visible for this account.
Sign in to message this scene.
Internal readouts for staging review. These panels explain what the server observed; they do not approve payments, settlement, payout, or production readiness.
Runtime-first status: this reports the coordination chain state the server can read. It does not certify payment, settlement, payout, or production readiness.
Available actions are scoped to the current viewer and server-side runtime state. A visible action is not a payment or payout authority.
not_participant
login_required
login_required
intent_missing
intent_missing
not_participant
payment_required
Settlement and payout execution remain blocked.
Commercial Runtime-first view: value records, payment evidence, ledger completion, settlement, and payout readiness are distinct. Payout execution is not claimed here.
Runtime-first view: identity, intent, participant, slot, and confirmation move in order. Commercial evidence is shown separately and never implied by this count.
Runtime allowed
7
Runtime blocked
1
Next runtime stop
Payout gate review
Detailed staging readout. It reports server-side chain decisions; it does not create value, ledger, settlement, or payout facts.
Ordered runtime decisions only. Payment evidence, ledger completion, and payout readiness remain separate commercial checks.
intent_conversion: allowed
scene_participant: allowed
scene_intent_lock: allowed
participant_confirmation: allowed
value_ledger_gate: allowed
value_record_and_ledger: allowed
payout_boundary: payout_not_enabled
participant_conversion: allowed
Pending value context
Creates a server-owned value and ledger context before owner-side Payment Link use or another payment adapter is used. Value, payment evidence, ledger state, settlement, and payout remain separate facts; the browser does not own any of them.
Payout readiness (read-only)
Reads participant, value, and ledger facts to explain whether a later distribution step could be considered. Readiness is not execution: no payout is called here, no payout truth is created here, and provider payout stays outside this room.
value_ledger_gate
Value and ledger facts stay server-owned. Browser confirmation cannot create payment proof, settlement, or payout truth.
Disabled here means this browser surface is not the authority for that fact. Runtime, value, ledger, settlement, and payout boundaries remain server-owned.
payout_analytics_boundary
Runtime confirmation, payout readiness, payout execution, and analytics conversion are separate surfaces. This room does not collapse them into one status.
Disabled here means this browser surface is not the authority for that fact. Runtime, value, ledger, settlement, and payout boundaries remain server-owned.
