Business notes
Partner-led approvals changed the expected stage path
The intended business rule spans multiple artifacts, so no single prompt-sized summary is enough to preserve the full constraint.
Immersive Explainer App
Operate the investigation like an AI systems console
Follow a Salesforce Opportunity stage-change case the way a recursive language model should: inspect one artifact, open the promising branch, store the finding, and synthesize only after the ledger is real.
Visible traces Working memory ledger User-directed branches
Case
Unexpected Opportunity stage change
Investigate the environment selectively, recurse into the most promising branch, and synthesize a diagnosis from stored findings.
Choose -> Inspect -> Store Recommended: Flow
Artifacts
mobile-first stack
Trace workspace
Inspect one artifact without losing the full trace
guided console
Investigation trace
Active branch
root modelFlow updates Opportunity stage after approval status changes
A record-triggered Flow listens for approval updates and writes to Opportunity stage under specific partner conditions.
Full trace
Trace the approval-status branch and the partner conditions that decide whether the Flow writes a new stage value.
Why this artifact
Inspect the Flow first because it bridges the business event and the stage mutation the user can see.
Suggested next step
Accept this branch into working memory because it establishes the first causal path.
Suggested next step
Current state
The root model is inspecting a single artifact and deciding whether the finding deserves durable memory.
Returned finding
The Flow is one mutation path and confirms that approval completion can trigger a stage update for partner deals.
Decision log
No decision recorded yet. Review the trace, then store the finding or dismiss it.
Working memory
Durable notes
0 findings
+
Working memory
Durable notes
0 findings
+
No findings stored yet. Stored evidence will collect here as a quieter ledger.
Flow
Flow updates Opportunity stage after approval status changes
The Flow is one mutation path and confirms that approval completion can trigger a stage update for partner deals.
Apex
Apex trigger adds a second stage mutation path
A second mutation path explains why the issue cannot be solved by reading only the Flow branch.
Validation
Validation rules encode assumptions from the old process
The investigation needs cross-artifact reconciliation rather than a shallow scan of one rule.
Field history
Audit trail shows stage flips after approval completion
Temporal evidence confirms that the Flow writes first and Apex applies a second legacy recalculation immediately after.
Incident notes
A prior hotfix changed one path but not the other
Past context is another artifact to inspect, not something to compress into the root prompt upfront.
Diagnosis
Unlock after evidence
+
Diagnosis
Unlock after evidence
The root model should wait until at least three findings have been stored before trusting the final diagnosis.