The “Why” behind every call
An audit trail under every recommendation — the exact inputs, the engine version, and the rules that fired — plus a decision register for the calls you make yourself, with revisit dates.
How it works
- 1Every recommendation is recorded with its inputs, engine version, and the rules that fired.
- 2Open any run, any time, and see exactly why it said what it said.
- 3The log is append-only — entries are never edited in place.
What you get
- Every recommendation keeps the inputs it was computed from
- The engine version and the exact rules that fired
- Open any past run and see the math behind the call
- A member decision register — log your own calls, in your own words
- Revisit dates, so a decision comes back up when it's due a second look
- Append-only — recommendations and decisions are never silently rewritten
Common questions
What is The “Why” behind every call?
An audit trail under every recommendation — the exact inputs, the engine version, and the rules that fired — plus a decision register for the calls you make yourself, with revisit dates.
How does The “Why” behind every call work?
Every recommendation is recorded with its inputs, engine version, and the rules that fired. Open any run, any time, and see exactly why it said what it said. The log is append-only — entries are never edited in place.
What do I get with The “Why” behind every call?
Every recommendation keeps the inputs it was computed from; The engine version and the exact rules that fired; Open any past run and see the math behind the call; A member decision register — log your own calls, in your own words.