Learning loop
How a correction from anyone on the team becomes a checked, tested and reviewed learning that applies to everyone, and when it's released without waiting.
When the analyst gets something wrong, fixing it once should fix it for everyone, without letting one person's mistake become the team's truth. The learning loop does both.
1. Someone corrects an answer
On any answer, choose Helpful or Not right, and say what was wrong: A number is wrong, Wrong definition, Missing context, Misread the question, or Something else. On a single figure, use This number is wrong.
A thumbs-down that says what was wrong is a correction. Right away:
- it's saved to that person's memory, so their next questions use it;
- it's saved as a draft guide on the source, for an admin to look at;
- it opens (or joins) a learning proposal for the team.
Taking the thumbs-down back undoes all of it.
2. The proposal is checked and tested
The Curator drafts a glossary term from the correction and keeps it as a proposed version. Then two things run before anyone has to look:
- A check: a query that proves the term against your data.
- A test: one analyst run with the unreleased term, graded on what its queries actually read.
3. Approve, or let it release itself
Owners and admins review proposals under Knowledge → Proposals and on Knowledge → Learnings, and can choose Make it a team learning, Edit or Not this, and Revert one after it's released. Everyone else can Suggest for the team.
A proposal is released without waiting only when all five hold:
- It is stated outright in the correction.
- It is low-risk: a new term that touches no released metric, dataset or term, and that no approver edited.
- Its check passed.
- Its test passed and used the term.
- It was said by an owner or admin, or by two different people who are owners, admins or members.
Otherwise it waits for an approver's single tap. In Slack, approvers get Make this a team learning? right in the thread.
Nothing changes silently
Every learning is a new version of a knowledge item, with who proposed it and why. Revert takes it back.
Evals
Under Knowledge → Evals, owners and admins get one test case per verified metric and per verified query. Run them with Run now or nightly. A case passes when the answer's gate passed and it cites the expected numbers, so you know when a change to definitions or knowledge breaks something that used to work.
Knowledge
Glossary terms, guides, verified queries, skills and memory. What each one teaches the analyst, when it's used, and who can change it.
Dashboards
Describe who a dashboard is for and what they do with it. The analyst plans it, builds it while you watch, and every number on it stays a query you can open.