Ideas · Builder Notes
Recording why a client was chosen and what the RM changed
Kognita alpha 0.4 records the client interaction, the reasons behind an origination and the relationship manager's review, including rubber-stamp flags.
Before
The reconstruction report could not yet answer: why this client, why this product, what did the RM see and change, and who made the final decision.
After
kognita.interaction opens one journey per client. kognita.origination records why a client or product was selected as structured facts with citations, and refuses a bare score. kognita.review stores a hash of the recommendation as rendered, a structured diff and a provenance label.
AI content an RM edits stays labelled as AI then human-edited.
Why it matters
Do not contact stands for the client until an authorised human records a cited reversal; an agent cannot reverse it. A review faster than the minimum review time, or an approver at a 99.9 per cent approval rate, is flagged as a rubber stamp.
Rubber-stamp thresholds are judgement calls. The sample size of 10 is a starting point, not a standard.
Human in the loop is not a control unless you measure whether the human actually looked.
Sources
Kognita is an open-source alpha. This note comes from Kognita PR #38 in the Kognita repository.