@leila I drafted a summary of our findings for junior/senior editors here. I am going to work on summarizing our findings for donors on Monday (there is not much really :) ).
It's still not in the format you required, but I first wanted to get a sense if these are the things you were looking for. Thank you!

Hi Leila, thanks for this.
I have one question about the levers. My understanding is that key open question for this funnel is around "conversion". So instead of how do we move metric X (we have so many metrics for each of these audiences and so our recommendations might become ineffective). I would target our lever suggestions on:

• what levers do we know of that can convert audiences from funnel stage T-1 to stage T?
• what levers we can confidently say that won't convert audiences from stage T-1 to stage T? (not worth trying)

Data collection ended in December.

Recent updates:

• More alignment created across Research and product teams
• As a result, we have a shareable version of a draft roadmap, which has already been reviewed by Applied Science and Design Research and is now out for review to ML and Head of Research.
• A few tasks around early experimentation have already started:
  • Recsys for Patrollers T398071
  • AI for Mentorship: data and initial tool T397550
  • AI-assisted tools for information retrieval T398482

Thank you @JAllemandou -- @Madocmadofmadog hi! If that answers your question, feel free to close this task.

Oh wonderful @kevinbazira sorry I misunderstood from your msg that you wanted to deploy only the metadata one! @Trokhymovych what do you need to provide the full model to ML?
Thanks so much both for all the work!

@kevinbazira based on @Trokhymovych 's feedback and after re-reading the paper, I strongly suggest we find a way to deploy the full model rather than the metadata model. The metadata model won't be serving the use-case that we have in mind for model deployment, because its accuracy is lower than what already exists on liftwing.
What would be the extra work required to deploy the full model?
CC @Sucheta-Salgaonkar-WMF for product implications, @AikoChou, and @fkaelin as he's now the owner of the knowledge-integrity pipeline.

Closing this task as this was the tracker for Q1

Resolving as this was the tracker task for Q1

Resolving this as this was the tracker for Q1.

Sorry @KC we just reviewed this as part of Fabian's Q2 allocation. This is now prioritized. Please change the description with the specific tasks for Q2. Thank you!

THanks @YLiou_WMF for creating this task. I co-assigned @CMyrick-WMF as she'll do a large portion of the analysis.

Thanks @CCiufo-WMF ! This has been prioritized on our end. @CMyrick-WMF will work with you. @CMyrick-WMF please update this task with the steps/timeline once you've clarified with the team.

Thank you @leila . Resolving this task as the doc is finalized. We will share with @GGoncalves-WMF today.

@diego I did a pass on the current draft and added some to-dos. I think before proceeding we should check-in with @leila about scope and framing. Will schedule something after the CHI deadlines.

Hi @KCVelaga ! Thanks for this request. Quick question, will you need this support in Q2 only, or throughout the whole fiscal year?

Extended the deadline as the need to speak with more PMs emerged. @fkaelin will report back the learnings of this round of meetings and the next stpes.

Moving this back to Research backlog until a training infrastructure becomes available. We will work on tooling to standardise the structure of model training, and that will be captured in a separate task.

@YLiou_WMF closing this task as follow up work is captured in T399736. Please reopen if you still need it! Thank you!

@leila just checking if you are ok with us to proceed after we responded to your last round of feedback. Thank you!

Thank you, @diego !! Resolving this task as the recommendation has been published. Thanks for all the work!

Closing this task as the blurb has been published. Thank you!

Oh no I am so sorry, I thought I've already approved this! So sorry for the delay. I approve yes!

@fkaelin closing this as I think all subtasks are completed. Please reopen if necessary. Thank you!

Declined as this has been incorporated into other tasks.

Changed the deadline as there were delays as we needed to switch the pipeline to use edit types instead of raw content diffs. The plan is to send the prototype out for feedback this week and summarize learnings in a couple of weeks.

Reassigned this to Fabian as this is a Research engineering task, the Research Science part of this is captured as subtask.

@Isaac is this task still valid? Does T361637 has a dependency on this?

@Isaac @MGerlach @fkaelin it looks like the task that had a dependency on this work has been closed. Should we decline/close this task or should we keep it open for future work?

Sure! I might remove the Research tag then if that's ok? If you identify a larger task for Research we can put it back and/or create a subtask.