Digital workers give responsibility.
Skills give capability.
But someone still has to decide when the work should happen and what process should be followed.
That is the job of a play.
A play is a repeatable operating procedure
A play is not just a prompt.
It is not just a checklist.
It is the business process around a piece of work.
It can define:
- what starts the work;
- which worker should handle it;
- which skill should be used;
- what information is needed;
- what approval is required;
- where the result should be recorded;
- what happens if something fails.
That is how AI becomes part of operations instead of a side quest in someone's browser.
Plays can be manual or scheduled
Some plays start when a person asks for them.
Some run every morning.
Some trigger when a document lands in a folder.
Some begin when a project changes status.
Some run when the CRM says an opportunity is ready for follow-up.
You can think of a play like a business-aware scheduler.
Not just "run this task at 9:00."
More like:
"Review the current work, identify what needs attention, assign the right worker, use the right skill, record the result, and escalate anything that needs a human."
Slightly more useful than a calendar reminder that says "do AI."
Plays protect against random automation
Automation without procedure is where things get weird.
The system can technically do something, so someone lets it.
Then nobody knows why it ran, what it changed, whether it succeeded, or who approved it.
That is how you get a very modern version of "the spreadsheet broke and nobody knows why."
Plays create structure.
They describe the work before the automation touches it.
Plays help separate useful work from noise
Not every AI idea deserves to become a process.
Some things are experiments.
Some are one-time tasks.
Some are better handled by a human.
Some are bad workflows that should be fixed before being automated.
A play is useful when the work repeats, the steps matter, and the result has value.
That is the sweet spot.
Plays answer the third question
In the NoodleNet hierarchy, plays sit under procedures.
They answer:
When should the work happen, and what process should be followed?
Without plays, digital workers wait around for humans to manually coordinate everything.
With plays, AI work starts to behave like part of the business.
