Engineering notes on how sf-intelligence works under the hood - the offline reasoning model, the trust model, and what changes in each release. Read-only, grounded, deterministic.
How to read a Salesforce Flow you did not build - identifying the trigger type, why entry conditions matter as much as the trigger, how decision outcomes actually evaluate, tracing every field it writes, the undefined-order problem with two record-triggered flows on one object, and what static reading genuinely cannot tell you.
Population tells you how much data is in a field; it never tells you what depends on it. A dependency-first cleanup method - what blocks a delete, what breaks silently afterwards, the four verdicts that make the output actionable, and the blind spots no static analysis closes.
What a Salesforce data dictionary is, why exported spreadsheets go stale, and how to auto-generate a living one from your org's real metadata - offline and cited to canonical component IDs.
The full save-order sequence in plain English - where before-save flows, validation, triggers, workflow, and after-save flows fire, the classic bugs it causes, and how to see your own org's automation order and collisions offline.
The deterministic, offline reasoning model behind sfi.interpret - a two-graph join of your org vault against a 94-concept, 143-rule org-independent Concept Model that returns cited, confidence-tiered structural claims. Plus what shipped in 0.2.0 and 0.2.1.