oppiOS / Playbooks
Write the shift once.
OPPI runs it on time, or when you ask.
Procedural memory
Each one has paused and is waiting on your call.
Last 7 days
Finished
4
Needed you
1
Failed
1
Oppi does not learn from your workflows yet. Once runs have been accumulating for a while, patterns it spots, routines that keep working and ones that keep failing, will show up here for you to approve.
The builder
The procedure builder lays a routine out step by step, in the venue's own words. Skills are the reusable pieces, a check, a message, a task to raise, and a skill builder keeps them consistent across procedures.
Workflows
Workflow stacks put procedures in order: an opening workflow, an event-night workflow, a closedown. One stack, many procedures, each still editable on its own.
Rehearsal
A rehearsal walks a procedure through without consequences, so you see what it would raise and to whom. Every real run is recorded in a runs table: what ran, when, and how it finished. Nothing runs that has not been seen.
From chat
In oppiGPT, ask for a playbook and a wizard drafts the procedure in the conversation. You confirm each action before it exists.
What it does
Steps, in order, in the venue's words.
Reusable pieces that many procedures share.
Procedures composed into an opening, a service, a closedown.
Run it without consequences and see what it would do.
Every run recorded: what, when, how it ended.
The procedure engine runs procedures on a schedule or on demand.
The opening workflow runs at the set time: the checks raised, the messages sent, the tasks on the board before the first person is in.
A stack built for a big night runs once on the night and rehearsed the week before.
Describe it to oppiGPT, confirm the steps, rehearse it, schedule it.
Write the routine. OPPI keeps it.
Procedures, skills and workflows the venue can rehearse and run.