From request to finished work.
How to assign a job with a clear finish, connect the systems it depends on, keep approvals visible, and turn a run that worked into one that repeats.
Your first job
Name the result, connect the work, define proof and authority, then inspect the outcome. One run teaches the pattern.
Read the guideHow a run works
The seven-stage contract every run follows, and the five parts of a useful request.
Read the guideProduct building blocks
Workspaces, Knowledge, Skills, Memory, integrations, identity, and review, and what each one changes.
Read the guideAutomations
Start or update runs from a GitHub event, a Slack message, a Linear update, a schedule, or a webhook.
Read the guideThe execution layer
What a governed run keeps connected
Software automation moved quickly because software has repositories, tests, environments, permissions, review, and version history. Most knowledge work has none of that. These six elements are the operating floor Opulent provides.
Accepted outcome
The requested business result, a named owner, and an acceptance condition.
Context
Approved Knowledge, policies, examples, and current system state.
Authority
Permissions, budgets, escalation rules, and actions reserved for people.
Execution
A persistent plan that can use tools, coordinate agents, and survive waiting.
Verification
Explicit checks, evidence, exceptions, and acceptance criteria.
Learning
Reviewed traces that improve future work through scoped, reversible updates.
Getting started
Start with one bounded job
- 01
Name the result
State what should exist or change when the run is complete.
- 02
Connect the work
Attach the source files and authorize only the systems the job requires.
- 03
Define proof and authority
Say what Opulent may change, how completion is checked, and what requires a person.
- 04
Inspect the outcome
Open the artifact, review the evidence and exceptions, then accept or revise.