DEV-only admin panel. The X-Admin-Secret header is required for all operations.
Close-Circle Beta Operations
Platform launch readiness — close-circle beta vs. public launch status and blockers.
Enter admin secret above, then click Load Beta Status.
Pre-Beta Readiness
Platform capability status — what is ready vs. mock/manual/not yet active.
Enter admin secret above, then click Load Readiness Check.
Storage & Capacity
MinIO bucket stats, DB media totals, and filesystem usage.
Enter admin secret above, then click Load Storage Metrics.
Generation Handoff Preview
Read-only generation readiness summary. UC#3 handoff preview shows what Daymory would send to the AI provider — no real generation is triggered.
Generation mode: mock
· UC#3 handoff: prepared, not active
· No real provider call is made
· Public launch blocker: real generation provider not active
Enter admin secret above, then click Load Generation Readiness.
Events Overview
Recent events with owner, media counts, unlock, and generation state.
Enter admin secret above, then click Load Events.
Media Review
Manual moderation — review and set status on any media asset.
Manual beta review — no external moderation provider active.
Approve, exclude, or flag assets manually. Select an optional reason below before taking action.
Moderation mode: manual / mock
· Provider integration: prepared, not active
· Reason persistence: not active (future schema decision required)
· Public launch blocker: real moderation provider not active
Reason is shown in confirmation — not stored in DB (beta)
Enter admin secret above, then click Load Media.
Beta Feedback Collection
Close-circle beta — collect operator and tester feedback manually. No analytics or tracking is added.
Use the template in docs/daymory-close-circle-beta-invite-templates.md (Template 5) to collect feedback via WhatsApp or email.
Suggested feedback questions:
Was guest upload clear and easy to complete?
Did the link work on your phone without issues?
Was the owner dashboard easy to understand?
What felt confusing or unclear?
Would you use this for a real event?
Pending Payment Requests
Payment requests awaiting approval. Click Approve, Reject, or Cancel
directly in the table — no UUID input needed.
Approval writes an event_unlock record and queues a generation job.
Enter admin secret above, then click Refresh.
Advanced — Manual Action by Payment Request ID
Fallback for support escalations or when the payment request is not in the pending list above.
Paste the full UUID to approve, reject, or cancel.
Operational Notes
⏳Export TTL: Export requests expire 24 hours after creation. Owners must create a new export if it expires.
🔲Upload window: If upload_window_end is set on an event, new guest sessions are automatically blocked after that time — even if status is still upload_open.
🎬Generation (DEV): Mock only — no real AI provider is called. All jobs succeed immediately with a placeholder MP4.
🔍Moderation (DEV): Mock only — all uploads are auto-approved. Replace before real users join.
✉️Magic link email (DEV): Not sent — token appears in the API response. Wire Resend before private beta.
Generation mode: mock
· Provider integration: prepared, not active
· UC#3 handoff contract: prepared
· Public launch blocker: real generation provider not active
Emergency Direct Event Unlock (admin override)
Bypasses the payment lifecycle. Use only for support escalations, testing, or private-beta exceptions.
Normal flow: owner creates payment request → admin approves via panel above.
Event must be in status: upload_closed, curation, or payment_pending.