Every personal invite, in one place
If personal invites become a thing, they live in the console beside the invite links, under Access › Invites. One list shows who each invite is for, where it stands and what it's waiting on. Open a row to watch it the way the person would, on a phone or a desktop. The wall shows every film playing at once, and a reshuffle re-rolls one to try another look.
Invites
Invites made for one person: the film, where it stands, and what it's waiting on.
| For | Piece | Stage | Waiting on | Code | Updated |
|---|
No one-person invites on this machine. Real ones load from invites.local.json, which is gitignored and links to relay-marketing video/invites.private.json. The templates below are addressed to no one.
Templates · addressed to no one
How a row gets here
Concept only. Nothing here is wired to the platform.
- A brief or a call becomes a record. The person's details and their invite's stage live in relay-marketing (
video/invites.private.json), never in this repo. In production they sit on the invite's own single-use code. - The console lists every record beside the invite links: who, which piece, the stage (draft → copy passed → ready → shown or sent → watched → redeemed), what it waits on (Ada, Erik's pick, consent, a spelling), and where it plays.
- A row opens the real landing in a phone or a desktop frame. It's the same page the person would see, drawn from the same record. One-person shorts sit in the same list and open in the same frame.
- Watched and redeemed come from the platform: series progress from the landing's own events, and redemption from the code's campaign attribution. Neither is built.