Session insights
A completed run leaves an operating record. Ask it specific questions.
Opulent can inspect one or more completed sessions to explain why a run succeeded or failed, where it spent time or compute, which dead ends it tried, which missing context caused rework, which parts of the method should be reused, and how a future request or Skill should change.
Ask a specific question
| Vague | Specific |
|---|---|
| What happened? | Which missing source caused the reconciliation to restart, and what preflight check would catch it next time? |
| Why was this slow? | Which step consumed the most compute, and was it doing work a deterministic check could have done? |
| Did it work? | Which acceptance criteria were verified with evidence, and which were asserted without it? |
A broad question produces a recap. A specific one points at a change you can make.
Comparing runs
When a Skill starts performing poorly, compare successful and failed sessions rather than rewriting the procedure from memory. Update the smallest part that explains the failure: an input check, a tool sequence, an exception rule, an output schema, or a validation step.
Test a candidate Skill on a held-out case before broad use. A change that fixes the run it was derived from tells you very little.