GuestList
GuestList carries one decision from the people running a product to the product itself: this tenant, this user or the system is in this audience. The audience is a name the model declares, such as Plus. What the product does with it, for example gating a feature on it, is the product’s own business; GuestList only records who is on which list.
Nothing in GuestList depends on Direct. The operator side is a package any Arc application with a Chronicle event store can host, and the product side is a package that only receives. Box Office module entitlements are separate and unchanged: Box Office still decides what a tenant has bought, and GuestList decides which audiences someone is in.
- How GuestList works: the three levels, how the newest decision wins and what stays when the link is down.
- Receive audiences in a product: add the product side and read what it recorded.
- Feed the availability engine: hand the product’s audiences to Choreography, reactive to change.
- Report what the model declares: tell the operator which audiences and gates the model declares and which decisions arrived.
- Grant audiences as an operator: host the commands and the outbox, with or without Direct.
- Contracts: the public events, their fields and the schema snapshot.
| Package | What it is |
|---|---|
Cratis.Showrunner.GuestList.Contracts |
The public events and the types they carry |
Cratis.Showrunner.GuestList |
The product side: inbox, read models and queries |
Cratis.Showrunner.GuestList.Availability |
Optional: feeds the Choreography availability engine from the product’s local audiences. See Feed the availability engine |
Cratis.Showrunner.GuestList.Authoring |
The operator side: commands, queries and the outbox |