Keeping Four Archive Secrets Attached to Their Roles
This is an invented planning exercise, not a customer event or testimonial.
Background and constraints
A fictional four-person mystery needs random assignment, but each secret must stay with the character it was written for.
Exact tool inputs
| premise | An original archive letter has changed shelves |
|---|---|
| setting | Archive |
| names | Ari Bea Cleo Dev |
| roles | Archivist Courier Curator Reader |
| secrets | The archivist knows the shelf label was revised. The courier holds the signed transfer slip. The curator saw the sealed envelope on the new shelf. The reader received a copy rather than the original. |
Actual generated result
- name
- Ari
- role
- Courier
- premise
- An original archive letter has changed shelves
- secret
- The courier holds the signed transfer slip.
- relationship
- You exchanged a fictional letter with Bea.
- name
- Bea
- role
- Archivist
- premise
- An original archive letter has changed shelves
- secret
- The archivist knows the shelf label was revised.
- relationship
- You exchanged a fictional letter with Cleo.
- name
- Cleo
- role
- Reader
- premise
- An original archive letter has changed shelves
- secret
- The reader received a copy rather than the original.
- relationship
- You exchanged a fictional letter with Dev.
- name
- Dev
- role
- Curator
- premise
- An original archive letter has changed shelves
- secret
- The curator saw the sealed envelope on the new shelf.
- relationship
- You exchanged a fictional letter with Ari.
Planning process
The host enters role names and secrets in matching order, then generates the draw. SecretSigil shuffles role slots while retaining the secret associated with each slot. The host checks the sampled cards and prints only the intended participant’s card at a time.
Result explanation
Randomizing participants must not independently randomize the secret text. The resulting archivist always receives the shelf-label secret, whoever holds that role. Generated letter relationships are fictional conversation links, not real messages sent by the app.
Alternative
Use the default numbered-fragment secrets if the activity only needs lightweight role flavor, while keeping core evidence public.
Execution notes
Treat the full result as a host view. A shared device cannot guarantee secrecy, and complete JSON backups include every role’s information.
Continue planning
How to Run a Murder Mystery Dinner
A Two-Person Role Exchange with Private Printouts
FAQ
Are these real event records?
No. All people, dates, constraints and planning amounts in this scenario are fictional inputs supplied to demonstrate a workflow.
How can I try this plan?
Open the linked tool, enter the exact inputs above, review the result and save it locally. Export a backup if you want a separate copy.