When to use Opulent
Choose Opulent when you can name the result, provide the source context, and explain how to check completion. The work can be complex. The outcome cannot be vague.
Many jobs in parallel
Independent jobs can run at the same time, which is the difference between working the top twenty items on a list and working all two hundred.
- Separate research questions for one market brief.
- Account research for several companies.
- Independent audits across repositories or business units.
- Data checks across files, regions, or reporting periods.
- Several document or content packages held to one standard.
- Software tickets, bug reports, application tests, and feature work.
Give each parallel run its own artifact or scope. If several runs need to change the same files or records, use one lead run to sequence the work and resolve conflicts.
Migrations, reconciliations, and modernization
Opulent applies one defined transformation across a large scope: migrate data between schemas, standardize documents, update a reporting package, modernize a codebase, remove stale rules, or reconcile records across systems.
Give the run the target pattern, the source of truth, the rollback boundary, and a validation method. For a large migration, split the scope into independent packages and require the lead run to compile one completion report.
A migration is usually a good fit precisely because the judgment is front-loaded. The pattern is decided once; the volume is what makes it expensive for people.
Common, repeatable work
After the first successful run, recurring review, research, reporting, testing, documentation, triage, and maintenance can become an operating package or an automation. Reuse the approved connections, Knowledge, procedure, templates, permissions, and completion checks rather than rebuilding them.
Customer and internal delivery
Opulent prepares custom analyses, applications, workflows, document sets, and demonstrations. It can learn an unfamiliar API, create a prototype, test the result, and package the evidence for review.
Customer work needs a named owner, because the important rules often remain unwritten. That owner confirms the source material, the exceptions, the approval path, and the definition of done before the run expands.
Visual and document work
Attach images with the first request when the job begins with a chart, design, screenshot, scan, or photographed document. Opulent uses that visual context during planning instead of asking for it after the run starts.
Use Opulent when the deliverable has to stay editable. It produces native presentations, spreadsheets, and documents, retains durable previews for review, and checks the final export rather than treating the source file as proof that the rendered result is correct.
Monitored work and approval pauses
Use a persistent monitor when the job must wake on new evidence, hold scoped working context, and continue the same operation. Queue triage, exception monitoring, and account watchlists all fit this shape better than a fresh run per event.
Work that is a poor fit
A normal model interface is faster for a quick answer that needs no tools, files, state, or verification. Keep a person in direct control when an action cannot be reversed, when requirements are still changing, or when credentials and approval boundaries are unclear.
If you cannot say how you would check the result, the job is not ready to delegate yet. That is a scoping problem rather than a capability problem, and fixing it usually improves the work even when a person does it.