@Sarai-WMF are you done with this? Is it ready for implementation?

For now, they should use the docs and write their instrument code before going to MPIC.

Let's remove the long answer text with the exception of the last one and let's start using this!

I can live with an imperfect InfoChip for now. Let's do it!
Thank you for mocking it up @Sarai-WMF

I added the observations to the bottom of the google doc so we do not lose the context when we are ready to post the metrics on wiki.

@Jdlrobson and @Jdforrester-WMF this performance budget work is really great. Thank you for taking the lead.

"I confirm that I have read and understood the risks specified in the Security and Legal review"

Can we add a clear indicator to the header that this is experimental software? Maybe the cdxIconLabFlask? And/or a tag that says "alpha" similar to the beta tag on codex?

@cjming yes, on hold.

Thank you for this feature request @Diskdance.
Wikistats is not in an active enhancement development currently, but we will keep this in the backlog for consideration,

@mpopov and @nettrom_WMF Marcel makes some good points here. Would love to hear your thoughts on this as well.

Done @Aklapper (thank you, as always, for the ping).This task had been moved and resolved in error when a sprint milestone was closed.

Can I see an example of "The schemas are presented as raw YAML files."? I want to make sure the raw YAML file is accessible for non-techncial users.

eventual goal would be to replace the "guide to measuring product health" and the "guide to conducting an experiment" with a link to MPIC. Does this align with the way you've been thinking about the tool?

Understood. Yes, ideally, if we continue to custom build, this will be the goal once mature.

Priority changes due to Designer's allocation to a different team. We need to capture this information before Saria rolls off our team.