Illustrative
OKRs
Pick an objective, then a key result. The target stays a planning label. The second pane is what the public demos already show.
OKR targets and scores are illustrative planning values, not achieved results.
Read the OKRs in the write-up
Loading the OKR view.
Show the full illustrative table
Objective 1
A routing note a reviewer can defend without a fake accuracy number.
The illustrative target is the planning label. The second column is what the public demos already show.| Key result | Illustrative target | What the demos already show |
|---|
| KR1 | The routing note cites "not documented" for gold accuracy, and does not cite the smoke floors as quality. | The multi-head model card already says this. |
|---|
| KR2 | An import test of the n8n file, on a non-production n8n, shows emergency to senior_agent. | The file exists. It has not been run. |
|---|
| KR3 | Precision and recall leave assumptions.yaml only after a labelled sample is written down. | They are still placeholders. |
|---|
Objective 2
A next-best action with a gate in front of the score.
The illustrative target is the planning label. The second column is what the public demos already show.| Key result | Illustrative target | What the demos already show |
|---|
| KR1 | A pilot score returns churn probability, a CLV proxy, and one action from the published rule table. | POST /score does this for one IBM-sample customer. |
|---|
| KR2 | CI fails if holdout ROC-AUC, PR-AUC, or top-decile lift fall below 0.82, 0.63, and 2.60. | Those floors are in gates.yaml for the IBM artifact. |
|---|
| KR3 | A model card and the gender / SeniorCitizen table ship with the score before an agent sees it. | The pack has both, for the IBM sample only. |
|---|
Objective 3
Journey changes follow an operator log, not a synthetic clock.
The illustrative target is the planning label. The second column is what the public demos already show.| Key result | Illustrative target | What the demos already show |
|---|
| KR1 | Time-to-first-response, repeat contact, and digital-to-call are computed on an operator log. | They are computed on the synthetic log only. |
|---|
| KR2 | Cost and containment inputs are replaced from operator sources, and the placeholder label comes off only after that swap. | The label is still on every input. |
|---|
| KR3 | A failed digital attempt changes the next route in a named pilot path. | No repo implements that change. |
|---|